Skip to content

bug: no lsp document symbols are found #88

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

Open
3 tasks done
bsolar17 opened this issue Apr 2, 2025 · 0 comments
Open
3 tasks done

bug: no lsp document symbols are found #88

bsolar17 opened this issue Apr 2, 2025 · 0 comments
Labels
bug Something isn't working

Comments

@bsolar17
Copy link

bsolar17 commented Apr 2, 2025

Did you check docs and existing issues?

  • I have read all the plugin docs
  • I have searched the existing issues
  • I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)

v0.11.0

Operating system/version

MacOS 15.4
Debian 12

Describe the bug

Using nvim-java no lsp document symbol is found. By manually configuring nvim-jdtls I noticed the lsp does provide document symbols in that configuration.

I tinkered a bit with nvim-java-core and removing this line makes lsp document symbols appear:

clientDocumentSymbolProvider = true,

Image

I'm not sure what clientDocumentSymbolProvider = true does though so I don't know what the full consequences of removing that line are.

Steps To Reproduce

  1. Install nvim-java.
  2. Open a Java file.
  3. Try to open document symbols, e.g. through fzf-lua's builtin lsp_document_symbols.

No lsp document symbol will appear.

Expected Behavior

Lsp document symbols are expected to be found and displayed.

Removing the above mentioned line leads to the expected behaviour but I don't know of possible side-effects as I don't fully understand what the line does.

@bsolar17 bsolar17 added the bug Something isn't working label Apr 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant