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