Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

VSCode-Neovim: Use embedded Neovim in VSCode without emulation

github.com

Post reply on HN
Print view View original

91–100 of 112 posts

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

#91

Post by tuukkah »

lanza wrote: post #70
coldtea wrote: post #30

Earlier quoted context omitted.

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

It's not just installing plugins. It's the VCS view, the symbol list, the terminal, the file browser, the search pane, the debugger pane, any pane added by any extension, etc.

> the terminal

Ctrl+`

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

#92

Post by jatins »

Could be Baader–Meinhof phenomenon but I feel like Vim is having a resurgence due to lots of streamers and youtubers using it.

I personally started using Vim bindings in VSCode recently due to wrist pain issues and have been geeking about it a bit. Though there is still a fair bit of cognitive overhead for basic editing operations that were second nature previously.

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

#93

Post by typon »

jchook wrote: post #74

This seems like a lot of work to ultimately have a Frankenstein monster. Just use NeoVim. Name one reason why you need VSCode.

* If you want 50ms latency on every interaction with the editor * If you want to send telemetry to Microsoft * If you want slow fuzzy search for massive codebases

Plenty of reasons

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

#94

Post by WirelessGigabit »

capableweb wrote: post #7

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…

If only there was some sane oob setup for neovim with decent file exploring, and debugging.

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

#95

Post by bradwood »

thegeomaster wrote: post #34
doomrobo wrote: 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.

Have you tried coc.nvim? I was in the same boat as you, trying to painlessly move away to a different editor with Vim keybindings or such, because I just couldn't get LSP stuff to work without constantly breaking. Since I started using Coc, it all just works magically, I just need a `:CocInstall` if I'm working in a new language.

This. I've been all over Coc since it showed up. It's pretty good. So much so that I've not yet even bothered to look at the native support that came later.

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

#96

Post by bradwood »

barefeg wrote: post #18

I love neovim but I don’t have a good replacement for the git plugin of vscode. I haven’t found my way to replicating that experience in neovim. I tried lazygit but I find the diff viewer hard to understand and navigate. Diff view ( https://github.com/sindrets/diffview.nvim ) might be it, but I haven’t made the time to install a newer version of git from source (Debian…)

Have you tried Fugitive?

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

#98

Post by SoraNoTenshi »

toastal wrote: post #80
dcow wrote: post #29

Earlier quoted context omitted.

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.

What does that shift in paradigm give you over Visual Mode in Vim?

My 2 cents to this as a helix user.

1. it's just nice to see your selection before u do any action.

2. There's not benefit to the new model, either you like it more or like it less, why does everything have to give a benefit? Maybe it's just about the preference.

3. Helix requires less than 50 Lines of TOML to configure, to me this is well worth it, as with neovim, i easily needed like ... 300 Lines of Lua code? Something like this.

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

#99

Post by LinXitoW »

krono wrote: post #68
fire wrote: post #37

My biggest complaint is probably that it doesn't support overlay or popup windows, which makes it impossible to use plugins like WhichKey[0] and such, which I like on normal neovim because I'm a scrub and don't know vim hotkeys by heart 0: https://github.com/folke/which-key.nvim

Whenever I didn't know how to do something or suspected there'd be a far more efficient way to go about it, I'd look up the magic words or keys to use and write them down. Limiting this cheatsheet to just one side of an A4 sheet kept it usable and forced me to rewrite it every so often - every next iteration leaving off all the commands I had been checking back often enough for that they had finally stuck. Completely…

The beauty of the whichkey/space menu is that you can both learn shortcuts AND find new ones (they're grouped by domain) AND find old shortcuts you rarely use.

It's the antidote to most sophisticated editors worst problem, that there's a bajillion commands scattered around a million menus, many of which are not even remotely intuitive.

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

#100

Post by rendall »

Ok, I tried this out. Setup is a bit of a chore but not difficult, mostly making sure that the correct version of neovim (> 8) is installed. I have only one bit of feedback, but for some reason it's a deal-killer for me.

Vim is my go-to text editor and VS Code with vim emulation is my go-to IDE, so I was excited to try.

The vim emulator puts the `:` command in the status bar on the lower left, quite like vim itself does. Type `:w` and you see that in the status bar.

By contrast,the way that command `:` is handled in the embedded neovim extension is that a search window pops up at the top where the commands and files drop-downs are (same place that gets the cursor when hitting ctrl-p). This confused and dismayed me so much that I immediately noped out, disabled the extension and went back to using the emulator. It might also have been dismaying that `w` was not one of the listed commands, only `wq` which is not what I wanted. `w` did work, but I was done.

I probably could get used to it, but I'm inclined to jettison things that mess with what I'm used to unless there's a massive value-add. As for now, I pretty much only use vanilla vim and so the emulator is good enough. When I need more power, I open vim either in a separate terminal or sometimes right in the VS Code embedded terminal. I don't really have an intense need for real neovim in VS Code at this point.

Finally, I do want to give props to the creator! This is an amazing accomplishment, and I hope that my feedback is not discouraging! If there could be a setting to reflect the commands in the status bar as the vim emulator does, I will be eager to try it out again. But still, great job!

Post reply on HN