Dispatch does not work with ruby interpreter, works for rspec about vim-dispatch HOT 5 CLOSED

I have the same problem, but with rspec too. :Dispatch works inside a rails project, when running the specs with Zeus (e.g. :Dispatch zeus rspec --color spec/models/user_spec.rb) or with bundle exec (e.g. :Dispatch bundle exec rspec --color spec/models/user_spec.rb).

With rspec globally installed and a simple _spec.rb-file, :Dispatch shows the behaviour described above when used in combination with tmux:

• :make % - works, runs the test
• :Make % - opens a split pane, closes it and doesn't show anything in the quickfix window
• :!rspec % - works, runs the test
• :Dispatch rspec % - opens a split pane, closes it and doesn't show anything in the quickfix window

I made a simple ascii.io recording to show what's happening. The recording doesn't show that all of this is happening in a tmux session, but it actually is.

Do you need any more information?

Edit:

I just tried this out with a simple minitest file and got the same results.

from vim-dispatch.

Check :Copen afterwards for errors.

from vim-dispatch.

Check :Copen afterwards for errors.

I just did that and it's empty. But I now changed that spec so that it fails and well, now the quickfix window stays open and does contain the error. So I guess that's the desired behaviour: do not show anything if there are no errors but open the quickfix window if there are any.

Thanks for clearing that up! So it's just a different behaviour from using bundle exec rspec, which keeps X examples, 0 failures in the quickfix window.

from vim-dispatch.

I think this is what's happening: when Dispatch recognizes the filetype it uses a compiler with make, so in case there are no errors, the quickfix is empty.

from vim-dispatch.

Yeah, sounds like this is the desired behavior. One could debate whether the ruby compiler should capture more informative output rather than just errors.

from vim-dispatch.