4 ms·

Funny, you use VSCode for the same reason I use Emacs -- so I can keep vim totally stock, so I'll retain the muscle memory / not be shocked on other systems, an

Funny, you use VSCode for the same reason I use Emacs -- so I can keep vim totally stock, so I'll retain the muscle memory / not be shocked on other systems, and so that it remains completely reliable and fast on my own. I'm incredibly skeptical, however, that VSCode has as-good of a vim emulation layer as evil-mode. Evil-mode is just fantastic. Customized Emacs w/ evil-mode gives me everything I'd get from a fancy IDE, and keeps my vim muscle memory intact for those times when I am using regular vim. This has been my pattern for a decade and it's glorious. GLORIOUS, I tell you! Few things give me joy in computing like the balance in the Force that I've managed to strike between Emacs and vim

imiric 3y ago
For sure, Emacs with evil-mode is the best of both worlds: deep customization and sane configuration language of Emacs, with the arguably superior modal interface of Vim. Using mnemonic key bindings is much friendlier than dozens of random key combinations. There's a popular key-chord package[1] that minimizes this discomfort, but without editing modes, users need to be concerned with the chords clashing with their actual text, which is absurd. Modes address this issue gracefully. I still use some basic combinations like M-x, but I would be completely lost in Emacs if it weren't for evil-mode. <3 The thing with modal UIs is that you want to use them everywhere. So I also enable vi-mode in my shells, and in any application that uses readline. [1]: https://www.emacswiki.org/emacs/KeyChord https://www.emacswiki.org/emacs/KeyChord
- lawn 3y ago
  Honestly, configuring Neovim with Lua felt more sane than elisp for me.
- SKWR-PLS 3y ago
  This is pretty close to how steno [https://www.openstenoproject.org/ https://www.openstenoproject.org/] works in practice and worth learning IMO if you are going to go this far. In fact I have a few emacs-specific chords, but not as many as you might think. The whole experience is a bit like if emacs is now your keyboard, so it happens to go great with emacs. [1]
elcritch 3y ago
There's two VSCode vim plugins, one a native one and the other actually uses neovim. They're both pretty good. The main downside is that VSCode plugin can take some time to startup. I use the native one as it's a little less "pure" about VIM and integrates better with VSCode things. Overall it's less evil than evil. ;)

imiric 3y ago

For sure, Emacs with evil-mode is the best of both worlds: deep customization and sane configuration language of Emacs, with the arguably superior modal interface of Vim. Using mnemonic key bindings is much friendlier than dozens of random key combinations. There's a popular key-chord package[1] that minimizes this discomfort, but without editing modes, users need to be concerned with the chords clashing with their actual text, which is absurd. Modes address this issue gracefully. I still use some basic combinations like M-x, but I would be completely lost in Emacs if it weren't for evil-mode. <3 The thing with modal UIs is that you want to use them everywhere. So I also enable vi-mode in my shells, and in any application that uses readline. [1]: https://www.emacswiki.org/emacs/KeyChord https://www.emacswiki.org/emacs/KeyChord

lawn 3y ago
Honestly, configuring Neovim with Lua felt more sane than elisp for me.
SKWR-PLS 3y ago
This is pretty close to how steno [https://www.openstenoproject.org/ https://www.openstenoproject.org/] works in practice and worth learning IMO if you are going to go this far. In fact I have a few emacs-specific chords, but not as many as you might think. The whole experience is a bit like if emacs is now your keyboard, so it happens to go great with emacs. [1]

elcritch 3y ago

There's two VSCode vim plugins, one a native one and the other actually uses neovim. They're both pretty good. The main downside is that VSCode plugin can take some time to startup. I use the native one as it's a little less "pure" about VIM and integrates better with VSCode things. Overall it's less evil than evil. ;)