Iron-E

I just tested neo-tree. It seems that there is some strange behavior with that plugin specifically— it seems to be deleting buffers. Removing [these lines](https://github.com/nvim-neo-tree/neo-tree.nvim/blob/v2.x/lua/neo-tree/ui/renderer.lua#L899-L904) specifically seems to make this...

I think I linked the wrong place, sorry. I have set up a fork which works for me

You should source the fork in your config and try to reproduce this issue.

> Are you implying the fork you set up? Yes. It is [here](https://github.com/Iron-E/neo-tree.nvim)

That makes sense. I created my fork just to confirm that the problem wasn't in the barbar.nvim code, but a precise line of code in neo-tree. To get this fixed,...

I only had to deviate from the plan in one area: the `render` module ended up becoming so large that I needed to split out the high-level functions into a...

Would you mind separating out `BufferMoveStart` into a separate PR? I'd be happy to merge that while looking at the specifics of your bug report.

> The best solution is to make sure that neo-tree is not active the window before opening a buffer. Unfortunately, his use case is opening files from the tree rendered...

Since the original author hasn't responded in a while, I'm going to close this as stale. It can always be reopened later.

Coming here from #1766. The description for `excludeSearchPatterns` and `systemExcludeSearchPatterns` is: > Used to define which directories and files should not be included in OmniSharp's file scanning/discovery process. I feel...