Skip to content
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

Cancel current run if new is triggered #867

Open
mbajur opened this issue Mar 15, 2017 · 0 comments
Open

Cancel current run if new is triggered #867

mbajur opened this issue Mar 15, 2017 · 0 comments

Comments

@mbajur
Copy link

mbajur commented Mar 15, 2017

Hello everyone!

I browsed entire guard documentation to find that feature but couldn't find anything related. Which seems pretty strange to me cause such feature sounds obvious.

Is that possible to tell guard to stop current process and start the new one when the new one "comes in"? Right now, when i'm saving a file, guard runs a specs for that file no matter if i'm gonna save it once again during that run or not. How i would love it to work would be to instruct guard to cancel currently running job if it detects another file change. Instead of queueing the new one.

Right now i need to cancel the current one by myself which is not a big deal but one more cmd + tab to hit :)

Thanks in advance!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant