BUG: Re-opening any file lefts `untitled` buffer opened

[Rid1-fz-06]

BUG: Re-opening any file lefts `untitled` buffer opened

[cseickel]

This is not a neo-tree responsibility at all, it is a built-in behavior of neovim to have an an empty buffer when no other buffer is open. If you wanted neovim to close after deleting the last buffer, you should use a "quit" command instead of a delete buffer command.

[Rid1-fz-06]

@cseickel I didn't mean that. I don't want to close neovim. Yes, neovim will always create an empty buffer when there is no buffer opened. But when I open any file from neo-tree (when there is no buffer opened but the empty Untitled buffer), neo-tree should have closed that empty Untitled buffer (not neovim), and open the file I tried to open. In other words, that Untitled buffer should be replaced by the file's buffer I was trying to open.

[Rid1-fz-06]

@cseickel this doesn't happen if I open any file first time after opening neovim. It only happens when I close that file, and try to re-open that file.

[cseickel]

neo-tree should have closed that empty Untitled buffer (not neovim), and open the file I tried to open. In other words, that Untitled buffer should be replaced by the file's buffer I was trying to open.

Sorry, but I don't agree with that statement at all. Neotree does not and will not close any buffers when you open a new one. It just issues the :edit <filename> command.

[Rid1-fz-06]

@cseickel I found that this issue is still there if I use the :edit command. It is not a bug of neo-tree. Sorry for wasting you time sir. Thanks