Woah, that’s pretty cool! i installed an extension for vim keybindings inside VS Code recently, as I find them very powerful. Unfortunately, I rely on VSC’s plugin ecosystem and thus can’t fully switch over to neovim, but I’ve liked it so far for everything else I do on my system, like writing bash scripts.
I’ve had issues with that one because I’m using VS Codium flatpak. I’ve exposed system binaries and the extension found the nvim binary, yet it kept erroring out with the message that Nvim was disconnected. VSVim is better in that regard for my case, because it is a stand-alone extension.
I saw an error like that, too. (Also with the flatpak.)
I want to say I had an error in my init.vim that was the underlying cause, and the error message cleared up once I had that fixed. I also had to make sure both executables were on my path, and I had to correct where the NeoVim plugin was looking for Nvim, as well, in settings.json.
I didn’t have any errors in the init.vim file because I didn’t have any. I added an example init.lua file with contents from here and configured the extension to pull this config file, yet it still says Nvim disconnected each time I restart it. I just gave up and resorted to VSVim
That makes sense. Did you also set the path to Nvim in settings.json? I had to do so to clear at least one error.
I also sometimes get that “disconnected” error too, but the have it work fine. I think there’s a race condition and it raises the error right after it starts, but then connects anyway, once everything else is set.
Did you also set the path to Nvim in settings.json? I had to do so to clear at least one error.
Yup. I set it to /run/host/usr/bin/nvim after exposing system libraries and binaries to VS Codium through KDE’s flatpak permission manager. Prior to that it kept throwing me ENOF errors (or something like that, I don’t remember now).
Unfortunately, that “disconnected” error is either not caused by a race condition for me or I was really unlucky, because at some point I restarted the extension 30 or some times out of frustration and nothing changed 😅
I know plenty of people that use vim/neovim for web development. I am also one of them
Woah, that’s pretty cool! i installed an extension for vim keybindings inside VS Code recently, as I find them very powerful. Unfortunately, I rely on VSC’s plugin ecosystem and thus can’t fully switch over to neovim, but I’ve liked it so far for everything else I do on my system, like writing bash scripts.
If you’re feeling bold, check out the NeoVim VSCode plugin. It’s delightful.
It’s essentially the VSCode remote plugin, but connecting to the NeoVim back-end.
It gives all the functionality of NeoVim along with all the functionality of VSCode.
Also, annecdotaly, it’s substantially faster than the VSVim plugin.
I’ve had issues with that one because I’m using VS Codium flatpak. I’ve exposed system binaries and the extension found the nvim binary, yet it kept erroring out with the message that Nvim was disconnected. VSVim is better in that regard for my case, because it is a stand-alone extension.
I saw an error like that, too. (Also with the flatpak.)
I want to say I had an error in my
init.vimthat was the underlying cause, and the error message cleared up once I had that fixed. I also had to make sure both executables were on my path, and I had to correct where the NeoVim plugin was looking for Nvim, as well, in settings.json.I didn’t have any errors in the
init.vimfile because I didn’t have any. I added an exampleinit.luafile with contents from here and configured the extension to pull this config file, yet it still says Nvim disconnected each time I restart it. I just gave up and resorted to VSVimThat makes sense. Did you also set the path to Nvim in settings.json? I had to do so to clear at least one error.
I also sometimes get that “disconnected” error too, but the have it work fine. I think there’s a race condition and it raises the error right after it starts, but then connects anyway, once everything else is set.
Yup. I set it to
/run/host/usr/bin/nvimafter exposing system libraries and binaries to VS Codium through KDE’s flatpak permission manager. Prior to that it kept throwing me ENOF errors (or something like that, I don’t remember now).Unfortunately, that “disconnected” error is either not caused by a race condition for me or I was really unlucky, because at some point I restarted the extension 30 or some times out of frustration and nothing changed 😅