• moreeni
    link
    fedilink
    arrow-up
    2
    ·
    edit-2
    1 month ago

    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

    • MajorHavoc@programming.dev
      link
      fedilink
      arrow-up
      3
      ·
      1 month ago

      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.

      • moreeni
        link
        fedilink
        arrow-up
        2
        ·
        1 month ago

        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 😅