3 ms·
It's not like you have to give up Vim anyway considering the good-enough VSVim plugin gives you most of the Vim basics. Personally I have found JetBrains' Vim p
by cutler 6y ago
It's not like you have to give up Vim anyway considering the good-enough VSVim plugin gives you most of the Vim basics. Personally I have found JetBrains' Vim plugin to be the best.
- theCodeStig 6y agoI've tried vim support extensively in VSCode, IntelliJ, and Emacs. The vim plugin for VSCode is sorely lacking; particularly with macro support. For my use case, it's unusable. The vim plugin for IntelliJ is slightly better. It's usable, but I still find it lacking. In my experience, the best (by far), is Evil for Emacs.
- cutler 6y agoI think it's unrealistic to expect a plugin to provide macro support.
- macinjosh 6y agoIf you use vim to its utmost a plugin that emulates vim in another editor pales in comparison. It is like learning to play an instrument. Some people stop digging into it when they learn to play a few tunes but the true beauty comes out when you really invest the time into it.
- scruple 6y agoI used VsVim for a number of years and felt the same way. Eventually, I was back in vim full-time (moved on from the projects/team that required Visual Studio). I've spent the last year migrating to neovim. I've spent the last month getting into some C# development and the VS Code neovim integration is very well done. It's not the same, and I will not be switching to VS Code for anything other than this C# work (for the foreseeable future, I just really like neovim...), but it's not an emulation layer (with this plugin the VS Code editor is a neovim instance in the backend) and it doesn't feel like one, either.