`binding.pry` not working anymore

[ashwinvidiyala]

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 also using vim-dispatch if that matters.

Any help would be greatly appreciated :)

[ioanniswd]

Having same issue, tried adding let g:test#preserve_screen = 1, but it did not help.

[janko]

The problem is most likely in vim-dispatch, I suggest you try to verify that by trying to use vim-dispatch directly.

[ioanniswd]

Tried it directly with :Dispatch ./bin/rspec % and it does pause for a while before dissappearing. However, modifiable is off, I can't do anything. Moving to vim-dispatch.

[ioanniswd]

tpope/vim-dispatch#294

[ioanniswd]

This is tpope's answer:

The solution is to use :Spawn instead of :Dispatch. If you have a default b:dispatch configured, :0Spawn will use it automatically. I don't know if vim-test provides a mechanism for this.

[janko]

vim-test doesn't have that option at the moment, but we could add a config variable. It should be an easy PR, the test#strategy#dispatch function is in autoload/test/strategy.vim.

[ioanniswd]

I added the config variable. However, the behavior is that of the basic strategy. Should I create the PR so that you can have a look and tell me if I am on the right track? Or perhaps dismiss it altogether if it is identical to the basic strategy?

[janko]

I was thinking that we instead add a variable that makes the existing Dispatch strategy execute the Spawn command. I genererally prefer the strategy = plugin philosophy.

You can send a PR with this.

[ashwinvidiyala]

Is there any update with this guys?

[ioanniswd]

To be honest, I was using these commits -> 16a005f, 3592eff as an example.
Do you mean something like this:

function! test#strategy#dispatch(cmd) abort
  if b:dispatch_command == 'spawn'
    execute 'Spawn '.a:cmd
  else
    execute 'Dispatch '.a:cmd
  endif
endfunction

Or do you mean to pass it like an argument to test#run?
Should I also do the same for the dispatch_background strategy, which appears to have its own strategy even though it is part of the same plugin?

Also, as I mentioned above, the Spawn command seems to behave the same way as the basic strategy. Not sure if it makes sense to implement it.

[janko]

If Spawn behaves the same way as the basic strategy, I don't think there is a need to add support for it in vim-test, as people could just use the basic strategy instead. Doesn't the test command output still get parsed into a quickfix list on test failures with Spawn?

[ioanniswd]

No it doesn't. And Copen doesn't open the quickfix list either. Not sure if I misunderstood something. Perhaps @tpope can clarify this.