Alexander Courtis

Tested on linux zsh but not windows.

## neo-tree ### Playing It has feature parity with nvim-tree plus: 1. fugitive style git manipulation mode `:Neotree source=git_status` 1. file nesting rules It lacks a little polish e.g. `:NeoTreeClose`...

> I think i'd like to make some performance analysis between the plugins, because the only reason i wrote nvim-tree in the first place was because nerd tree was too...

## Stability We have achieved stability both when adding features and making fixes. We have greatly improved over the last few months and we are good at it. I don't...

> If i test, i usually go with tdd Agreed. Retrofitting is always difficult when functions are not built for test. > I use tested and not tested neovim plugins,...

> i think we should have a talk with the maintainer Yes. Understanding the author's motivations would be of great assistance. Are you happy to open the conversation?

A conversation with the neo-tree author. Perhaps we could discuss: * Motivation for building neo-tree rather than collaborating on nvim-tree * Future plans for neo-tree: features and internal enhancements *...

> 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...

@archiif your testing would be gratefully appreciated.

> does this change means that nvim-tree will not find file in symlink directories ? I think we should only prevent looping indefinitely right ? I recall that it did....