Personally, my problem with trying to use Vim keybindings in VS Code is not about the motions of moving around/editing the code itself, but everything else. You end up in plenty of situations where you have to resolve using the mouse because you ended up on some sub-page or whatever, where you either need to resolve using the mouse or keep pressing Tab until you get to where you want to go. Installing plugins is one…
VSCode-Neovim: Use embedded Neovim in VSCode without emulation
21–30 of 112 posts
Re: VSCode-Neovim: Use embedded Neovim in VSCode without emulation
#22Personally, my problem with trying to use Vim keybindings in VS Code is not about the motions of moving around/editing the code itself, but everything else. You end up in plenty of situations where you have to resolve using the mouse because you ended up on some sub-page or whatever, where you either need to resolve using the mouse or keep pressing Tab until you get to where you want to go. Installing plugins is one…
perhaps onivim would be a good VSCode alternative for you, I think they have a mode like the browser vim extensions that labels everything on screen with a key you can press instead of clicking. https://onivim.io/
Re: VSCode-Neovim: Use embedded Neovim in VSCode without emulation
#23Personally, my problem with trying to use Vim keybindings in VS Code is not about the motions of moving around/editing the code itself, but everything else. You end up in plenty of situations where you have to resolve using the mouse because you ended up on some sub-page or whatever, where you either need to resolve using the mouse or keep pressing Tab until you get to where you want to go. Installing plugins is one…
perhaps onivim would be a good VSCode alternative for you, I think they have a mode like the browser vim extensions that labels everything on screen with a key you can press instead of clicking. https://onivim.io/
Re: VSCode-Neovim: Use embedded Neovim in VSCode without emulation
#24To me the greatness of using something like neovim/vim is that you don't have to use the mouse. This I don't know what's good for...
Re: VSCode-Neovim: Use embedded Neovim in VSCode without emulation
#25To me the greatness of using something like neovim/vim is that you don't have to use the mouse. This I don't know what's good for...
For something like editing text, as a programmer you do this endlessly - it is absolutely worth it to be ruthlessly efficient at this, even if you have to pay effort learning it.
But for, say, installing a plugin in your text editor... that's something you do a handful of times a month. The mouse is much more adaptable and easy to use, even if you give up accuracy.
This way, you can be efficient at editing text without having to learn keybindings for a bunch of misc things that you do rarely.
Re: VSCode-Neovim: Use embedded Neovim in VSCode without emulation
#26Re: VSCode-Neovim: Use embedded Neovim in VSCode without emulation
#27Re: VSCode-Neovim: Use embedded Neovim in VSCode without emulation
#28Would love to see if people have a good experience with this. The only thing keeping me on neovim is the ergonomics of my config. If I can have that, PLUS the discoverability of all the LSP features, hovering, consolidated error messages, etc. without it breaking all the time, I would switch in a heartbeat.
Re: VSCode-Neovim: Use embedded Neovim in VSCode without emulation
#29I used to use this before I switched away from VSCode for greener pastures. It was far and away the best option for vim editing. It’s great because you can still make use of any neovim plugins you have without needing extra VSCode extensions.
What are your greener pastures?
Re: VSCode-Neovim: Use embedded Neovim in VSCode without emulation
#30Personally, my problem with trying to use Vim keybindings in VS Code is not about the motions of moving around/editing the code itself, but everything else. You end up in plenty of situations where you have to resolve using the mouse because you ended up on some sub-page or whatever, where you either need to resolve using the mouse or keep pressing Tab until you get to where you want to go. Installing plugins is one…
Sounds like a minor annoyance at best... Where vim-mode is important to me is editing and navigating code, not when installing plugins...