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

Fixed a missing word in the 'man' page, and just a few other tweaks. #15

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 6 additions & 6 deletions thd.pod
Original file line number Diff line number Diff line change
Expand Up @@ -13,15 +13,15 @@ B<thd> [B<--help>] [B<--user> I<name>] [B<--listevents>] [B<--dump>] [B<--socket
Triggerhappy is a hotkey daemon that operates on a system wide scale. It watches all configured input devices
for key, switch or button events and can launch arbitrary commands specified by the administrator. In contrast
to hotkey services provided by desktop environments, Triggerhappy is especially suited to hardware related switches
like volume or wifi control; it works independently from a specific user being logged in and is also suitable for embedded systems that do not a graphical user interface.
like volume or wifi control; it works independently from a specific user being logged in and is also suitable for embedded systems that do not have a graphical user interface.

=head1 OPTIONS

=over

=item B<--help>

Shows usage instructions
Shows usage instructions.

=item B<--listevents>

Expand Down Expand Up @@ -81,7 +81,7 @@ Additional command line arguments are considered filenames of input devices.
The hotkey bindings used by Triggerhappy are set in the configuration file specified by B<--triggers>. Each line consists of three segments:
The symbolic name of the key or event name to react on, the value carried by the expected event, and of course the command to be launched.

The event names can be identified by operating the desired key or switch while running the triggerhappy daemon with the option B<--dump>.
The event names can be identified by operating the desired key or switch while running the Triggerhappy daemon with the option B<--dump>.

Key events carry the value I<1> for a key being pressed and transmit the payload I<0> when it is released; holding the key down constantly yields events with a value of I<2>.

Expand All @@ -99,7 +99,7 @@ Dump all events processable by thd to the console; this is useful to find out th

B<thd --triggers /etc/triggerhappy/triggers.d/ /dev/input/event*>

Read from all currently connected input devices and process events according to the files in F</etc/triggerhappy/triggers.d/>.
Read from all currently connected input devices and process events according to the files in F</etc/triggerhappy/triggers.d/>

B<thd --triggers /etc/triggerhappy/triggers.conf --socket /var/run/thd.socket>

Expand Down Expand Up @@ -129,7 +129,7 @@ its name to the event name:
KEY_KPPLUS@media 1 /usr/bin/mpc next
KEY_KPMINUS@media 1 /usr/bin/mpc prev

These two lines will only cause mpc to be called if the triggerhappy daemon is in
These two lines will only cause mpc to be called if the Triggerhappy daemon is in
"media" mode. Changing the mode can be achieved by placing a special trigger inside
the configuration:

Expand All @@ -151,7 +151,7 @@ presses once a special trigger is reached:
By prepending a keycode with the special character '<', other applications will
receive a press and release of the corresponding key. This is especially useful
to remap or mirror events generated by devices exclusively serviced by the
triggerhappy daemon.
Triggerhappy daemon.

It is possible to create handlers that only react to specific devices: to achieve
such behaviour, add the input device using B<th-cmd> and supply it with a tag; this
Expand Down