Neovim

I want to preemptively start this thread to survey for suggestions. A cursory search lead me to this promising repository https://github.com/enigo-rs/enigo

Since closing the window is a common point of failure, that will be the focus for the first pass of testing as I learn how to use the library.

Components for testing:

• bridge
• editor
• renderer
• settings
• wind

We should make it easier to override the default sorters, since not every builtin currently respects the config flags.

First off, I just wanted to say a HUGE thank you to all of the maintainers of this project. Adding treesitter into my Neovim setup has elevated my daily development experience so much. I very much appreciate all of the hard work that has gone into this plugin and ecosystem to bring Treesitter support to Neovim!

I'm opening this issue to try and get some feedback/guidance on how to go about

For the longest time I was able to access the pry console while running tests using :TestNearest, but it hasn't been working of late. I am able to run tests using :TestNearest and the other vim-test commands. My issue is that if I throw in a binding.pry in the test, I don't see the pry console open up anymore in the test window. That used to work before, and I can't figure out why. I'm