Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
While using Guard I always noticed that it exits with status code "1" even when using the interactor to stop it (My terminal shows failure status codes).
It would be nice to let Guard exit with the right status codes because it is a tool used by a lot of developers.
I've changed the way Guard exits in this commit. Guard doesn't exit the program no more when calling
Guard.stop
. This has the advantage of being able to useGuard.stop
programmatically knowing it won't kill the process.I felt that the interactor should be the one to exit Guard's process, so now it will call
Kernel::exit
after it stops all running guards.When there is an interrupt, Guard will still stop all guards, but now it will use
Kernel::abort
to return a failure status-code.The commits will apply nicely and the specs pass: http://travis-ci.org/#!/Maher4Ever/guard