-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bug: No LSP client found that supports symbols #236
Comments
Hard to tell exactly what's happening from this description, but I found where some of the LSP logic could potentially disagree and cause a conflict. Can you try with this patch and see if it fixes it? If not, can you provide some more information? Things like
|
I'm still experiencing similar problem when using lsp backend with texlab ( some observations:
FYI here is the dump of the texlab client object:
|
The fact that it seems to still be working is the confusing part. That means that the active buffer continues to have a functioning LSP client with a symbols provider attached to it. The only thing I can think of is maybe something has caused aerial to try to attach to a different buffer somehow, and that buffer doesn't have a client. I've added the buffer number to the error message. If you see it again, can you confirm if the buffer number is the number of the current file? |
@stevearc Sorry for the late response. With latest commit, it shows a warning |
I have the same issue, but the problem only happens when use It is worth to note that when you use I think this might related to how we handle the detach event: aerial.nvim/lua/aerial/backends/lsp/init.lua Line 149 in 07039ea
Besides, I am on the latest commit 07039ea |
I find a way to "bypass" this bug: I find that if I commented out the change the config from this: require('aerial').setup {
backends = { 'lsp', 'treesitter', 'markdown' },
on_attach = function(bufnr)
bufmap(bufnr, 'n', '<leader>lo', '<cmd>AerialToggle!<CR>', {
desc = 'lsp symbol outline',
})
end,
}
to this require('aerial').setup {
backends = { 'lsp', 'treesitter', 'markdown' },
-- on_attach = function(bufnr)
-- bufmap(bufnr, 'n', '<leader>lo', '<cmd>AerialToggle!<CR>', {
-- desc = 'lsp symbol outline',
-- })
-- end,
}
then the warnings will not be yielded. |
I believe this is the same as #249, and is also fixed |
Neovim version (nvim -v)
v0.8.3
Operating system/version
MacOS 12.2
Output of :AerialInfo
Aerial Info
Filetype: go
Configured backends:
lsp (supported) (attached)
treesitter (supported)
markdown (not supported) [Filetype is not markdown]
Show symbols: Array, Boolean, Class, Constant, Constructor, Enum, EnumMember, Event, Field, File, Function, Interface, Key, Method, Mod
ule, Namespace, Null, Number, Object, Operator, Property, String, Struct, TypeParameter, Variable
Describe the bug
It sometimes show the warning "No LSP client found that supports symbols" when I opened a ".go" file.
But the LSP of golang is attached, and the aerial is working well in the same buffer.
:LspInfo
Steps To Reproduce
I don't know.
Expected Behavior
Do not notify this warning.
Minimal example file
No response
Minimal init.lua
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: