Neo-tree and ahmedkhalf/project.nvim how to make them work together? #728
Unanswered
CyrilPeponnet
asked this question in
Q&A
Replies: 1 comment 1 reply
-
|
I don't know if it will work or not, but based on the choices presented the correct choice for That will line up with how neo-tree manages the working directory. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hey guys,
I moved from nvim-tree to neo-tree and looks like the handle of cwd / tcd / lcd is not as smooth.
The "ahmedkhalf/project.nvim" plugin change the directory when loading a project and has the following options:
On the other side neo-tree have for filesystem source:
(and tbh I cannot understand the cwd target ones ;p)
So now here is the thing:
Given I have a file foo in project A (with its own root) and a file bar in a project B (different root).
If I use the bind_to_cwd to true, loading the file foo and open the tree will open the tree in the project A root dir. Now If I open the file bar from project B (invoking the project plugin) with the tree still open, the tree is properly "revealed" to tree B for a split second then goes back to the root A. If toggle the tree off and on again with force reveal flag it goes back to B but whenever I click on my buffer that contain the bar file from B the tree "refresh" to root A.
So far to have a behavior that pseudo work I need to disable the bind_to_cwd but in that case I need to manually refresh reveal the tree.
Is there a way to make it work properly with the settings above?
For now I have a hack like:
Thanks :)
Beta Was this translation helpful? Give feedback.
All reactions