[Pkg-lirc-maint] Bug#513675: New version of 22_man_page2
Philipp Matthias Hahn
pmhahn at titan.lahn.de
Sat Jan 31 09:19:30 UTC 2009
There war a minor formatting error regarding the lirc[m]d.8 pages,
here's a new patch.
--
Philipp Matthias Hahn <pmhahn at debian.org>
GPG/PGP: 9A540E39 @ keyrings.debian.org
-------------- next part --------------
Improve reading experience of manual pages by applying visual hints
--- a/doc/man/ircat.1
+++ b/doc/man/ircat.1
@@ -7,11 +7,11 @@ ircat - print strings when pressing butt
[\fIoptions\fR] \fI<prog>\fR
.SH DESCRIPTION
This program prints config strings to standard output. It can be used
-to provide remote control input to scripts and to debug your .lircrc
+to provide remote control input to scripts and to debug your \fI.lircrc\fP
file.
The argument to the program is the program name, as it
-appears in the prog entries in .lircrc.
+appears in the prog entries in \fI.lircrc\fP.
.TP
\fB\-h\fR \fB\-\-help\fR
display usage summary
@@ -22,7 +22,7 @@ display version
\fB\-c\fR \fB\-\-config=\fR<file>
set config file
.SH EXAMPLES
-If .lircrc contains:
+If \fI.lircrc\fP contains:
.nf
begin
--- a/doc/man/irexec.1
+++ b/doc/man/irexec.1
@@ -7,10 +7,10 @@ irexec - run programs with one button pr
[\fIoptions\fR] [\fIconfig_file\fR]
.SH DESCRIPTION
This program lets you execute arbitrary commands on an IR signal decoded
-by lircd, the LIRC daemon. You can give irexec a command line parameter
+by \fBlircd\fP, the LIRC daemon. You can give irexec a command line parameter
which has to be a name of a valid config file. If no command line
parameters are given irexec reads the default config file which is
-usually ~/.lircrc.
+usually \fI~/.lircrc\fP.
If irexec executes a program it will wait until this program terminates.
So append a '&' to the command string if you don't want that.
@@ -29,16 +29,16 @@ run in background
\fB\-n\fR \fB\-\-name\fR
use this program name
.SH OPTIONS
-If you add the \-\-daemon option irexec will fork to
-background. That way you can easily start irexec from an init script. In
+If you add the \fB\-\-daemon\fP option irexec will fork to
+background. That way you can easily start \fBirexec\fP from an init script. In
this case you should specify a config file on the command line as irexec
won't be able to find your home directory. Potential uses are shutting
down the computer, starting a dial-up connection etc.
.SH NOTE
-If you start irexec, it reads your ~/.lircrc and reacts only on
+If you start irexec, it reads your \fI~/.lircrc\fP and reacts only on
prog= entries that point to irexec. If you have included more than one
-program in your .lircrc, then start all these programs, they react
-itself only to their according entries in .lircrc.
+program in your \fI.lircrc\fP, then start all these programs, they react
+itself only to their according entries in \fI.lircrc\fP.
.SH "SEE ALSO"
The documentation for
.B lirc
--- a/doc/man/irpty.1
+++ b/doc/man/irpty.1
@@ -4,16 +4,16 @@
irpty - pseudo tty driver
.SH SYNOPSIS
.B irpty
-[\fIoptions\fR] \fIconfig_file -- program \fR[\fIargs \fR...]
+[\fIoptions\fR] \fIconfig_file \fB--\fP program \fR[\fIargs \fR...]
.SH DESCRIPTION
-irpty connects to lircd to receive infrared codes and converts them to
-key strokes. E.g. type irpty ~/.lircrc -- workbone to control the
+\fBirpty\fP connects to lircd to receive infrared codes and converts them to
+key strokes. E.g. type irpty\fI ~/.lircrc\fP -- workbone to control the
CD-player program workbone. Of course you will have to create an
appropriate config file for this purpose first. The config string will
be passed to the desired application. Note that you can use escape
sequences to specify non printable characters. Have a look at the\
- .lircrc file format description for details.
+ \fI.lircrc\fP file format description for details.
.TP
\fB\-h\fR \fB\-\-help\fR
display usage summary
--- a/doc/man/irrecord.1
+++ b/doc/man/irrecord.1
@@ -7,14 +7,14 @@ irrecord - application for recording IR-
[\fIoptions\fR] \fIfile\fR
.SH DESCRIPTION
This program will record the signals from your remote control and create
-a config file for lircd. A proper config file for lircd is maybe the
+a config file for \fBlircd\fP(8). A proper config file for \fBlircd\fP(8) is maybe the
most vital part of this package, so you should invest some time to
create a working config file. Although I put a good deal of effort in
this program it is often not possible to automatically recognize all
features of a remote control.
If the program fails to recognize the protocol of the remote control you
-should use the \-\-force option to at least create a config file in raw mode.
+should use the \fB\-\-force\fP option to at least create a config file in raw mode.
If \fIfile\fR already exists and contains a valid config irrecord will use the
protocol description found there and will only try to record the
@@ -22,8 +22,8 @@ buttons. This is very useful if you want
files of the same brand are already available. Of course this will only
work if the remotes use the same protocol but it's worth a try. You will
find template files for the most common protocols in the
-remotes/generic/ directory of this package. The name of the new file is
-created by appending .conf to the given filename in this case.
+\fIremotes/generic/\fP directory of this package. The name of the new file is
+created by appending \fI.conf\fP to the given filename in this case.
.TP
\fB\-h\fR \fB\-\-help\fR
display this message
--- a/doc/man/irsend.1
+++ b/doc/man/irsend.1
@@ -6,7 +6,7 @@ irsend - basic LIRC program to send infr
.B irsend
[\fIoptions\fR] \fIDIRECTIVE REMOTE CODE \fR[\fICODE\fR...]
.SH DESCRIPTION
-Asks the \fBlircd\fR daemon to send one or more CIR
+Asks the \fBlircd\fR(8) daemon to send one or more CIR
(Consumer Infra-Red) commands. This is intended for remote control
of electronic devices such as TV boxes, HiFi sets, etc.
.PP
@@ -23,12 +23,12 @@ of electronic devices such as TV boxes,
.fi
.PP
-\fIREMOTE\fR is the name of a remote, as described in the \fBlircd\fR
+\fIREMOTE\fR is the name of a remote, as described in the \fBlircd\fR(8)
configuration file.
.PP
\fICODE\fR is the name of a remote control key of \fIREMOTE\fR, as it
-appears in the \fBlircd\fR configuration file.
+appears in the \fBlircd\fR(8) configuration file.
.PP
\fINUM\fR is the transmitter number of the hardware device.
@@ -55,8 +55,8 @@ display usage summary
\fB\-v\fR \fB\-\-version\fR
display version
.TP
-\fB\-d\fR \fB\-\-device\fR
-use given lircd socket [/dev/lircd]
+\fB\-d\fR \fB\-\-device\fR=\fI/dev/lircd\fP
+use given lircd socket
.TP
\fB\-a\fR \fB\-\-address\fR=\fIhost[\fR:port]
connect to lircd at this address
@@ -79,12 +79,12 @@ irsend SIMULATE "0000000000000476 00 OK
.SH FILES
.TP
.I /etc/lircd.conf
-Default \fBlircd\fR configuration file. It should contain all the
+Default \fBlircd\fR(8) configuration file. It should contain all the
remotes, their infra-red codes and the corresponding timing and
waveform details.
.SH DIAGNOSTICS
-If \fBlircd\fR is not running (or /dev/lircd lacks write permissions)
+If \fBlircd\fR(8) is not running (or \fI/dev/lircd\fP lacks write permissions)
\fBrc\fR aborts with the following diagnostics:
.nf
"irsend: could not connect to socket"
@@ -96,5 +96,10 @@ The documentation for
is maintained as html pages. They are located under html/ in the
documentation directory.
-.BR lircd "(8), " mode2 "(1), " smode2 "(1), " xmode2 "(1), "
-.BR irrecord "(1), " irw "(1), " http://www.lirc.org .
+.BR lircd (8),
+.BR mode2 (1),
+.BR smode2 (1),
+.BR xmode2 (1),
+.BR irrecord (1),
+.BR irw (1),
+.BR http://www.lirc.org .
--- a/doc/man/irw.1
+++ b/doc/man/irw.1
@@ -7,9 +7,9 @@ irw - sends data from Unix domain socket
[\fIsocket\fR]
.SH DESCRIPTION
-irw will connect to any Unix domain socket and will print the data that it
+\fBirw\fP will connect to any Unix domain socket and will print the data that it
receives to stdout. If you don't give it a socket name argument it will watch
-\//dev/lircd. Useful for debugging.
+\/\fI/dev/lircd\fP. Useful for debugging.
.TP
\fB\-h\fR \fB\-\-help\fR
display usage summary
--- a/doc/man/irxevent.1
+++ b/doc/man/irxevent.1
@@ -6,13 +6,13 @@ irxevent - infrared X-event sender
.B irxevent
[\fIoption\fR]... [\fIconfig file\fR]
.SH DESCRIPTION
-Irxevent is a program that I wrote to send button clicks and key presses to X
+\fBirxevent\fP is a program that I wrote to send button clicks and key presses to X
applications triggered by a LIRC driven remote control. You can control your
favorite CD/MP3 player or your TV tuner program or any other X application
that responds to keyboard or mouse input. If you like to you can send emacs
^X^S from your armchair.
-Irxevent is a complement to irexec and irpty.
+\fBirxevent\fP is a complement to \fBirexec\fP(1) and \fBirpty\fP(1).
.TP
\fB\-d\fR \fB\-\-daemon\fR
fork and run in background
@@ -23,10 +23,10 @@ display usage summary
\fB\-V\fR \fB\-\-version\fR
display version
.SH FILES
-Irxevent works with the same config file as irexec and irpty (~/.lircrc). For
-a complete sample .lircrc look at examples/lircrc.
+\fBirxevent\fP works with the same config file as \fBirexec\fP(1) and \fBirpty\fP(1) (\fI~/.lircrc\fP). For
+a complete sample \fI.lircrc\fP look at examples/lircrc.
-.B Part of your .lircrc could look like this:
+Part of your \fI.lircrc\fP could look like this:
.nf
.RS 3
@@ -74,7 +74,7 @@ end
.RE
.fi
-.B Simply said \fIconfig\fB = lines may look like this:
+Simply said \fBconfig=\fP lines may look like this:
.nf
.RS 3
@@ -87,7 +87,7 @@ config = xy_Key <x> <y> [shift-][ctrl-][
.RE
.fi
-.B some more examples:
+some more examples:
.nf
.RS 3
@@ -100,7 +100,7 @@ config = Key shift-Page_Up rxvt
.RE
.fi
-.B In BNF this looks like:
+In BNF this looks like:
.RS 3
.nf
@@ -119,40 +119,40 @@ TARGET = Windowname | "WindowID" id | "
.RS 2
is the key symbol that is declared in X windows. E.g. "Up" refers to the
cursor arrow pointing up. "KP_Add" is the plus sign on the key pad. Just take
-a look at irxevent.keys (in the documentation directory) if you are not sure
+a look at \fIirxevent.keys\fP (in the documentation directory) if you are not sure
about a symbol's name.
.RE
.I KeySym:
.RS 2
-number as returned by XStringToKeysym(3x).
+number as returned by \fBXStringToKeysym\fP(3x).
.RE
.I KeyCode:
.RS 2
-number as returned by XKeysymToKeycode(3x).
+number as returned by \fBXKeysymToKeycode\fP(3x).
.RE
.I Windowname:
.RS 2
can be the first characters of the window name displayed by the window manager
or the name that is displayed below the icon. Some programs use the name
displayed by the window manager to show a lot of status information but don't
-change the icon name (like xawtv). Others append information to the window
+change the icon name (like \fBxawtv\fP(1)). Others append information to the window
name ("GQmpeg - kill_windooz.mp3"). If neither window name nor icon name match
-the given Windowname information from XClassHint(3x) will be checked.
+the given Windowname information from \fBXClassHint\fP(3x) will be checked.
.RE
.I CurrentWindow:
.RS 2
-refers to the active window as returned by XGetInputFocus(3x). Most times this
+refers to the active window as returned by \fBXGetInputFocus\fP(3x). Most times this
is the window with your mouse pointer in it.
.RE
.I RootWindow:
.RS 2
-refers to the \fIroot\fR window as returned by RootWindow(3x). You may need
+refers to the \fIroot\fR window as returned by \fBRootWindow\fP(3x). You may need
this to send events to the window manager.
.RE
.I WindowID id:
.RS 2
refers to the window with window identifier \fIid\fR. \fIid\fR should be a
-decimal number. It is useful when irxevent can't find the desired window by
+decimal number. It is useful when \fBirxevent\fP can't find the desired window by
other means.
.RE
.I Focus:
@@ -165,32 +165,32 @@ CurrentWindow.
.SH TROUBLESHOOTING
If you have problems finding the coordinates for a button click you can try
-xev \-id <window_id>. The window_id can be found using xwininfo. If xev and
-xwininfo are not part of your distribution you can find them at a FTP server
-using the search engine at: http://ftpsearch.ntnu.no/ . xev also reports the
+\fBxev \-id\fP <\fIwindow_id\fP>. The \fIwindow_id\fP can be found using \fBxwininfo\fP(1). If \fBxev\fP(1) and
+\fBxwininfo\fP(1) are not part of your distribution you can find them at a FTP server
+using the search engine at: http://ftpsearch.ntnu.no/ . \fBxev\fP also reports the
names of key symbols like "Control_L" (your left control key) or "KP_Subtract"
(the 'minus' key on your keypad).
There are programs that do not accept any synthetic X-events by default
-because they can cause security problems. Currently xterm and xemacs are known
-to ignore events simulated by irxevent.
+because they can cause security problems. Currently \fBxterm\fP(1) and \fBxemacs\fP(1) are known
+to ignore events simulated by \fBirxevent\fP.
-You can however make xterm accept external events by enabling "Allow
+You can however make \fBxterm\fP(1) accept external events by enabling "Allow
SendEvents" in the "Main Options" (hold down the Ctrl button and press the
left mouse button inside the xterm window). You can as well place this line
-into your .Xresources file to change this permanently:
+into your \fI.Xresources\fP file to change this permanently:
.RS 3
XTerm.vt100.allowSendEvents: true
.RE
-Yet another possibility is to start xterm like this:
+Yet another possibility is to start \fBxterm\fP(1) like this:
.RS 3
xterm \-xrm "XTerm.vt100.allowSendEvents: true"
.RE
-xemacs will accept events if you set a built-in variable. The following was
+\fBxemacs\fP(1) will accept events if you set a built-in variable. The following was
taken from the online help:
.RS 3
--- a/doc/man/lircd.8
+++ b/doc/man/lircd.8
@@ -7,11 +7,11 @@ domain socket.
.B lircd
[\fIoptions\fR] [\fIconfig-file\fR]
.SH DESCRIPTION
-The main task of lircd is to decode the infrared signals and provide an
-uniform interface for client applications. Clients can connect to lircd
-through a Unix domain socket which is located in /dev/lircd. Using this
+The main task of \fBlircd\fP is to decode the infrared signals and provide an
+uniform interface for client applications. Clients can connect to \fBlircd\fP
+through a Unix domain socket which is located in \fI/dev/lircd\fP. Using this
socket they will get the infrared codes received by lircd and they can
-send commands to lircd.
+send commands to \fBlircd\fP.
.TP
\fB\-h\fR \fB\-\-help\fR
display this message
@@ -23,7 +23,7 @@ display version
don't fork to background
.TP
\fB\-p\fR \fB\-\-permission\fR=\fImode\fR
-file permissions for /dev/lircd
+file permissions for \fI/dev/lircd\fP
.TP
\fB\-H\fR \fB\-\-driver\fR=\fIdriver\fR
use given driver
@@ -35,7 +35,7 @@ read from given device
listen for network connections on port
.TP
\fB\-c\fR \fB\-\-connect\fR=\fIhost[\fR:port]
-connect to remote lircd server
+connect to remote \fBlircd\fP server
.TP
\fB\-o\fR \fB\-\-output\fR=\fIsocket\fR
output socket filename
@@ -52,48 +52,48 @@ auto-generate release events
\fB\-a\fR \fB\-\-allow\-simulate\fR
accept SIMULATE command
.SH OPTIONS
-The \-\-permission option gives the file permission of /dev/lircd if it
+The \fB\-\-permission\fP option gives the file permission of \fI/dev/lircd\fP if it
has to be created in octal representation. Read the documentation for
-chmod for further details. If no \-\-permission option is given when the
+\fBchmod\fP(1) for further details. If no \fB\-\-permission\fP option is given when the
socket is initially created the default is to give all users read and
-write permissions (0666 in octal representation). If /dev/lircd already
+write permissions (0666 in octal representation). If \fI/dev/lircd\fP already
exists this option has no effect.
-With the \-\-device option you can select the character device which lircd
-should read from. The default currently is /dev/lirc but it probably
+With the \fB\-\-device\fP option you can select the character device which \fBlircd\fP
+should read from. The default currently is \fI/dev/lirc\fP but it probably
will change in future.
-If you're using the dev/input driver, you can use \fIname=STRING\fR or
-\fIphys=STRING\fR to select the device; lircd will look in /dev/input
+If you're using the \fBdev/input\fP driver, you can use \fBname=\fP\fISTRING\fR or
+\fBphys=\fP\fISTRING\fR to select the device; \fBlircd\fP will look in \fI/dev/input\fP
to find a device with a matching description. This is useful in case
the device name isn't fixed. \fISTRING\fR may contain the '*' and '?'
wildcards and '\\' to mark them as literal.
-With the \-\-listen option you can let lircd listen for network
-connections on the given port. The default port is 8765. No security
+With the \fB\-\-listen\fP option you can let lircd listen for network
+connections on the given port. The default port is \fI8765\fP. No security
checks are currently implemented.
-The \-\-connect option allows you to connect to other lircd servers that
+The \fB\-\-connect\fP option allows you to connect to other \fBlircd\fP servers that
provide a network socket at the given host and port number. The number
of such connections is currently limited to 100.
-With the \-\-output option you can select Unix domain socket, which lircd
-will write remote key codes to. The default currently is /dev/lircd.
+With the \fB\-\-output\fP option you can select Unix domain socket, which \fBlircd\fP
+will write remote key codes to. The default currently is \fI/dev/lircd\fP.
-With the \-\-pidfile option you can select the lircd daemon pid file.
-The default currently is /var/run/lircd.pid.
+With the \fB\-\-pidfile\fP option you can select the \fBlircd\fP daemon pid file.
+The default currently is \fI/var/run/lircd.pid\fP.
-With the \-\-logfile option you can select the lircd daemon log file.
-The default currently is /var/log/lircd. Note that this option will
-only be available if you compiled lircd without syslog support.
+With the \fB\-\-logfile\fP option you can select the \fBlircd\fP daemon log file.
+The default currently is \fI/var/log/lircd\fP. Note that this option will
+only be available if you compiled \fBlircd\fP without syslog support.
-The \-\-release option enables automatic generation of release events
-for each button press. lircd will append the given suffix to the button
+The \fB\-\-release\fP option enables automatic generation of release events
+for each button press. \fBlircd\fP will append the given suffix to the button
name for each release event. If no suffix is given the default suffix
is '_UP'.
-The \-\-allow-simulate option will enable the SIMULATE command which can
-be issued using irsend(1). This will allow simulating arbitrary IR events
+The \fB\-\-allow-simulate\fP option will enable the SIMULATE command which can
+be issued using \fBirsend\fP(1). This will allow simulating arbitrary IR events
from the command line. Use this option with caution because it will give all
users with access to the lircd socket wide control over you system.
E.g. if you have configured your system to shut down by a button press
@@ -101,22 +101,22 @@ on your remote control, everybody will b
your system from the command line.
.SH FILES
-The config file for lircd is located in /etc/lircd.conf. lircd
-has its own log file in /var/log/lircd (beginning with LIRC version
+The config file for \fBlircd\fP is located in \fI/etc/lircd.conf\fP. \fBlircd\fP
+has its own log file in \fI/var/log/lircd\fP (beginning with LIRC version
0.6.1 you can configure lircd to use syslogd for log messages; then it
depends on your system configuration where log messages will show up).
-You can make lircd reread its config file and reopen its log file by
+You can make \fBlircd\fP reread its config file and reopen its log file by
sending the HUP signal to the program. That way you can rotate old log
files.
.SH DAEMONS
-lircd and lircmd are daemons. You should start them in some init script
+\fBlircd\fP and \fBlircmd\fP(8) are daemons. You should start them in some init script
depending on your system. There are some example scripts for different
-distributions in the contrib directory. lircmd has to be started after
-lircd as it connects to the socket lircd provides.
+distributions in the contrib directory. \fBlircmd\fP(8) has to be started after
+\fBlircd\fP as it connects to the socket \fBlircd\fP provides.
-If you start lircd or lircmd from your shell prompt you will usually get
+If you start \fBlircd\fP or \fBlircmd\fP(8) from your shell prompt you will usually get
back immediately to the prompt. Often people think that the program has
-died. But this is not an error. lircd and lircmd are daemons. Daemons
+died. But this is not an error. \fBlircd\fP and \fBlircmd\fP(8) are daemons. Daemons
always run in background.
.SH "SEE ALSO"
The documentation for
--- a/doc/man/lircmd.8
+++ b/doc/man/lircmd.8
@@ -9,7 +9,7 @@ lircmd \- translates infrared signals in
This daemon can simulate a MouseSystems, IntelliMouse or IMPS/2 type mouse. It
gets the received buttons from lircd and converts them to mouse events. To
make this possible, lircmd needs a config file located
-in /etc/lircmd.conf. In this file you have to determine which
+in \fI/etc/lircmd.conf\fP. In this file you have to determine which
button from which remote causes a mouse move or a mouse button click.
.TP
\fB\-h\fR \fB\-\-help\fR
@@ -21,19 +21,19 @@ display version
\fB\-n\fR \fB\-\-nodaemon\fR
don't fork to background
.SH OPTIONS
-If you provide the \-\-nodaemon option lircmd won't fork to background.
+If you provide the \fB\-\-nodaemon\fP option \fBlircmd\fP won't fork to background.
.SH FILES
-lircmd will use syslogd to output error messages. It depends on your
+\fBlircmd\fP will use syslogd to output error messages. It depends on your
system configuration where they will show up.
.SH DAEMONS
-lircd and lircmd are daemons. You should start them in some init script
+\fBlircd\fP(8) and \fBlircmd\fP are daemons. You should start them in some init script
depending on your system. There are some example scripts for different
-distributions in the contrib directory. lircmd has to be started after
-lircd as it connects to the socket lircd provides.
+distributions in the contrib directory. \fBlircmd\fP has to be started after
+\fBlircd\fP(8) as it connects to the socket \fBlircd\fP(8) provides.
-If you start lircd or lircmd from your shell prompt you will usually get
+If you start \fBlircd\fP(8) or \fBlircmd\fP from your shell prompt you will usually get
back immediately to the prompt. Often people think that the program has
-died. But this is not an error. lircd and lircmd are daemons. Daemons
+died. But this is not an error. \fBlircd\fP(8) and \fBlircmd\fP are daemons. Daemons
always run in background.
.SH "SEE ALSO"
The documentation for
--- a/doc/man/lircrcd.1
+++ b/doc/man/lircrcd.1
@@ -8,7 +8,7 @@ lircrc \- handle consistent .lircrc stat
.SH DESCRIPTION
.B lircrcd
-reads the given .lircrc config file and synchronises the mode
+reads the given \fI.lircrc\fP config file and synchronises the mode
that the LIRC clients using this config file (\fBirexec\fR(1),
\fBirxevent\fR(1) , etc.) are in. Using
.B lircrcd
@@ -32,16 +32,16 @@ output socket filename
.SH OPTIONS
.TP
.BI \-p,\ \-\-premission= mode
-The \-\-permission option gives the file permission of the Unix domain
-socket lircrcd creates on startup in octal representation. Read the
-documentation for chmod for further details. If no \-\-permission option
+The \fB\-\-permission\fP option gives the file permission of the Unix domain
+socket \fBlircrcd\fP creates on startup in octal representation. Read the
+documentation for \fBchmod\fP(1) for further details. If no \fB\-\-permission\fP option
is given when the socket is created the default is to give only the
user owning the file read and write permissions (0600 in octal
representation).
.TP
.BI \-o,\ \-\-output= socket
-With the \-\-output option you can select the Unix domain socket, which
-lircrcd will create. The default is to append a "d" character to the
+With the \fB\-\-output\fP option you can select the Unix domain socket, which
+\fBlircrcd\fP will create. The default is to append a "d" character to the
config filename given.
.SH "SEE ALSO"
The documentation for
--- a/doc/man/mode2.1
+++ b/doc/man/mode2.1
@@ -13,7 +13,7 @@ debugging. Of course this program won't
the signals itself like e.g. TV cards or the Irman.
-mode2 will simply print pulse&space lengths to stdout.
+\fBmode2\fP will simply print pulse&space lengths to stdout.
.TP
\fB\-h\fR \fB\-\-help\fR
display usage summary
@@ -27,7 +27,9 @@ read from given device
\fB\-m\fR \fB\-\-mode\fR
enable alternative display mode
.SH "SEE ALSO"
-mode2(1), smode2(1), xmode2(1)
+.BR mode2 (1),
+.BR smode2 (1),
+.BR xmode2(1) .
The documentation for
.B lirc
--- a/doc/man/smode2.1
+++ b/doc/man/smode2.1
@@ -13,12 +13,12 @@ debugging. Of course this program won't
the signals itself like e.g. TV cards or the Irman.
-smode2 uses the svgalib to show the IR waveform in a graphical
+\fBsmode2\fP uses the svgalib to show the IR waveform in a graphical
representation. The time division is variable from 1 ms/unit to
extremely high values (integer type) but there is no point increasing
this value above 20 ms/unit, because one pulse is about 1 ms. This kind
of presentation is much more exciting than the simple pulse&space output
-showed by mode2.
+showed by \fBmode2\fP(1).
.TP
\fB\-h\fR \fB\-\-help\fR
display usage summary
@@ -32,7 +32,9 @@ read from given device
\fB\-t\fR \fB\-\-timediv\fR=\fIvalue\fR
ms per unit
.SH "SEE ALSO"
-mode2(1), smode2(1), xmode2(1)
+.BR mode2 (1),
+.BR smode2 (1),
+.BR xmode2(1) .
The documentation for
.B lirc
--- a/doc/man/xmode2.1
+++ b/doc/man/xmode2.1
@@ -13,10 +13,10 @@ debugging. Of course this program won't
the signals itself like e.g. TV cards or the Irman.
-xmode2 is based on smode2 by Sinkovics Zoltan. It is just a conversion
+\fBxmode2\fP is based on \fBsmode2\fP by Sinkovics Zoltan. It is just a conversion
from svga to X with some basic support for resizing. The only
-differences are that the \-\-mode option enables an alternative display
-mode and that xmode2 can read and visualise mode2 output from stdin.
+differences are that the \fB\-\-mode\fP option enables an alternative display
+mode and that \fBxmode2\fP can read and visualise \fBmode2\fP(1) output from stdin.
.TP
\fB\-h\fR \fB\-\-help\fR
display usage summary
@@ -26,8 +26,9 @@ display version
.TP
\fB\-d\fR \fB\-\-device\fR=\fIdevice\fR
read from given device
-.HP
-\fB\-g\fR \fB\-\-geometry\fR=\fIgeometry\fR window geometry
+.TP
+\fB\-g\fR \fB\-\-geometry\fR=\fIgeometry\fR
+window geometry
.TP
\fB\-t\fR \fB\-\-timediv\fR=\fIvalue\fR
ms per unit
@@ -35,7 +36,9 @@ ms per unit
\fB\-m\fR \fB\-\-mode\fR
enable alternative display mode
.SH "SEE ALSO"
-mode2(1), smode2(1), xmode2(1)
+.BR mode2 (1),
+.BR smode2 (1),
+.BR xmode2 (1).
The documentation for
.B lirc
More information about the Pkg-lirc-maint
mailing list