Live data from Hacker News

VSCode-Neovim: Use embedded Neovim in VSCode without emulation

github.com

21–30 of 112 posts

Re: VSCode-Neovim: Use embedded Neovim in VSCode without emulation

#21

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…

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

#22

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…

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/

Onivim is no longer being developed :(

Re: VSCode-Neovim: Use embedded Neovim in VSCode without emulation

#23

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…

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/

Onivim development has stopped, it is now abandonware: https://github.com/onivim/oni2/issues/3811#issuecomment-9103...

Re: VSCode-Neovim: Use embedded Neovim in VSCode without emulation

#24

To 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...

Good for people who like the ergonomics of VSCode (one-click plugin installs, everything simply "just works" out of the box) with the ergonomics of Vim (modal editing, speed).

Re: VSCode-Neovim: Use embedded Neovim in VSCode without emulation

#25

To 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...

The advantage of Vim is efficiency and speed. The disadvantage is that it has a longer learning curve.

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

#27
I remember trying neovim with Atom a while ago. At that time I realized that me using nvim it's not just about motions/plugins/no mouse, etc, but rather the whole terminal experience. For example, I rely heavily on tmux for splitting my screen whichever way suits the current task best and then, I may spontaneously open nvim in some of the splits or run other CLI tools. This experience is not the same with the CLI built into vscode or any other IDE.

Re: VSCode-Neovim: Use embedded Neovim in VSCode without emulation

#28
post #3

Would 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.

FYI: LunarVim is a neovim config that integrates all the LSP and treesitter stuff. I've been using it for around 6 months now and am loving it. However, I'll admit that I went into it looking for a vim config that would allow me to ditch the vi configs I had been carting around for decades, including a lot of half working plugins, so I've tried to modify the stock LunarVim configs as much as possible. So it'll depend on how much of the ergonomics of your config is based on customizations, YMMV.

Re: VSCode-Neovim: Use embedded Neovim in VSCode without emulation

#29
post #8

I 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?

helix is pretty nice if you’re willing to challenge your traditional vim editing model. vim is action -> selection. helix is selection -> action. Beyond that helix feels like a modern vim. LSP natively supported. DAP as well. Very little configuration and bootstrapping to wade through.

Re: VSCode-Neovim: Use embedded Neovim in VSCode without emulation

#30

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…

>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.

Sounds like a minor annoyance at best... Where vim-mode is important to me is editing and navigating code, not when installing plugins...

Post reply on HN