[patleeman]

I recently forced myself to learn vim motions and it's been paying off pretty well. Once it clicked I found myself wanting vim motions everywhere.

I went deep and set up a neovim config, forcing myself to use neovim full time. However my new role requires me to use Intellij and I didn't want to spend hours upon hours figuring out how to replicate the java support in Neovim (and no, it isn't just installing the LSP, my work has some pretty specific intellij setup).

At this point I'm just using Intellij and VSCode with their respective vim plugins and I'm getting about 80% of the utility that I did with pure neovim. The one thing I really love about neovim is that it really forces you to keep your hands on the keyboard and you learn the keybinds very well because otherwise you just can't do the thing you wanted to! I find myself using the mouse a lot in VSCode and Intellij because they give you really handy buttons to click on.

I could probably go pure keyboard if I just sat down and learned all the various keybinds, but who has time for that?

[LargeTomato]

The VS Code vim bindings are too slow, incomplete, and they conflict with VS Code's other keybindings. I had to disable VS Code vim mode.

[roblh]

Have you tried the neovim plugin instead of the regular vim one? I find they have different trade offs, but the neovim one is actually using neovim inside a vscode window and requires a neovim install.

Particularly, I’ve found the undo functionality to be far better with the neovim one, it never screws up. Holding alt and moving a line up and down can sometimes accidentally move your cursor one line higher or lower though.

[capableweb]

Biggest personal issue with VS codes vim mode is that it only works in the text editor. The beauty of vim/neovim is that the keybindings work everywhere in the UI, not just the text edit window.

[patleeman]

Yeah, this is the biggest thing I miss from neovim.

[hinell]

I basically had to disable entire VS Code. Didn't remove it yet and keep it just in case I need to remember how crappy it's. It has some advantages over neovim though, but they don't outhweigh neovim.

[localghost3000]

For IntelliJ, check out what you can do with the .ideavimrc file. You can turn pretty much anything into a vim motion and it has light plugin support as well. Also makes your setup portable.

[patleeman]

Yeah, I've been meaning to spend more time on it, but I've been switching around to different editors a lot lately, so the constant jumping around means I'm trying to keep my vim keybinds as vanilla as possible.