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

Ctrl + \ quits instead of restarting #36

Closed
fbjork opened this issue Oct 10, 2011 · 13 comments
Closed

Ctrl + \ quits instead of restarting #36

fbjork opened this issue Oct 10, 2011 · 13 comments

Comments

@fbjork
Copy link

fbjork commented Oct 10, 2011

After upgrading guard-spork I can no longer to Ctrl + backslash to restart, instead SIGQUIT is sent.

@netzpirat
Copy link
Contributor

From the Guard readme:

Interactions

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.

@rymai
Copy link
Member

rymai commented Oct 10, 2011

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:
#36

@rymai
Copy link
Member

rymai commented Oct 10, 2011

Aha too slow! :P

@netzpirat
Copy link
Contributor

Yeah, the Guard organization has an incredible response time (during CET) :P

@fbjork
Copy link
Author

fbjork commented Oct 10, 2011

Thanks!

@thibaudgg
Copy link
Member

You're amazing! :)

@fbjork
Copy link
Author

fbjork commented Oct 12, 2011

So how do I get Guard to re-run all specs again? Just enter does nothing for me.

@thibaudgg
Copy link
Member

Please can you show us your Guardfile,

@fbjork
Copy link
Author

fbjork commented Oct 12, 2011

@thibaudgg
Copy link
Member

Ok weird, and you're using guard 0.8.4 launched with bundle exec right? Entering 'q' + enter is not working neither?

@fbjork
Copy link
Author

fbjork commented Oct 12, 2011

Yeah, and q works fine.

@thibaudgg
Copy link
Member

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

@rymai
Copy link
Member

rymai commented Oct 12, 2011

By any chance, does it change anything if you press return?

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

4 participants