Kiyan

I guess it could work, and it might actually be more efficient than custom implementations.

@alex-courtis

Thank you for doing this. I don't think neo tree copies nvim-tree code or tries to accomplish the same feature set, but since it's stated in the readme: > Everything...

A new one ? or this one ?

i will probably be away from the computer for the month of august, so i think we can start this discussion in september, this way if neo tree came up...

seems reasonable, thanks you can merge them if you feel they are correct, and they might not break something. I think it should be pretty calm during August anyway :)

thanks for the PR :) i think this was asked a lot by people, we could ask them to try it out. https://github.com/kyazdani42/nvim-tree.lua/issues/135

I agree we could merge a first version and improve on that. I'm not sure all the UX impacts that will raise. Closing the window when leaving it would also...

legacy migration (under the hood, automated): https://github.com/kyazdani42/nvim-tree.lua/pull/1476 NEEDS: `help shows on_attach mappings`, `document default mappings`

because you source your node_modules into version control ? I think you should start using #682 or disable the git management alltogether at this point. If the tree gets slower...