search

equalsraf / neovim-qt

Neovim client library and GUI, in Qt5.
https://github.com/equalsraf/neovim-qt/wiki
ISC License
1.85k stars 171 forks source link

nvim-lspconfig not working with neovim-qt #932

Closed Cloudperry closed 3 years ago

Cloudperry commented 3 years ago

So nvim-lspconfig doesn't work with neovim-qt and it works just fine in terminal neovim. This can be easily checked by running :LspInfo in neovim and neovim-qt. In terminal neovim it doesn't error and in neovim-qt it errors with: E5108: Error executing lua . . .nvim/plugged/nvim-lspconfig/lua/lspconfig/ui/windows.lua:106: Invalid key 'border'

This also causes autocomplete with nvim-cmp and built-in lsp to not work. I tried this with both neovim and neovim-qt fresh from git and it doesn't change anything.

jgehrig commented 3 years ago

@Cloudperry

I cannot reproduce this issue (Linux or Windows). Since this is a plugin, could there be a configuration issue or conflict?

It would be helpful if you can provide a minimal.vim and set of instructions that reproduces the issue.

You can load mininal.vim with the command: nvim-qt -- -u minimal.vim.

Cloudperry commented 3 years ago

Yeah this is a weird one. I tried making a minimal config to reproduce this, but then I can't reproduce it. I will start looking into my normal init.lua to see what causes this.

Edit: It doesn't happen when running neovim-qt through terminal instead of running it using the .desktop shortcut. Maybe my environment is somehow messed up, but idk how it could be because my terminal is just fish shell in konsole. I haven't set any environment variables for fish specifically and my login shell is bash. Also this doesn't happen when running other Neovim GUIs through .desktop (tested neoray and neovide).

jgehrig commented 3 years ago

This sounds like a configuration issue...

One long-shot idea:

Try running nvim-qt -- somefile.txt from your terminal. Our desktop shortcut is a little weird and opens files by passing them as arguments to nvim. I don't see how this would impact the scenario, but it is a possible difference between the cases.

Cloudperry commented 3 years ago

Sorry for this "bug" report. I found what the configuration issue was. I just had a too old nvim-qt version (some nightly of 0.5). I was using the appimage earlier and after I switched to the Arch package for nvim-qt I still had the shortcut for the appimage. So I was just using the old appimage version without noticing.

The latest version works normally.