-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LspInfo reports Running in single file mode
when current buffer is not in root_dir
#3167
Comments
it outside of the root then it run in single file mode what's the problem ? |
Client itself is not outside of the root dir, but it's wrongly reported as such. The problem is wrong info reported by All those servers are not running in single file mode. They all have its own root_dir. So it's strange to report it like this. Compare it to this: I just switched buffer, nothing else changed. Now Checkhealth (all clients has root_dir):
|
I remeber there has a problem after i add workspace relate stuff see #2648 I will check it later. |
Could you reopen for the time being? It's not urgent, but so that it's not forgotten completely. |
Description
When active buffer is outside of
root_dir
LspInfo
reports root directory asRunning in single file mode
.Steps to reproduce
minimal_init.lua
:nvim --clean --noplugin -u minimal_init.lua
. One buffer is active.:LspInfo
. Root directory:/tmp/lspinfo_repro.9qkBbS
.:edit /tmp/lspinfo_repro
.:LspInfo
. Root directory:Running in single file mode
.:buffer #
.:LspInfo
. Root directory:/tmp/lspinfo_repro.9qkBbS
.9qkBbS
to your case)::e /tmp/lspinfo_repro.9qkBbS/1234
.:LspInfo
. Root directory:/tmp/lspinfo_repro.9qkBbS
.LspInfo
again reports root directory as single file.The text was updated successfully, but these errors were encountered: