You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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
Install nvim-java.
Open a Java file.
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.
The text was updated successfully, but these errors were encountered:
Did you check docs and existing issues?
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:
nvim-java-core/lua/java-core/ls/servers/jdtls/config.lua
Line 14 in 401bf76
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
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.
The text was updated successfully, but these errors were encountered: