-
Notifications
You must be signed in to change notification settings - Fork 483
Configure keyboard shortcuts
From version >= 0.7.0 Posix Signal handlers are no more used to interact with Guard.
The Guard keyboard shortcuts are in fact signals that are being trapped. Signals are specified in POSIX.1 standard and not all operating systems are full POSIX compliant (like embedded systems and windows). You can send signals to Guard with the kill command on Unix like operating systems.
Guard uses the following signals:
-
SIGHUP
=> Run all -
SIGINT
=> Stop -
SIGTSTP
=> Reload
You can set the options for a terminal device interface with the stty command. This allows you to list the current control characters for signals:
$ stty -a
cchars: discard = ^O; dsusp = ^Y; eof = ^D; eol = <undef>;
eol2 = <undef>; erase = ^?; intr = ^C; kill = ^U; lnext = ^V;
min = 1; quit = ^\; reprint = ^R; start = ^Q; status = ^T;
stop = ^S; susp = ^Z; time = 0; werase = ^W;
Now you can change the control character for SIGQUIT
:
$ stty quit "^R"
This maps Guards' Run all to Ctrl-R
.
If you use Guard on Windows, you should install Cygwin and make sure you have the coreutils package installed to have the appropriate commands available in your shell.
This wiki and the Guard README document contain a lot of information, please take your time and read these instructions carefully.
If you run into any trouble, you may start by understanding how Guard works.
We provide detailed changes for each Guard release.
Be sure to read the CONTRIBUTING guidelines before reporting a new Guard issue or open a pull request.
If you have any questions about the Guard usage or want to share some information with the Guard community, please go to one of the following places:
- Google+ community
- Google group
- StackOverflow
- IRC channel
#guard
(irc.freenode.net) for chatting