> You ALWAYS and CONTINUOUSLY have to invest time. Not at all. First, you learn Emacs Lisp. Then, you don't need to learn anything else related to Emacs, EVER.

> You ALWAYS and CONTINUOUSLY have to invest time. Not at all. First, you learn Emacs Lisp. Then, you don't need to learn anything else related to Emacs, EVER. > Every time you want to use a new language, try a new plugin, etc. you need to learn a bunch of shortcuts. I think this is detrimental to actually becoming more efficient at using your IDE. No, not at all. Just rebind the defaults - the defaults are what suited the author of the package, and being a different person in different environment there's very little chance they would suit you. So, instead of learning how others do things, just pick keys you want to use, and write a hook for every new mode to bind those keys to the functions you expect of them. Once you know even just a little Elisp, it's a trivial thing to do - literally 10 minutes on the longer side. > I can just fuzzy search the commands and get a reminder of what the shortcut is. I do the same in Emacs all the time. Press Alt+x and start typing, Helm will display keybinding next to the (fuzzily matched) command names (doing it this way is often faster(!) than pressing the key combination, which can involve multiple keys in a row, in a so-called chord). From the same interface, you can jump to the command source and display its documentation, too. > The example you give with git is about investing your time learning git, not investing your time learning emacs. I use git on the terminal within VSCode. I think the OP meant specifically the interactive rebase, where you're expected to replace the leading word in each line with one of a few choices. Of course, Magit is the answer here, so you don't even need the advanced ways of navigating and replacing text.