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
consult-lsp--file-symbols-candidates: No symbols #33
Comments
Hello, It looks like your LSP server either hasn't been started, or that it cannot deal with the current file. Cheers |
@gagbo, thanks for the quick reply. I used pyright python language server and it works well with Does |
No, there are 2 calls,
I didn't check the protocol in a while to see if it changed, but theoretically that should not be a problem, so somehow pyright doesn't want to answer the documentSymbols call it seems |
just today I noticed I'd get the same error (with a language server that definitely returned symbols), but in my case it was because |
All good points, it's indeed more likely that the heart of the issue is the use of |
Both issues should be fixed now with the commit above ^. I also tagged it so eventually it'll also hit MELPA stable for the mad lads who trust it. Don't hesitate to comment if that doesn't work |
when I run consult-lsp-file-symbols, it showed no symbols. but I got right infos with consult-imenu.
consult-lsp-file-symbols has a big advantage to consult-imenu due to the narrowing mechanism. I really hope this command could run as expected. thx.
The text was updated successfully, but these errors were encountered: