Closed fbjork closed 12 years ago
From the Guard readme:
From version >= 0.7.0 Posix Signal handlers are no more used to interact with Guard. If you're using a version < 0.7, please refer to the README in the v0.6 branch.
When Guard do nothing you can interact with by entering a command + hitting enter:
stop|quit|exit|s|q|e + enter
- Calls each guard's #stop
method, in the same order they are declared in the Guardfile, and then quits Guard itself.reload|r|z + enter
- Calls each guard's #reload
method, in the same order they are declared in the Guardfile.pause|p + enter
- Toggle files modification listening. Useful when switching git branches.just enter (no commands)
- Calls each guard's #run_all
method, in the same order they are declared in the Guardfile.Hi,
From version 0.7 Guard is not using signals anymore, please consult Guard's README ("Interaction" section)!
Thanks.
Sent from my iPhone
On 10 oct. 2011, at 19:42, Fredrik Björk reply@reply.github.com wrote:
After upgrading guard-spork I can no longer to Ctrl + backslash to restart, instead SIGQUIT is sent.
Reply to this email directly or view it on GitHub: https://github.com/guard/guard-spork/issues/36
Aha too slow! :P
Yeah, the Guard organization has an incredible response time (during CET) :P
Thanks!
You're amazing! :)
So how do I get Guard to re-run all specs again? Just enter does nothing for me.
Please can you show us your Guardfile,
Ok weird, and you're using guard 0.8.4 launched with bundle exec
right? Entering 'q' + enter is not working neither?
Yeah, and q works fine.
That's really really weird, never have issues to run all specs by just pressing enter. Maybe give us more info about your environment (ruby, os, terminal app...)
By any chance, does it change anything if you press return
?
After upgrading guard-spork I can no longer to Ctrl + backslash to restart, instead SIGQUIT is sent.