1
fix hyphen-used-as-minus-sign problem.
2
fix manpage-has-bad-whatis-entry
4
© 2006 Hector Garcia <hector@debian.org>
5
© 2008 Stefan Lippers-Hollmann <s.l-h@gmx.de>
7
Index: lirc-0.8.5/doc/man/irexec.1
8
===================================================================
9
--- lirc-0.8.5.orig/doc/man/irexec.1 2009-05-21 10:55:09.000000000 -0500
10
+++ lirc-0.8.5/doc/man/irexec.1 2009-06-15 00:40:00.000000000 -0500
12
\fB\-n\fR \fB\-\-name\fR
15
-If you add the --daemon option irexec will fork to
16
+If you add the \-\-daemon option irexec will fork to
17
background. That way you can easily start irexec from an init script. In
18
this case you should specify a config file on the command line as irexec
19
won't be able to find your home directory. Potential uses are shutting
20
Index: lirc-0.8.5/doc/man/irrecord.1
21
===================================================================
22
--- lirc-0.8.5.orig/doc/man/irrecord.1 2009-05-21 10:55:10.000000000 -0500
23
+++ lirc-0.8.5/doc/man/irrecord.1 2009-06-15 00:40:00.000000000 -0500
25
features of a remote control.
27
If the program fails to recognize the protocol of the remote control you
28
-should use the --force option to at least create a config file in raw mode.
29
+should use the \-\-force option to at least create a config file in raw mode.
31
If \fIfile\fR already exists and contains a valid config irrecord will use the
32
protocol description found there and will only try to record the
33
Index: lirc-0.8.5/doc/man/irxevent.1
34
===================================================================
35
--- lirc-0.8.5.orig/doc/man/irxevent.1 2009-05-21 10:55:10.000000000 -0500
36
+++ lirc-0.8.5/doc/man/irxevent.1 2009-06-15 00:40:00.000000000 -0500
40
If you have problems finding the coordinates for a button click you can try
41
-xev -id <window_id>. The window_id can be found using xwininfo. If xev and
42
+xev \-id <window_id>. The window_id can be found using xwininfo. If xev and
43
xwininfo are not part of your distribution you can find them at a FTP server
44
using the search engine at: http://ftpsearch.ntnu.no/ . xev also reports the
45
names of key symbols like "Control_L" (your left control key) or "KP_Subtract"
47
Yet another possibility is to start xterm like this:
50
-xterm -xrm "XTerm.vt100.allowSendEvents: true"
51
+xterm \-xrm "XTerm.vt100.allowSendEvents: true"
54
xemacs will accept events if you set a built-in variable. The following was
55
Index: lirc-0.8.5/doc/man/lircd.8
56
===================================================================
57
--- lirc-0.8.5.orig/doc/man/lircd.8 2009-05-21 10:55:10.000000000 -0500
58
+++ lirc-0.8.5/doc/man/lircd.8 2009-06-15 00:41:33.000000000 -0500
60
.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.24.
61
-.TH LIRCD "1" "May 2009" "lircd 0.8.5" FSF
62
+.TH LIRCD "8" "May 2009" "lircd 0.8.5" FSF
64
-LIRC daemon - decodes infrared signals and provides them on a Unix
65
+LIRC daemon \- decodes infrared signals and provides them on a Unix
70
\fB\-u\fR \fB\-\-uinput\fR
71
generate Linux input events
73
-The --permission option gives the file permission of /dev/lircd if it
74
+The \-\-permission option gives the file permission of /dev/lircd if it
75
has to be created in octal representation. Read the documentation for
76
-chmod for further details. If no --permission option is given when the
77
+chmod for further details. If no \-\-permission option is given when the
78
socket is initially created the default is to give all users read and
79
write permissions (0666 in octal representation). If /dev/lircd already
80
exists this option has no effect.
82
-With the --device option you can select the character device which lircd
83
+With the \-\-device option you can select the character device which lircd
84
should read from. The default currently is /dev/lirc but it probably
85
will change in future.
87
If you're using the dev/input driver, you can use \fIname=STRING\fR or
88
\fIphys=STRING\fR to select the device; lircd will look in /dev/input
89
to find a device with a matching description. This is useful in case
90
-the device name isn't fixed. \fISTRING\fR may contain the '*' and '?'
91
+the device name isn't fixed. \fISTRING\fR may contain the '*' and '?'
92
wildcards and '\\' to mark them as literal.
94
-With the --listen option you can let lircd listen for network
95
+With the \-\-listen option you can let lircd listen for network
96
connections on the given address/port. The default address is 0.0.0.0,
97
which means that connections on all network interfaces will be accepted.
98
The default port is 8765. No security checks are currently implemented.
99
The listening lircd instance will send all IR events to the connecting
102
-The --connect option allows you to connect to other lircd servers that
103
+The \-\-connect option allows you to connect to other lircd servers that
104
provide a network socket at the given host and port number. The number
105
of such connections is currently limited to 100.
106
The connecting lircd instance will receive IR events from the lircd
107
instance it connects to.
109
-With the --output option you can select Unix domain socket, which lircd
110
+With the \-\-output option you can select Unix domain socket, which lircd
111
will write remote key codes to. The default currently is /dev/lircd.
113
-With the --pidfile option you can select the lircd daemon pid file.
114
+With the \-\-pidfile option you can select the lircd daemon pid file.
115
The default currently is /var/run/lircd.pid.
117
-With the --logfile option you can select the lircd daemon log file.
118
+With the \-\-logfile option you can select the lircd daemon log file.
119
The default currently is /var/log/lircd. Note that this option will
120
only be available if you compiled lircd without syslog support.
122
-The --release option enables automatic generation of release events
123
+The \-\-release option enables automatic generation of release events
124
for each button press. lircd will append the given suffix to the button
125
name for each release event. If no suffix is given the default suffix
128
-The --allow-simulate option will enable the SIMULATE command which can
129
+The \-\-allow-simulate option will enable the SIMULATE command which can
130
be issued using irsend(1). This will allow simulating arbitrary IR events
131
from the command line. Use this option with caution because it will give all
132
users with access to the lircd socket wide control over you system.
134
on your remote control, everybody will be able to shut down
135
your system from the command line.
137
-On Linux systems the --uinput option will enable automatic generation
138
+On Linux systems the \-\-uinput option will enable automatic generation
139
of Linux input events. lircd will open /dev/input/uinput and inject
140
key events to the Linux kernel. The key code depends on the name that
141
was given a button in the lircd config file, e.g. if the button is
142
Index: lirc-0.8.5/doc/man/lircmd.8
143
===================================================================
144
--- lirc-0.8.5.orig/doc/man/lircmd.8 2009-05-21 10:55:10.000000000 -0500
145
+++ lirc-0.8.5/doc/man/lircmd.8 2009-06-15 00:42:10.000000000 -0500
147
.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.24.
148
-.TH LIRCMD "1" "May 2009" "lircmd 0.8.5" FSF
149
+.TH LIRCMD "8" "May 2009" "lircmd 0.8.5" FSF
151
-LIRC mouse daemon - translates infrared signals into mouse events
152
+LIRC mouse daemon \- translates infrared signals into mouse events
155
[\fIoptions\fR] [\fIconfig-file\fR]
157
\fB\-n\fR \fB\-\-nodaemon\fR
158
don't fork to background
160
-If you provide the --nodaemon option lircmd won't fork to background.
161
+If you provide the \-\-nodaemon option lircmd won't fork to background.
163
lircmd will use syslogd to output error messages. It depends on your
164
system configuration where they will show up.
165
Index: lirc-0.8.5/doc/man/lircrcd.1
166
===================================================================
167
--- lirc-0.8.5.orig/doc/man/lircrcd.1 2009-05-21 10:55:10.000000000 -0500
168
+++ lirc-0.8.5/doc/man/lircrcd.1 2009-06-15 00:40:00.000000000 -0500
170
.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.24.
171
.TH LIRCRCD "1" "May 2009" "lircrcd 0.8.5" FSF
173
-lircrc daemon - handle consistent .lircrc state among client applications
174
+lircrc \- handle consistent .lircrc state among client applications
177
[\fIoptions\fR] \fIconfig-file\fR
181
.BI \-p,\ \-\-premission= mode
182
-The --permission option gives the file permission of the Unix domain
183
+The \-\-permission option gives the file permission of the Unix domain
184
socket lircrcd creates on startup in octal representation. Read the
185
-documentation for chmod for further details. If no --permission option
186
+documentation for chmod for further details. If no \-\-permission option
187
is given when the socket is created the default is to give only the
188
user owning the file read and write permissions (0600 in octal
191
.BI \-o,\ \-\-output= socket
192
-With the --output option you can select the Unix domain socket, which
193
+With the \-\-output option you can select the Unix domain socket, which
194
lircrcd will create. The default is to append a "d" character to the
195
config filename given.
197
Index: lirc-0.8.5/doc/man/xmode2.1
198
===================================================================
199
--- lirc-0.8.5.orig/doc/man/xmode2.1 2009-05-21 10:55:09.000000000 -0500
200
+++ lirc-0.8.5/doc/man/xmode2.1 2009-06-15 00:40:00.000000000 -0500
203
xmode2 is based on smode2 by Sinkovics Zoltan. It is just a conversion
204
from svga to X with some basic support for resizing. The only
205
-differences are that the --mode option enables an alternative display
206
+differences are that the \-\-mode option enables an alternative display
207
mode and that xmode2 can read and visualise mode2 output from stdin.
209
\fB\-h\fR \fB\-\-help\fR