VSCode-Neovim: Use embedded Neovim in VSCode without emulation
1–10 of 112 posts
Re: VSCode-Neovim: Use embedded Neovim in VSCode without emulation
#2I 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.
Re: VSCode-Neovim: Use embedded Neovim in VSCode without emulation
#3Would 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
#4I don't use VSCode, but if you use this plugin or the other Vim plugin for VSCode, make sure to put it in its own thread so it doesn't compete with other blocking tasks and slow down your editor motions.
See "Affinity" docs here for putting it in its own thread: https://github.com/vscode-neovim/vscode-neovim#installation
Re: VSCode-Neovim: Use embedded Neovim in VSCode without emulation
#5Would 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.
Been using it for a couple of years. No problems.
You don't get the "absolute fullest" (neo)vim experience because you don't get the buffers/panes like you do in nvim though.
Re: VSCode-Neovim: Use embedded Neovim in VSCode without emulation
#6Does that mean that I don't have to learn how to use VScode at all ?
Re: VSCode-Neovim: Use embedded Neovim in VSCode without emulation
#7Personally, 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 good example of this, where even if you use a Vim plugin (or this, it seems), you still need to resolve to using the mouse/Tabbing to actually install the plugin itself.
While with Neo/Vim itself, you never need to reach for the mouse, because the entire thing, not just the editing/writing, is meant to facilitate keyboard-only usage.
Re: VSCode-Neovim: Use embedded Neovim in VSCode without emulation
#8I 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
#9I don't use VSCode, but if you use this plugin or the other Vim plugin for VSCode, make sure to put it in its own thread so it doesn't compete with other blocking tasks and slow down your editor motions. See "Affinity" docs here for putting it in its own thread: https://github.com/vscode-neovim/vscode-neovim#installation
This must be a new option, hadn't seen it before. Thanks!
Re: VSCode-Neovim: Use embedded Neovim in VSCode without emulation
#10Would 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.
I find that on the whole it's much speedier, albeit a tad buggier, than the “official” vim extension. I think in another year it will be more or less perfect.
If you're talking about keeping your Neovim config: yes, due to the Neovim extension using the actual Neovim program (this was one of the new Neovim features: it includes a vim server that processes keystrokes and sends updates for use in a different UI). So it has no problem reading your vim config at startup.