bug: lsp hover shows "no information available" twice about lazyvim HOT 8 CLOSED

This is what noice does (overwriting the LSP buffer handler) and you can use the option I mentioned earlier to silence those notifications. If you don't use noice, then you have to do something similar in your personal configuration on your own.

from lazyvim.

You must have multiple LSP servers attached to the buffer and not everyone has information about the symbol under the cursor. I noticed this when I had pyright and jedi and had disabled HoverProvider from pyright in favor of jedi. You can enable an option in noice.nvim to not show these messages. opts.lsp.hover.silent = true

For more info read noice's docs.

from lazyvim.

I think it's because of nvim-notify. Try disabling it and see if you observe same behavior.

from lazyvim.

without nvim-notify it prints twice to messages stack

and if I disable all plugins and extras and disable nvim-notify I see nothing at all on hover

but switching off nvim-notify is not an optimal solution here because nvim-notify is needed. Any js/ts buffer has at any given moment at least 3 lsp clients working at the same time to complete missing parts of each other, eslint + tsserver + cssls, so I am surprised that this is a an actual problem

from lazyvim.

Are you able to reproduce this with default LazyVim installation?

from lazyvim.

This is default behavior for Neovim vim.lsp.buf.hover(). See here where it is defined. It calls request, which is the function just above, which returns vim.lsp.buf_request(). That in turn is defined here and you can see from the comments that

--- Sends an async request for all active clients attached to the
--- buffer.

Since it sends the request to all active clients in the buffer, the ones that don't have information for the symbol under the cursor send back Information not available. If there are more than one server which doesn't have information available you will see more than one notification.

So, not a LazyVim bug it seems.

from lazyvim.

Noice does the same as the default lsp handler

from lazyvim.

@dpetka2001 thanks for checking

This resolves the issue for me for good

neovim/neovim#20457 (comment)

do you think this can be added to lazyvim as well?

from lazyvim.