Closed KalenAnson closed 8 months ago
Checkout the v1.15 branch, I resolved this in #154 :)
v1.15 is still a bit buggy so until I have all the bugs worked out, I am not ready to merge it into main. But it does give some quality of life stuff like this, async read/write, actual notifications on failure to open stuff, os icons, etc.
I had planned on getting v1.15 merged into main by the end of this month but we will see. I keep finding more weirdness lol. I have had to completely re-write the neo-tree code so there is quite a few things changed under the hood
Solid, thanks again.
First of all, Mike - this is an amazing plugin. Well done man.
Context, I worked through getting neo-tree UI integration working with netman, so far life is good. I am predominantly using the ssh provider.
Not reporting a bug per se, so no logs atm.
This may be a feature request or something you perhaps you can easily point me to a proper solution, but when I close the neo-tree window and then attempt to reopen neo-tree with something like
:Neotree source=remote reveal
on the current file (say a file on a remote host with a path likessh://dev///home/user/myfile.txt
) I get the popup to change working directory (this is a neo-tree dialog), then afterwards, the neo-tree ui opens with no providers expanded and I need to work my way back to ssh > host > file.I did find (https://github.com/nvim-neo-tree/neo-tree.nvim/issues/645) which leads me to believe what I want is not easy.
Are you aware of a way to easily restore the neo-tree window state when I am viewing a remote file?
This one hangup is not stopping me from using the plugin, but it feels like a big quality of life thing I would love to figure out. Happy to help implement this if you can steer me in the right direction.