Replies: 3 comments 2 replies
-
No, I don't think it's supposed to do that. Can you try with another client? https://helix-editor.com/ is modal and has out-of-the-box LSP support. |
Beta Was this translation helpful? Give feedback.
-
I assume neovim might report opened files as workspaces via lsp. I could imagine that causing issues like this because we then try to open the corresponding cargo project |
Beta Was this translation helpful? Give feedback.
-
I think I found a clue in the nvim-lspconfig repo: https://github.com/neovim/nvim-lspconfig/blob/5da57456597ac2f25f20d6ecfae7b7c9cbd01fc6/lua/lspconfig/server_configurations/rust_analyzer.lua#L41-L44 It looks like there is custom logic for reusing an instance... |
Beta Was this translation helpful? Give feedback.
-
I'm using neovim and a regular LSP setup but I'm getting diagnostics when I go to a definition within the standard library:
I noticed also that a new LSP instance is attached when I do this (with root dir
...../rust/library/core
). Is this supposed to happen?Did anyone encounter this problem as well?
Beta Was this translation helpful? Give feedback.
All reactions