-
Notifications
You must be signed in to change notification settings - Fork 386
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature: support for dispatch Spawn #756
Comments
Thank you for raising this, do you envisage this as a new strategy or a modification to the Dispatch strategy? |
Looks like the Dispatch strategy currently has two options or "identifiers", (dispatch and dispatch_background), I was thinking this could be the third (dispatch_spawn) ? |
Sounds good to me, would like to have a try raising a PR for this new strategy? Happy to give a hand |
bnadlerjr
added a commit
to bnadlerjr/vim-test
that referenced
this issue
May 28, 2024
dispatch.vim supports the `Spawn` and `Spawn!` commands in addition to the `Dispatch` variations. This adds a strategy to also support `Spawn`. Closes vim-test#756.
bnadlerjr
added a commit
to bnadlerjr/vim-test
that referenced
this issue
May 28, 2024
dispatch.vim supports the `Spawn` and `Spawn!` commands in addition to the `Dispatch` variations. This adds a strategy to also support `Spawn`. Closes vim-test#756.
codeinabox
pushed a commit
that referenced
this issue
May 30, 2024
dispatch.vim supports the `Spawn` and `Spawn!` commands in addition to the `Dispatch` variations. This adds a strategy to also support `Spawn`. Closes #756.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have been using Vim8 with vim-test for a while using the default basic strategy which is great. I wanted to run my tests non-blocking while still be able to navigate the code, so I tried Dispatch strategy. That allows me to continue to navigate the code, but now I can no longer stop at breakpoints to debug. The Dispatch recommendation is to use Spawn instead of Dispatch as the command.
tpope/vim-dispatch#319
Could vim-test add support for this?
I read through the other options and it wasn't clear that any of the other strategies that are supported would meet desire for non-blocking, debuggability / interactive term. I tried asyncrun but the debugger wouldn't work there either.
The text was updated successfully, but these errors were encountered: