You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On windows, when I use LSP go to definition in another directory, the root of nvim-tree changed to that directory, even when the destination directory is a sub-directory of current directory.
With some debug message, I found the path passed from LSP is not normalized. The "c:" is lower case, while other place uses upper case drive identifier "C:". So the path_relative function doesn't return as expected.
Uh oh!
There was an error while loading. Please reload this page.
Description
On windows, when I use LSP go to definition in another directory, the root of nvim-tree changed to that directory, even when the destination directory is a sub-directory of current directory.
Neovim version
Operating system and version
Windows 11
Windows variant
Command Prompt
nvim-tree version
82ab19e
Clean room replication
Steps to reproduce
Expected behavior
The root of nvim-tree doesn't change frequently if the directories are in the same project.
Actual behavior
root of the nvim-tree windows has changed
The text was updated successfully, but these errors were encountered: