4 ms·

There's a vscode extension that embeds NeoVim and just uses VSCode UI as a front end to delegate key presses to: https://github.com/vscode-neovim/vscode-neovim

There's a vscode extension that embeds NeoVim and just uses VSCode UI as a front end to delegate key presses to: https://github.com/vscode-neovim/vscode-neovim https://github.com/vscode-neovim/vscode-neovim This yields a better experience than the old half baked VSCode vim emulation.

faraazb 2y ago
This setup 'just' works for me. I have mapped certain functionality, for e.g. toggling the file explorer to a nvim keymap (the extension also enables h, j, k, l, y, p, etc. commands in the explorer) but I use the cmd/ctrl + P keymap for searching files in the current project, so it feels incomplete sometimes. When I am editing a set of files it works great, but as soon as I use a VS code feature, for e.g. project search, the experience is okay and may require a mouse, which is not surprising but I hope the integration gets even better. I am sure that with more configuration, the experience could be made more NeoVim like but I don't know whether I should spend time doing this or invest my time learning/adapting to a terminal based flow for the few tasks for which I am used to the VS Code GUI (browsing Git history, diffs for pull requests, git stash operations, debugging). I started with a base config (kickstart.nvim) after trying out LazyVim sometime back, but kept going back to VS Code for some of the tasks. So what I have now is not significantly better but I like it.
- wyclif 2y ago
  I tend to agree with this, but I went in the reverse direction. I started out with kickstart.nvim and moved to LazyVim when I saw what Folke was doing with it. It's an excellent config and rarely chokes on large files or breaks, even though the development is very rapid.
alabhyajindal 2y ago
I used this for a few months and went back to the vim emulator [1]. I can't recall what but some of the things kept breaking in Neovim. And the frequent, near daily extension updates were annoying. 1. https://marketplace.visualstudio.com/items?itemName=vscodevim.vim https://marketplace.visualstudio.com/items?itemName=vscodevi...
wyclif 2y ago
Why does this not work with VSCodium as well?
- pynappo 2y ago
  Doing a quick search in the repo i see multiple issues where people report using vscodium but none of them seem to report any immediate breakage. If you're experiencing a problem with it, it is only in vscodium?

faraazb 2y ago

This setup 'just' works for me. I have mapped certain functionality, for e.g. toggling the file explorer to a nvim keymap (the extension also enables h, j, k, l, y, p, etc. commands in the explorer) but I use the cmd/ctrl + P keymap for searching files in the current project, so it feels incomplete sometimes. When I am editing a set of files it works great, but as soon as I use a VS code feature, for e.g. project search, the experience is okay and may require a mouse, which is not surprising but I hope the integration gets even better. I am sure that with more configuration, the experience could be made more NeoVim like but I don't know whether I should spend time doing this or invest my time learning/adapting to a terminal based flow for the few tasks for which I am used to the VS Code GUI (browsing Git history, diffs for pull requests, git stash operations, debugging). I started with a base config (kickstart.nvim) after trying out LazyVim sometime back, but kept going back to VS Code for some of the tasks. So what I have now is not significantly better but I like it.

wyclif 2y ago
I tend to agree with this, but I went in the reverse direction. I started out with kickstart.nvim and moved to LazyVim when I saw what Folke was doing with it. It's an excellent config and rarely chokes on large files or breaks, even though the development is very rapid.

alabhyajindal 2y ago

I used this for a few months and went back to the vim emulator [1]. I can't recall what but some of the things kept breaking in Neovim. And the frequent, near daily extension updates were annoying. 1. https://marketplace.visualstudio.com/items?itemName=vscodevim.vim https://marketplace.visualstudio.com/items?itemName=vscodevi...

wyclif 2y ago

Why does this not work with VSCodium as well?

pynappo 2y ago
Doing a quick search in the repo i see multiple issues where people report using vscodium but none of them seem to report any immediate breakage. If you're experiencing a problem with it, it is only in vscodium?