3 ms·
You can do all that in VS Code with the vim extension. I'm with you on the vim keystrokes, but configuring debuggers, code completion, etc. in vim never seemed
by schnable 2y ago
You can do all that in VS Code with the vim extension. I'm with you on the vim keystrokes, but configuring debuggers, code completion, etc. in vim never seemed worth the effort. With VS Code and vim keybindings, it's the best of both worlds.
- ramses0 2y agoVS Code's vim extension is the _first_ non-vim implementation I've used that "has the Buddha nature". 1) macros 2) ctrl-w <hjkl> "does the right thing" with visual (IDE) window-splits(!!) I just about fell out of my chair when I stumbled upon <c-w> in a random vscode session (almost literally). Many editors pay lip service and think "if we stop at hjkl, that's good enough!" Even fewer make it to a rational macro implementation, but vim is so much more. The fact that vscode "does the right thing" when stabbed with <c-w> is incredible... now if only I could figure out how to get simplistic <c-p>/<c-n> to work with raw strings instead of trying to omni-complete...
- feketegy 2y agoThere is a Neovim plugin for VSCode that uses an embedded implementation of Neovim in the background that lets you use the full power of Neovim in VSCode, and even most Neovim plugins work too.