Closed perrin4869 closed 1 year ago
Thanks for the report. Well, I'm not sure but it seems Neovim accidentally enables LSP features on a virtual file (suda://...
) even Neovim cannot handle it. So it's a kinda Neovim's runtime issue I guess.
Yeah feel free to close this if you don't consider this a suda issue. But to be fair, lsp should be enabled in that virtual file, even if it's not writable you can jump to definition, etc
But to be fair, lsp should be enabled in that virtual file, even if it's not writable you can jump to definition, etc
Yes but only when Neovim's LSP itself supports a virtual file handling I think.
This has been a long-standing issue of mine, which I finally got around to troubleshooting I've been using
suda_smart_edit = 1
because it is extremely useful when editing system files However, I noticed when doingscala
development, whenever I would usevim.lsp.buf.definition
to a dependency file, I would get an error (this happens onneovim
0.8.1, but also happens on everyneovim
version I can remember):Running buffers returns:
Since I noticed the buffer was renamed to
suda:///
, I tried disabling the plugin, and the problem was solved. You can probably reproduce this by doingvim.lsp.buf.definition
which would result in opening areadonly
file on any lsp server, this is not specific to scala (but probably common in scala due tometals
creating readonly dependency files). I really don't have much of a clue how this could be solved, but I thought I'd report it