Set `errorformat` for AsyncRun Strategy?

[stevenharman]

I'm still struggling to understand how vim-test and various strategies hang together, so forgive me I'm way off base. But... I'm using the AsyncRun strategy, and it works, but the errorformat used in the QuickFix window isn't correct. Specifically, if I use the Dispatch strategy, or even :Dispatch rspec directly, the QuickFix window is populated as I'd expect:

But when running with AsyncRun the Quickfix window looks like this:

I know for some other strategies vim-test calls dispatch#compiler_for_program to set the compiler, which also impacts the errorformat used. Is it possible to do something similar for the AsyncRun strategy?

This is possibly related to #145 and/or #220.

[janko]

I added finding the correct compiler before running AsyncRun, let me know whether it works for you.

[stevenharman]

@janko-m Hmm, that... did not work. The QuickFix is now broken:

It's like everything with any text at all is being filtered out. So I'm not sure what errorformat is being used. 🤷‍♀️

[janko]

Ok, I reverted that commit for now. The problem is that AsyncRun doesn't work for me at all, the quickfix never opens, even when there are test failures. I tried on both Neovim and Vim 8. So I cannot test whether a fix works or not 🤷‍♂️

[ezpuzz]

I have a similar problem where it looks blank but hitting on one of the blank lines actually goes to the error. workaround is :cclose followed by :copen. I don't know if it's asyncrun or what that is causing problems with errorformat parsing.

[ezpuzz]

@janko-m I think default behavior for asyncrun is not to open automatically, you have to call :copen or use their config to auto open it on output.

[jacobat]

I have this in my .vimrc:

" Open quickfix after AsyncRun
:let g:asyncrun_open = 8