Janko Marohnić

@aignas Maybe you could help out with this?

What vim-dispatch strategy is being used (tmux, neovim terminal, ...)? vim-test's `dispatch` strategy doesn't do anything other than calling the `:Dispatch` command with the test command. Does the same behaviour...

@olalonde Could you show me your vim-test configuration, and the Neovim version you're using? Ideally I should have all information I need to reproduce the issue. What does the LanguageClient-neovim...

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

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`.

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...

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...

Yes, the convention for strategy-specific variables would be the latter, `test#shtuff#receiver`. Feel free to send a PR 👍

@codeinabox The `basic` strategy opens a new tab on Neovim. @Sevensidedmarble I think that opening the terminal in a new tab is a good default behaviour, because it leaves your...

Yes, that sounds reasonable, I'd accept this PR.