Replies: 1 comment 5 replies
-
Delete opts from Mason lspconfig line it causes it to setup jdtls before nvim-java and see #293 and #399 |
Beta Was this translation helpful? Give feedback.
5 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi, I've recently switched from
nvim-jdtls
tonvim-java
(and from Telescope to FzfLua for better presentation) and for some reason LSP document symbols just does not work, FzfLua says[Fzf-lua] LSP: server does not support textDocument/documentSymbol
. It did work withnvim-jdtls
. Workspace symbols do work correctly, but I had to disablespring-boot-tools
because this plugin's output is clearly meant to be used with some other tool and not FzfLua. Document symbols also work for other languages, for example Lua. Everything else I've tried so far (completions, debugging, running JUnits etc.) also works, just not document symbols. It's not a very big deal, but would be helpful when working in codebases with Java files going into thousands of lines.I've tried some print debugging and found that
:lua print(vim.lsp.get_clients({name="jdtls"})[1]:supports_method("textDocument/documentSymbol", 3))
printsfalse
, but if I try:lua vim.print(vim.lsp.get_clients({name="jdtls"})[1])
it gives me this, which does not make sense for me:My setup, some paths redacted. Neovim is installed via AppImage:
OS default Java:
My lspconfig loaded with lazy.nvim, written from scratch from various guides, not a distribution:
Output of
:LspInfo
on any random Java code after everything is loaded and built:And
ftplugin/java.lua
:Beta Was this translation helpful? Give feedback.
All reactions