Open chipsenkbeil opened 2 years ago
Now that I know what the error is, this might be more relevant to file against neovim itself? I'm not sure what the fix is, unless there's something neovim or nvim-lspconfig is doing to garble the path before sending it to the LSP server.
this might be more relevant to file against neovim itself?
I think so.
I'm guessing that the mounted path is actually a network path on Windows. \\Mac\Home
is a specific directory mounted into my VM using Windows networking. So my guess is that any network path is going to fail with neovim. I tested both rls
and rust-analyzer
on VS Code using my network path and they work, so it is possible to have a language server work with a network path! 😄
nvim version 0.9.2
I've encountered the same issue on windows 10 while using nvim-tree
since it always resolves the filepath as UNC
Description
I originally filed this issue against
rust-tools.nvim
, but realized it affected all language servers: https://github.com/simrat39/rust-tools.nvim/issues/205.The gist is that I'm running Windows within my Mac using Parallels and mounting a directory from my Mac onto the Windows machine.
The path is
\\Mac\Home\projects\distant
for my Rust project, which isn't a traditional path likeC:\path\to\distant
. I'm making the assumption that the path is what is causing the issue, otherwise there's some problem with the mounted directory. I can compile my code, run it, and open files within neovim for highlighting with treesitter without issue.Error found within lsp.log
Seems like language servers, at least
rust-analyzer
andsumneko_lua
, don't like the path and give this error:Mac
Attaches to the buffer without issue.
Windows (failing)
Seems to detect that a server is available, but does not attach. Also there are extra fields in
:LspInfo
than I was expecting.Windows (succeeding)
If I clone the repository within my VM, this works without issue.
Neovim version
Nvim-lspconfig version
No response
Operating system and version
Windows 11
Affected language servers
all
Steps to reproduce
With a minimal config used, the client exits
Actual behavior
LSP client is not created and does not attach to the buffer
Expected behavior
LSP client starts and properly attaches to the buffer.
Minimal config
LSP log
https://gist.github.com/chipsenkbeil/964321062669031f4fa5ec33c91e427a