When I get to a new machine I download them and configure them on the new machine. It's a bit of a pain, but it is what I do.Įxport the key bindings for each tool and save them to a file that is stored in GITHUB. I keep: 'what I want to do', tool/keybinding/commandname, default command name (for that key binding) for each of the tools. I have a MS Word document with the different tools and the key bindings I use for them. This is somehow still natural (probably I've used emacs for 30 years). I've come to use the windows cut/copy/paste, undo/redo which for better or worse seems to be the default for most systems except emacs (so that's easy for them). So the basic's of navigation (up,down,left,right,home,end) all work the same. I currently use emacs key bindings for: emacs, eclipse, Microsoft Word, IntelliJ, Sublime, and vscode. I have a primary set of key bindings that I use across every one that will allow me to change my key bindings. I have used vi, emacs, vim, notepad++, eclipse, Microsoft Word, Visual Studio, IntelliJ, Chrome Debugger, Atom, Sublime, and most recently VSCode. :-) Nowadays, vim can do most everything, but Eclipse, IntelliJ, and Visual Studio are widely used.

It used to be simple because emacs could do everything. My approach has changed over the years (30+ in this field).

Intellij key bindings in vs code