[ViewVC] Diff of: cvs/rxvt-unicode/doc/rxvt.7.man.in

Comparing rxvt-unicode/doc/rxvt.7.man.in (file contents):
Revision 1.66 by root, Tue Jan 31 21:04:14 2006 UTC vs.
Revision 1.79 by root, Mon Aug 7 16:17:30 2006 UTC

-.\" Automatically generated by Pod::Man v1.37, Pod::Parser v1.14
+.\" Automatically generated by Pod::Man 2.09 (Pod::Simple 3.04)
 .\"
 .\" Standard preamble:
 .\" ========================================================================
 .de Sh \" Subsection heading
 .br
 .    ds Ae AE
 .\}
 .rm #[ #] #H #V #F C
 .\" ========================================================================
 .\"
-.IX Title "rxvt 7"
+.IX Title "@@RXVT_NAME@@ 7"
-.TH rxvt 7 "2006-01-31" "7.5" "RXVT-UNICODE"
+.TH @@RXVT_NAME@@ 7 "2006-08-07" "7.9" "RXVT-UNICODE"
 .SH "NAME"
 RXVT REFERENCE \- FAQ, command sequences and other background information
 .SH "SYNOPSIS"
 .IX Header "SYNOPSIS"
 .Vb 2
 \&   # set a new font set
 \&   printf '\e33]50;%s\e007' 9x15,xft:Kochi" Mincho"
-.Ve
+\&
-.PP
-.Vb 2
-\&   # change the locale and tell rxvt-unicode about it
+\&   # change the locale and tell rxvt\-unicode about it
-\&   export LC_CTYPE=ja_JP.EUC-JP; printf "\e33]701;$LC_CTYPE\e007"
+\&   export LC_CTYPE=ja_JP.EUC\-JP; printf "\e33]701;$LC_CTYPE\e007"
-.Ve
+\&
-.PP
-.Vb 2
 \&   # set window title
 \&   printf '\e33]2;%s\e007' "new window title"
 .Ve
 .SH "DESCRIPTION"
 .IX Header "DESCRIPTION"
 Beginning with version 7.3, there is a perl extension that implements a
 simple tabbed terminal. It is installed by default, so any of these should
 give you tabs:
 .PP
 .Vb 1
-\&   @@URXVT_NAME@@ -pe tabbed
+\&   @@URXVT_NAME@@ \-pe tabbed
-.Ve
+\&
-.PP
-.Vb 1
-\&   URxvt.perl-ext-common: default,tabbed
+\&   URxvt.perl\-ext\-common: default,tabbed
 .Ve
 .PP
 It will also work fine with tabbing functionality of many window managers
 or similar tabbing programs, and its embedding-features allow it to be
 embedded into other programs, as witnessed by \fIdoc/rxvt\-tabbed\fR or
 .IX Subsection "How can I start @@URXVT_NAME@@d in a race-free way?"
 .PP
 Try \f(CW\*(C`@@URXVT_NAME@@d \-f \-o\*(C'\fR, which tells @@URXVT_NAME@@d to open the
 display, create the listening socket and then fork.
 .PP
+\fIHow can I start @@URXVT_NAME@@d automatically when I run URXVT_NAME@@c?\fR
+.IX Subsection "How can I start @@URXVT_NAME@@d automatically when I run URXVT_NAME@@c?"
+.PP
+If you want to start @@URXVT_NAME@@d automatically whenever you run
+@@URXVT_NAME@@c and the daemon isn't running yet, use this script:
+.PP
+.Vb 6
+\&   #!/bin/sh
+\&   @@URXVT_NAME@@c "$@"
+\&   if [ $? \-eq 2 ]; then
+\&      @@URXVT_NAME@@d \-q \-o \-f
+\&      @@URXVT_NAME@@c "$@"
+\&   fi
+.Ve
+.PP
+This tries to create a new terminal, and if fails with exit status 2,
+meaning it couldn't connect to the daemon, it will start the daemon and
+re-run the command. Subsequent invocations of the script will re-use the
+existing daemon.
+.PP
-\fIHow do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc.\fR
+\fIHow do I distinguish whether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc.\fR
-.IX Subsection "How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc."
+.IX Subsection "How do I distinguish whether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc."
 .PP
 The original rxvt and rxvt-unicode always export the variable \*(L"\s-1COLORTERM\s0\*(R",
 so you can check and see if that is set. Note that several programs, \s-1JED\s0,
 slrn, Midnight Commander automatically check this variable to decide
 whether or not to use color.
 Courtesy of Chuck Blake <cblake@BBN.COM> with the following shell script
 snippets:
 .PP
 .Vb 12
 \&   # Bourne/Korn/POSIX family of shells:
-\&   [ ${TERM:-foo} = foo ] && TERM=xterm # assume an xterm if we don't know
+\&   [ ${TERM:\-foo} = foo ] && TERM=xterm # assume an xterm if we don't know
-\&   if [ ${TERM:-foo} = xterm ]; then
+\&   if [ ${TERM:\-foo} = xterm ]; then
-\&      stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not
+\&      stty \-icanon \-echo min 0 time 15 # see if enhanced rxvt or not
-\&      echo -n '^[Z'
+\&      echo \-n '^[Z'
 \&      read term_id
 \&      stty icanon echo
-\&      if [ ""${term_id} = '^[[?1;2C' -a ${DISPLAY:-foo} = foo ]; then
+\&      if [ ""${term_id} = '^[[?1;2C' \-a ${DISPLAY:\-foo} = foo ]; then
-\&         echo -n '^[[7n'        # query the rxvt we are in for the DISPLAY string
+\&         echo \-n '^[[7n'        # query the rxvt we are in for the DISPLAY string
 \&         read DISPLAY           # set it in our local shell
 \&      fi
 \&   fi
 .Ve
 .PP
 features unique to urxvt (locale, encoding conversion, iso14755 etc.) are
 already in use in this mode.
 .PP
 .Vb 3
 \&    text    data     bss     drs     rss filename
-\&   98398    1664      24   15695    1824 rxvt --disable-everything
+\&   98398    1664      24   15695    1824 rxvt \-\-disable\-everything
-\&  188985    9048   66616   18222    1788 urxvt --disable-everything
+\&  188985    9048   66616   18222    1788 urxvt \-\-disable\-everything
 .Ve
 .PP
 When you \f(CW\*(C`\-\-enable\-everything\*(C'\fR (which \fIis\fR unfair, as this involves xft
 and full locale/XIM support which are quite bloaty inside libX11 and my
-libc), the two diverge, but not unreasnobaly so.
+libc), the two diverge, but not unreasonably so.
 .PP
 .Vb 3
 \&    text    data     bss     drs     rss filename
-\&  163431    2152      24   20123    2060 rxvt --enable-everything
+\&  163431    2152      24   20123    2060 rxvt \-\-enable\-everything
-\& 1035683   49680   66648   29096    3680 urxvt --enable-everything
+\& 1035683   49680   66648   29096    3680 urxvt \-\-enable\-everything
 .Ve
 .PP
 The very large size of the text section is explained by the east-asian
 encoding tables, which, if unused, take up disk space but nothing else
 and can be compiled out unless you rely on X11 core fonts that use those
 .PP
 .Vb 4
 \&   libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000)
 \&   libc.so.6 => /lib/libc.so.6 (0x00002aaaaadde000)
 \&   libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab01d000)
-\&   /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)
+\&   /lib64/ld\-linux\-x86\-64.so.2 (0x00002aaaaaaab000)
 .Ve
 .PP
 And here is rxvt\-unicode:
 .PP
 .Vb 5
 \&   libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000)
 \&   libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00002aaaaada2000)
 \&   libc.so.6 => /lib/libc.so.6 (0x00002aaaaaeb0000)
 \&   libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab0ee000)
-\&   /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)
+\&   /lib64/ld\-linux\-x86\-64.so.2 (0x00002aaaaaaab000)
 .Ve
 .PP
 No large bloated libraries (of course, none were linked in statically),
 except maybe libX11 :)
 .Sh "Rendering, Font & Look and Feel Issues"
 .PP
 1. Use inheritPixmap:
 .PP
 .Vb 2
 \&   Esetroot wallpaper.jpg
-\&   @@URXVT_NAME@@ -ip -tint red -sh 40
+\&   @@URXVT_NAME@@ \-ip \-tint red \-sh 40
 .Ve
 .PP
 That works. If you think it doesn't, you lack transparency and tinting
 support, or you are unable to read.
 .PP
 2. Use a simple pixmap and emulate pseudo\-transparency. This enables you
 to use effects other than tinting and shading: Just shade/tint/whatever
 your picture with gimp or any other tool:
 .PP
 .Vb 2
-\&   convert wallpaper.jpg -blur 20x20 -modulate 30 background.xpm
+\&   convert wallpaper.jpg \-blur 20x20 \-modulate 30 background.xpm
-\&   @@URXVT_NAME@@ -pixmap background.xpm -pe automove-background
+\&   @@URXVT_NAME@@ \-pixmap background.xpm \-pe automove\-background
 .Ve
 .PP
 That works. If you think it doesn't, you lack \s-1XPM\s0 and Perl support, or you
 are unable to read.
 .PP
 3. Use an \s-1ARGB\s0 visual:
 .PP
 .Vb 1
-\&   @@URXVT_NAME@@ -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc
+\&   @@URXVT_NAME@@ \-depth 32 \-fg grey90 \-bg rgba:0000/0000/4444/cccc
 .Ve
 .PP
 This requires \s-1XFT\s0 support, and the support of your X\-server. If that
 doesn't work for you, blame Xorg and Keith Packard. \s-1ARGB\s0 visuals aren't
-there yet, no matter what they claim. Rxvt-Unicode contains the neccessary
+there yet, no matter what they claim. Rxvt-Unicode contains the necessary
 bugfixes and workarounds for Xft and Xlib to make it work, but that
 doesn't mean that your \s-1WM\s0 has the required kludges in place.
 .PP
 4. Use xcompmgr and let it do the job:
 .PP
 .Vb 2
-\&  xprop -frame -f _NET_WM_WINDOW_OPACITY 32c \e
+\&  xprop \-frame \-f _NET_WM_WINDOW_OPACITY 32c \e
-\&        -set _NET_WM_WINDOW_OPACITY 0xc0000000
+\&        \-set _NET_WM_WINDOW_OPACITY 0xc0000000
 .Ve
 .PP
 Then click on a window you want to make transparent. Replace \f(CW0xc0000000\fR
 by other values to change the degree of opacity. If it doesn't work and
 your server crashes, you got to keep the pieces.
-.PP
-\fIWhy do some chinese characters look so different than others?\fR
-.IX Subsection "Why do some chinese characters look so different than others?"
-.PP
-This is because there is a difference between script and language \*(--
-rxvt-unicode does not know which language the text that is output is,
-as it only knows the unicode character codes. If rxvt-unicode first
-sees a japanese/chinese character, it might choose a japanese font for
-display. Subsequent japanese characters will use that font. Now, many
-chinese characters aren't represented in japanese fonts, so when the first
-non-japanese character comes up, rxvt-unicode will look for a chinese font
-\&\*(-- unfortunately at this point, it will still use the japanese font for
-chinese characters that are also in the japanese font.
-.PP
-The workaround is easy: just tag a chinese font at the end of your font
-list (see the previous question). The key is to view the font list as
-a preference list: If you expect more japanese, list a japanese font
-first. If you expect more chinese, put a chinese font first.
-.PP
-In the future it might be possible to switch language preferences at
-runtime (the internal data structure has no problem with using different
-fonts for the same character at the same time, but no interface for this
-has been designed yet).
-.PP
-Until then, you might get away with switching fonts at runtime (see \*(L"Can I switch the fonts at runtime?\*(R" later in this document).
 .PP
 \fIWhy does rxvt-unicode sometimes leave pixel droppings?\fR
 .IX Subsection "Why does rxvt-unicode sometimes leave pixel droppings?"
 .PP
 Most fonts were not designed for terminal use, which means that character
 however: Xft fonts often draw glyphs larger than their acclaimed bounding
 box, and rxvt-unicode has no way of detecting this (the correct way is to
 ask for the character bounding box, which unfortunately is wrong in these
 cases).
 .PP
-It's not clear (to me at least), wether this is a bug in Xft, freetype,
+It's not clear (to me at least), whether this is a bug in Xft, freetype,
 or the respective font. If you encounter this problem you might try using
 the \f(CW\*(C`\-lsp\*(C'\fR option to give the font more height. If that doesn't work, you
 might be forced to use a different font.
 .PP
 All of this is not a problem when using X11 core fonts, as their bounding
 .PP
 Yes, using an escape sequence. Try something like this, which has the same
 effect as using the \f(CW\*(C`\-fn\*(C'\fR switch, and takes effect immediately:
 .PP
 .Vb 1
-\&   printf '\ee]50;%s\e007' "9x15bold,xft:Kochi Gothic"
+\&   printf '\e33]50;%s\e007' "9x15bold,xft:Kochi Gothic"
 .Ve
 .PP
 This is useful if you e.g. work primarily with japanese (and prefer a
 japanese font), but you have to switch to chinese temporarily, where
 japanese fonts would only be in your way.
 \fIWhy do italic characters look as if clipped?\fR
 .IX Subsection "Why do italic characters look as if clipped?"
 .PP
 Many fonts have difficulties with italic characters and hinting. For
 example, the otherwise very nicely hinted font \f(CW\*(C`xft:Bitstream Vera Sans
-Mono\*(C'\fR completely fails in it's italic face. A workaround might be to
+Mono\*(C'\fR completely fails in its italic face. A workaround might be to
 enable freetype autohinting, i.e. like this:
 .PP
 .Vb 2
 \&   URxvt.italicFont:        xft:Bitstream Vera Sans Mono:italic:autohint=true
 \&   URxvt.boldItalicFont:    xft:Bitstream Vera Sans Mono:bold:italic:autohint=true
 .PP
 \fIRxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?\fR
 .IX Subsection "Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?"
 .PP
 Rxvt-unicode will use whatever you specify as a font. If it needs to
-fall back to it's default font search list it will prefer X11 core
+fall back to its default font search list it will prefer X11 core
 fonts, because they are small and fast, and then use Xft fonts. It has
 antialiasing disabled for most of them, because the author thinks they
 look best that way.
 .PP
 If you want antialiasing, you have to specify the fonts manually.
 \&   URxvt.color3:   #A8A800
 \&   URxvt.color4:   #0000A8
 \&   URxvt.color5:   #A800A8
 \&   URxvt.color6:   #00A8A8
 \&   URxvt.color7:   #A8A8A8
-.Ve
+\&
-.PP
-.Vb 8
 \&   URxvt.color8:   #000054
 \&   URxvt.color9:   #FF0054
 \&   URxvt.color10:  #00FF54
 \&   URxvt.color11:  #FFFF54
 \&   URxvt.color12:  #0000FF
 \&   URxvt.color15:  #FFFFFF
 .Ve
 .PP
 And here is a more complete set of non-standard colors.
 .PP
-.Vb 18
+.Vb 10
 \&   URxvt.cursorColor:  #dc74d1
 \&   URxvt.pointerColor: #dc74d1
 \&   URxvt.background:   #0e0e0e
 \&   URxvt.foreground:   #4ad5e1
 \&   URxvt.color0:       #000000
 \&   URxvt.color14:      #73f7ff
 \&   URxvt.color7:       #e1dddd
 \&   URxvt.color15:      #e1dddd
 .Ve
 .PP
-(They were described (not by me) as \*(L"pretty girly\*(R").
+They have been described (not by me) as \*(L"pretty girly\*(R".
 .PP
 \fIWhy do some characters look so much different than others?\fR
 .IX Subsection "Why do some characters look so much different than others?"
 .PP
 See next entry.
 .PP
 In that case, select a font of your taste and add it to the font list,
 e.g.:
 .PP
 .Vb 1
-\&   @@URXVT_NAME@@ -fn basefont,font2,font3...
+\&   @@URXVT_NAME@@ \-fn basefont,font2,font3...
 .Ve
 .PP
 When rxvt-unicode sees a character, it will first look at the base
 font. If the base font does not contain the character, it will go to the
 next font, and so on. Specifying your own fonts will also speed up this
 search and use less resources within rxvt-unicode and the X\-server.
 .PP
 The only limitation is that none of the fonts may be larger than the base
 font, as the base font defines the terminal character cell size, which
 must be the same due to the way terminals work.
+.PP
+\fIWhy do some chinese characters look so different than others?\fR
+.IX Subsection "Why do some chinese characters look so different than others?"
+.PP
+This is because there is a difference between script and language \*(--
+rxvt-unicode does not know which language the text that is output is,
+as it only knows the unicode character codes. If rxvt-unicode first
+sees a japanese/chinese character, it might choose a japanese font for
+display. Subsequent japanese characters will use that font. Now, many
+chinese characters aren't represented in japanese fonts, so when the first
+non-japanese character comes up, rxvt-unicode will look for a chinese font
+\&\*(-- unfortunately at this point, it will still use the japanese font for
+chinese characters that are also in the japanese font.
+.PP
+The workaround is easy: just tag a chinese font at the end of your font
+list (see the previous question). The key is to view the font list as
+a preference list: If you expect more japanese, list a japanese font
+first. If you expect more chinese, put a chinese font first.
+.PP
+In the future it might be possible to switch language preferences at
+runtime (the internal data structure has no problem with using different
+fonts for the same character at the same time, but no interface for this
+has been designed yet).
+.PP
+Until then, you might get away with switching fonts at runtime (see \*(L"Can
+I switch the fonts at runtime?\*(R" later in this document).
 .Sh "Keyboard, Mouse & User Interaction"
 .IX Subsection "Keyboard, Mouse & User Interaction"
 \fIThe new selection selects pieces that are too big, how can I select single words?\fR
 .IX Subsection "The new selection selects pieces that are too big, how can I select single words?"
 .PP
 If you want to select e.g. alphanumeric words, you can use the following
 setting:
 .PP
 .Vb 1
-\&   URxvt.selection.pattern-0: ([[:word:]]+)
+\&   URxvt.selection.pattern\-0: ([[:word:]]+)
 .Ve
 .PP
 If you click more than twice, the selection will be extended
 more and more.
 .PP
 To get a selection that is very similar to the old code, try this pattern:
 .PP
 .Vb 1
-\&   URxvt.selection.pattern-0: ([^"&'()*,;<=>?@[\e\e\e\e]^`{|})]+)
+\&   URxvt.selection.pattern\-0: ([^"&'()*,;<=>?@[\e\e\e\e]^`{|})]+)
 .Ve
 .PP
 Please also note that the \fILeftClick Shift-LeftClik\fR combination also
 selects words like the old code.
 .PP
 \&\fB\s-1PREPACKAGED\s0 \s-1EXTENSIONS\s0\fR in the @@URXVT_NAME@@\fIperl\fR\|(3) manpage. For
 example, to disable the \fBselection-popup\fR and \fBoption-popup\fR, specify
 this \fBperl-ext-common\fR resource:
 .PP
 .Vb 1
-\&   URxvt.perl-ext-common: default,-selection-popup,-option-popup
+\&   URxvt.perl\-ext\-common: default,\-selection\-popup,\-option\-popup
 .Ve
 .PP
 This will keep the default extensions, but disable the two popup
 extensions. Some extensions can also be configured, for example,
 scrollback search mode is triggered by \fBM\-s\fR. You can move it to any
 other combination either by setting the \fBsearchable-scrollback\fR resource:
 .PP
 .Vb 1
-\&   URxvt.searchable-scrollback: CM-s
+\&   URxvt.searchable\-scrollback: CM\-s
 .Ve
 .PP
 \fIThe cursor moves when selecting text in the current input line, how do I switch this off?\fR
 .IX Subsection "The cursor moves when selecting text in the current input line, how do I switch this off?"
 .PP
 circumstances, it will move your cursor around when you click into the
 line that contains it. It tries hard not to do this at the wrong moment,
 but when running a program that doesn't parse cursor movements or in some
 cases during rlogin sessions, it fails to detect this properly.
 .PP
-You can permamently switch this feature off by disabling the \f(CW\*(C`readline\*(C'\fR
+You can permanently switch this feature off by disabling the \f(CW\*(C`readline\*(C'\fR
 extension:
 .PP
 .Vb 1
-\&   URxvt.perl-ext-common: default,-readline
+\&   URxvt.perl\-ext\-common: default,\-readline
 .Ve
 .PP
 \fIMy numerical keypad acts weird and generates differing output?\fR
 .IX Subsection "My numerical keypad acts weird and generates differing output?"
 .PP
 Some Debian GNUL/Linux users seem to have this problem, although no
 specific details were reported so far. It is possible that this is caused
-by the wrong \f(CW\*(C`TERM\*(C'\fR setting, although the details of wether and how
+by the wrong \f(CW\*(C`TERM\*(C'\fR setting, although the details of whether and how
 this can happen are unknown, as \f(CW\*(C`TERM=rxvt\*(C'\fR should offer a compatible
 keymap. See the answer to the previous question, and please report if that
 helped.
 .PP
 \fIMy Compose (Multi_key) key is no longer working.\fR
 .PP
 \fIWhat's with the strange Backspace/Delete key behaviour?\fR
 .IX Subsection "What's with the strange Backspace/Delete key behaviour?"
 .PP
 Assuming that the physical Backspace key corresponds to the
-BackSpace keysym (not likely for Linux ... see the following
+Backspace keysym (not likely for Linux ... see the following
 question) there are two standard values that can be used for
 Backspace: \f(CW\*(C`^H\*(C'\fR and \f(CW\*(C`^?\*(C'\fR.
 .PP
 Historically, either value is correct, but rxvt-unicode adopts the debian
 policy of using \f(CW\*(C`^?\*(C'\fR when unsure, because it's the one only only correct
 .PP
 .Vb 3
 \&   # use Backspace = ^H
 \&   $ stty erase ^H
 \&   $ @@URXVT_NAME@@
-.Ve
+\&
-.PP
-.Vb 3
 \&   # use Backspace = ^?
 \&   $ stty erase ^?
 \&   $ @@URXVT_NAME@@
 .Ve
 .PP
 For an existing rxvt\-unicode:
 .PP
 .Vb 3
 \&   # use Backspace = ^H
 \&   $ stty erase ^H
-\&   $ echo -n "^[[36h"
+\&   $ echo \-n "^[[36h"
-.Ve
+\&
-.PP
-.Vb 3
 \&   # use Backspace = ^?
 \&   $ stty erase ^?
-\&   $ echo -n "^[[36l"
+\&   $ echo \-n "^[[36l"
 .Ve
 .PP
 This helps satisfy some of the Backspace discrepancies that occur, but
 if you use Backspace = \f(CW\*(C`^H\*(C'\fR, make sure that the termcap/terminfo value
 properly reflects that.
 you have run \*(L"configure\*(R" with the \f(CW\*(C`\-\-disable\-resources\*(C'\fR option you can
 use the `keysym' resource to alter the keystrings associated with keysyms.
 .PP
 Here's an example for a URxvt session started using \f(CW\*(C`@@URXVT_NAME@@ \-name URxvt\*(C'\fR
 .PP
-.Vb 20
+.Vb 10
 \&   URxvt.keysym.Home:          \e033[1~
 \&   URxvt.keysym.End:           \e033[4~
-\&   URxvt.keysym.C-apostrophe:  \e033<C-'>
+\&   URxvt.keysym.C\-apostrophe:  \e033<C\-'>
-\&   URxvt.keysym.C-slash:       \e033<C-/>
+\&   URxvt.keysym.C\-slash:       \e033<C\-/>
-\&   URxvt.keysym.C-semicolon:   \e033<C-;>
+\&   URxvt.keysym.C\-semicolon:   \e033<C\-;>
-\&   URxvt.keysym.C-grave:       \e033<C-`>
+\&   URxvt.keysym.C\-grave:       \e033<C\-`>
-\&   URxvt.keysym.C-comma:       \e033<C-,>
+\&   URxvt.keysym.C\-comma:       \e033<C\-,>
-\&   URxvt.keysym.C-period:      \e033<C-.>
+\&   URxvt.keysym.C\-period:      \e033<C\-.>
-\&   URxvt.keysym.C-0x60:        \e033<C-`>
+\&   URxvt.keysym.C\-0x60:        \e033<C\-`>
-\&   URxvt.keysym.C-Tab:         \e033<C-Tab>
+\&   URxvt.keysym.C\-Tab:         \e033<C\-Tab>
-\&   URxvt.keysym.C-Return:      \e033<C-Return>
+\&   URxvt.keysym.C\-Return:      \e033<C\-Return>
-\&   URxvt.keysym.S-Return:      \e033<S-Return>
+\&   URxvt.keysym.S\-Return:      \e033<S\-Return>
-\&   URxvt.keysym.S-space:       \e033<S-Space>
+\&   URxvt.keysym.S\-space:       \e033<S\-Space>
-\&   URxvt.keysym.M-Up:          \e033<M-Up>
+\&   URxvt.keysym.M\-Up:          \e033<M\-Up>
-\&   URxvt.keysym.M-Down:        \e033<M-Down>
+\&   URxvt.keysym.M\-Down:        \e033<M\-Down>
-\&   URxvt.keysym.M-Left:        \e033<M-Left>
+\&   URxvt.keysym.M\-Left:        \e033<M\-Left>
-\&   URxvt.keysym.M-Right:       \e033<M-Right>
+\&   URxvt.keysym.M\-Right:       \e033<M\-Right>
-\&   URxvt.keysym.M-C-0:         list \e033<M-C- 0123456789 >
+\&   URxvt.keysym.M\-C\-0:         list \e033<M\-C\- 0123456789 >
-\&   URxvt.keysym.M-C-a:         list \e033<M-C- abcdefghijklmnopqrstuvwxyz >
+\&   URxvt.keysym.M\-C\-a:         list \e033<M\-C\- abcdefghijklmnopqrstuvwxyz >
 \&   URxvt.keysym.F12:           command:\e033]701;zh_CN.GBK\e007
 .Ve
 .PP
 See some more examples in the documentation for the \fBkeysym\fR resource.
 .PP
 Rather than have rxvt-unicode try to accommodate all the various possible
 keyboard mappings, it is better to use `xmodmap' to remap the keys as
 required for your particular machine.
 .Sh "Terminal Configuration"
 .IX Subsection "Terminal Configuration"
+\fICan I see a typical configuration?\fR
+.IX Subsection "Can I see a typical configuration?"
+.PP
+The default configuration tries to be xterm\-like, which I don't like that
+much, but it's least surprise to regular users.
+.PP
+As a rxvt or rxvt-unicode user, you are practically supposed to invest
+time into customising your terminal. To get you started, here is the
+author's .Xdefaults entries, with comments on what they do. It's certainly
+not \fItypical\fR, but what's typical...
+.PP
+.Vb 2
+\&   URxvt.cutchars: "()*,<>[]{}|'
+\&   URxvt.print\-pipe: cat >/tmp/xxx
+.Ve
+.PP
+These are just for testing stuff.
+.PP
+.Vb 2
+\&   URxvt.imLocale: ja_JP.UTF\-8
+\&   URxvt.preeditType: OnTheSpot,None
+.Ve
+.PP
+This tells rxvt-unicode to use a special locale when communicating with
+the X Input Method, and also tells it to only use the OnTheSpot pre-edit
+type, which requires the \f(CW\*(C`xim\-onthespot\*(C'\fR perl extension but rewards me
+with correct-looking fonts.
+.PP
+.Vb 6
+\&   URxvt.perl\-lib: /root/lib/urxvt
+\&   URxvt.perl\-ext\-common: default,selection\-autotransform,selection\-pastebin,xim\-onthespot,remote\-clipboard
+\&   URxvt.selection.pattern\-0: ( at .*? line \e\ed+)
+\&   URxvt.selection.pattern\-1: ^(/[^:]+):\e
+\&   URxvt.selection\-autotransform.0: s/^([^:[:space:]]+):(\e\ed+):?$/:e \e\eQ$1\e\eE\e\ex0d:$2\e\ex0d/
+\&   URxvt.selection\-autotransform.1: s/^ at (.*?) line (\e\ed+)$/:e \e\eQ$1\e\eE\e\ex0d:$2\e\ex0d/
+.Ve
+.PP
+This is my perl configuration. The first two set the perl library
+directory and also tells urxvt to use a large number of extensions. I
+develop for myself mostly, so I actually use most of the extensions I
+write.
+.PP
+The selection stuff mainly makes the selection perl-error-message aware
+and tells it to convert perl error messages into vi-commands to load the
+relevant file and go tot he error line number.
+.PP
+.Vb 2
+\&   URxvt.scrollstyle:      plain
+\&   URxvt.secondaryScroll:  true
+.Ve
+.PP
+As the documentation says: plain is the preferred scrollbar for the
+author. The \f(CW\*(C`secondaryScroll\*(C'\fR configures urxvt to scroll in full-screen
+apps, like screen, so lines scrolled out of screen end up in urxvt's
+scrollback buffer.
+.PP
+.Vb 7
+\&   URxvt.background:       #000000
+\&   URxvt.foreground:       gray90
+\&   URxvt.color7:           gray90
+\&   URxvt.colorBD:          #ffffff
+\&   URxvt.cursorColor:      #e0e080
+\&   URxvt.throughColor:     #8080f0
+\&   URxvt.highlightColor:   #f0f0f0
+.Ve
+.PP
+Some colours. Not sure which ones are being used or even non\-defaults, but
+these are in my .Xdefaults. Most notably, they set foreground/background
+to light gray/black, and also make sure that the colour 7 matches the
+default foreground colour.
+.PP
+.Vb 1
+\&   URxvt.underlineColor:   yellow
+.Ve
+.PP
+Another colour, makes underline lines look different. Sometimes hurts, but
+is mostly a nice effect.
+.PP
+.Vb 4
+\&   URxvt.geometry:         154x36
+\&   URxvt.loginShell:       false
+\&   URxvt.meta:             ignore
+\&   URxvt.utmpInhibit:      true
+.Ve
+.PP
+Uh, well, should be mostly self\-explanatory. By specifying some defaults
+manually, I can quickly switch them for testing.
+.PP
+.Vb 1
+\&   URxvt.saveLines:        8192
+.Ve
+.PP
+A large scrollback buffer is essential. Really.
+.PP
+.Vb 1
+\&   URxvt.mapAlert:         true
+.Ve
+.PP
+The only case I use it is for my \s-1IRC\s0 window, which I like to keep
+iconified till people msg me (which beeps).
+.PP
+.Vb 1
+\&   URxvt.visualBell:       true
+.Ve
+.PP
+The audible bell is often annoying, especially when in a crowd.
+.PP
+.Vb 1
+\&   URxvt.insecure:         true
+.Ve
+.PP
+Please don't hack my mutt! Ooops...
+.PP
+.Vb 1
+\&   URxvt.pastableTabs:     false
+.Ve
+.PP
+I once thought this is a great idea.
+.PP
+.Vb 9
+\&   urxvt.font:             9x15bold,\e
+\&                           \-misc\-fixed\-bold\-r\-normal\-\-15\-140\-75\-75\-c\-90\-iso10646\-1,\e
+\&                           \-misc\-fixed\-medium\-r\-normal\-\-15\-140\-75\-75\-c\-90\-iso10646\-1, \e
+\&                           [codeset=JISX0208]xft:Kochi Gothic, \e
+\&                           xft:Bitstream Vera Sans Mono:autohint=true, \e
+\&                           xft:Code2000:antialias=false
+\&   urxvt.boldFont:         \-xos4\-terminus\-bold\-r\-normal\-\-14\-140\-72\-72\-c\-80\-iso8859\-15
+\&   urxvt.italicFont:       xft:Bitstream Vera Sans Mono:italic:autohint=true
+\&   urxvt.boldItalicFont:   xft:Bitstream Vera Sans Mono:bold:italic:autohint=true
+.Ve
+.PP
+I wrote rxvt-unicode to be able to specify fonts exactly. So don't be
+overwhelmed. A special note: the \f(CW\*(C`9x15bold\*(C'\fR mentioned above is actually
+the version from XFree\-3.3, as XFree\-4 replaced it by a totally different
+font (different glyphs for \f(CW\*(C`;\*(C'\fR and many other harmless characters),
+while the second font is actually the \f(CW\*(C`9x15bold\*(C'\fR from XFree4/XOrg. The
+bold version has less chars than the medium version, so I use it for rare
+characters, too. When editing sources with vim, I use italic for comments
+and other stuff, which looks quite good with Bitstream Vera anti\-aliased.
+.PP
+Terminus is a quite bad font (many very wrong glyphs), but for most of my
+purposes, it works, and gives a different look, as my normal (Non\-bold)
+font is already bold, and I want to see a difference between bold and
+normal fonts.
+.PP
+Please note that I used the \f(CW\*(C`urxvt\*(C'\fR instance name and not the \f(CW\*(C`URxvt\*(C'\fR
+class name. Thats because I use different configs for different purposes,
+for example, my \s-1IRC\s0 window is started with \f(CW\*(C`\-name IRC\*(C'\fR, and uses these
+defaults:
+.PP
+.Vb 9
+\&   IRC*title:              IRC
+\&   IRC*geometry:           87x12+535+542
+\&   IRC*saveLines:          0
+\&   IRC*mapAlert:           true
+\&   IRC*font:               suxuseuro
+\&   IRC*boldFont:           suxuseuro
+\&   IRC*colorBD:            white
+\&   IRC*keysym.M\-C\-1:       command:\e033]710;suxuseuro\e007\e033]711;suxuseuro\e007
+\&   IRC*keysym.M\-C\-2:       command:\e033]710;9x15bold\e007\e033]711;9x15bold\e007
+.Ve
+.PP
+\&\f(CW\*(C`Alt\-Shift\-1\*(C'\fR and \f(CW\*(C`Alt\-Shift\-2\*(C'\fR switch between two different font
+sizes. \f(CW\*(C`suxuseuro\*(C'\fR allows me to keep an eye (and actually read)
+stuff while keeping a very small window. If somebody pastes something
+complicated (e.g. japanese), I temporarily switch to a larger font.
+.PP
+The above is all in my \f(CW\*(C`.Xdefaults\*(C'\fR (I don't use \f(CW\*(C`.Xresources\*(C'\fR nor
+\&\f(CW\*(C`xrdb\*(C'\fR). I also have some resources in a separate \f(CW\*(C`.Xdefaults\-hostname\*(C'\fR
+file for different hosts, for example, on ym main desktop, I use:
+.PP
+.Vb 5
+\&   URxvt.keysym.C\-M\-q: command:\e033[3;5;5t
+\&   URxvt.keysym.C\-M\-y: command:\e033[3;5;606t
+\&   URxvt.keysym.C\-M\-e: command:\e033[3;1605;5t
+\&   URxvt.keysym.C\-M\-c: command:\e033[3;1605;606t
+\&   URxvt.keysym.C\-M\-p: perl:test
+.Ve
+.PP
+The first for keysym definitions allow me to quickly bring some windows
+in the layout I like most. Ion users might start laughing but will stop
+immediately when I tell them that I use my own Fvwm2 module for much the
+same effect as Ion provides, and I only very rarely use the above key
+combinations :\->
+.PP
 \fIWhy doesn't rxvt-unicode read my resources?\fR
 .IX Subsection "Why doesn't rxvt-unicode read my resources?"
 .PP
 Well, why, indeed? It does, in a way very similar to other X
 applications. Most importantly, this means that if you or your \s-1OS\s0 loads
 resources into the X display (the right way to do it), rxvt-unicode will
 ignore any resource files in your home directory. It will only read
-\&\fI$HOME/.Xdefaults\fR when no resources are attached to the display.
+\&\fI\f(CI$HOME\fI/.Xdefaults\fR when no resources are attached to the display.
 .PP
-If you have or use an \fI$HOME/.Xresources\fR file, chances are that
+If you have or use an \fI\f(CI$HOME\fI/.Xresources\fR file, chances are that
 resources are loaded into your X\-server. In this case, you have to
 re-login after every change (or run \fIxrdb \-merge \f(CI$HOME\fI/.Xresources\fR).
 .PP
 Also consider the form resources have to use:
 .PP
 .Vb 1
 \&  URxvt.resource: value
 .Ve
 .PP
 If you want to use another form (there are lots of different ways of
-specifying resources), make sure you understand wether and why it
+specifying resources), make sure you understand whether and why it
 works. If unsure, use the form above.
 .PP
 \fIWhen I log-in to another system it tells me about missing terminfo data?\fR
 .IX Subsection "When I log-in to another system it tells me about missing terminfo data?"
 .PP
 The correct solution for this problem is to install the terminfo, this can
 be done like this (with ncurses' infocmp):
 .PP
 .Vb 2
 \&   REMOTE=remotesystem.domain
-\&   infocmp rxvt-unicode | ssh $REMOTE "cat >/tmp/ti && tic /tmp/ti"
+\&   infocmp rxvt\-unicode | ssh $REMOTE "cat >/tmp/ti && tic /tmp/ti"
 .Ve
 .PP
 \&... or by installing rxvt-unicode normally on the remote system,
 .PP
 If you cannot or do not want to do this, then you can simply set
 One reason you might want this is that some distributions or operating
 systems still compile some programs using the long-obsoleted termcap
 library (Fedora Core's bash is one example) and rely on a termcap entry
 for \f(CW\*(C`rxvt\-unicode\*(C'\fR.
 .PP
-You could use rxvt's termcap entry with resonable results in many cases.
+You could use rxvt's termcap entry with reasonable results in many cases.
 You can also create a termcap entry by using terminfo's infocmp program
 like this:
 .PP
 .Vb 1
-\&   infocmp -C rxvt-unicode
+\&   infocmp \-C rxvt\-unicode
 .Ve
 .PP
 Or you could use this termcap entry, generated by the command above:
 .PP
-.Vb 20
+.Vb 10
-\&   rxvt-unicode|rxvt-unicode terminal (X Window System):\e
+\&   rxvt\-unicode|rxvt\-unicode terminal (X Window System):\e
 \&           :am:bw:eo:km:mi:ms:xn:xo:\e
 \&           :co#80:it#8:li#24:lm#0:\e
 \&           :AL=\eE[%dL:DC=\eE[%dP:DL=\eE[%dM:DO=\eE[%dB:IC=\eE[%d@:\e
 \&           :K1=\eEOw:K2=\eEOu:K3=\eEOy:K4=\eEOq:K5=\eEOs:LE=\eE[%dD:\e
 \&           :RI=\eE[%dC:SF=\eE[%dS:SR=\eE[%dT:UP=\eE[%dA:ae=\eE(B:al=\eE[L:\e
 .PP
 \fIWhy does \f(CI\*(C`ls\*(C'\fI no longer have coloured output?\fR
 .IX Subsection "Why does ls no longer have coloured output?"
 .PP
 The \f(CW\*(C`ls\*(C'\fR in the \s-1GNU\s0 coreutils unfortunately doesn't use terminfo to
-decide wether a terminal has colour, but uses it's own configuration
+decide whether a terminal has colour, but uses its own configuration
-file. Needless to say, \f(CW\*(C`rxvt\-unicode\*(C'\fR is not in it's default file (among
+file. Needless to say, \f(CW\*(C`rxvt\-unicode\*(C'\fR is not in its default file (among
 with most other terminals supporting colour). Either add:
 .PP
 .Vb 1
-\&   TERM rxvt-unicode
+\&   TERM rxvt\-unicode
 .Ve
 .PP
 to \f(CW\*(C`/etc/DIR_COLORS\*(C'\fR or simply add:
 .PP
 .Vb 1
-\&   alias ls='ls --color=auto'
+\&   alias ls='ls \-\-color=auto'
 .Ve
 .PP
 to your \f(CW\*(C`.profile\*(C'\fR or \f(CW\*(C`.bashrc\*(C'\fR.
 .PP
 \fIWhy doesn't vim/emacs etc. use the 88 colour mode?\fR
 .PP
 The best thing is to fix your startup environment, as you will likely run
 into other problems. If nothing works you can try this in your .profile.
 .PP
 .Vb 1
-\&  printf '\ee]701;%s\e007' "$LC_CTYPE"
+\&  printf '\e33]701;%s\e007' "$LC_CTYPE"
 .Ve
 .PP
 If this doesn't work, then maybe you use a \f(CW\*(C`LC_CTYPE\*(C'\fR specification not
 supported on your systems. Some systems have a \f(CW\*(C`locale\*(C'\fR command which
 displays this (also, \f(CW\*(C`perl \-e0\*(C'\fR can be used to check locale settings, as
 The reasons is that there exists a perfectly fine mechanism for selecting
 the encoding, doing I/O and (most important) communicating this to all
 applications so everybody agrees on character properties such as width
 and code number. This mechanism is the \fIlocale\fR. Applications not using
 that info will have problems (for example, \f(CW\*(C`xterm\*(C'\fR gets the width of
-characters wrong as it uses it's own, locale-independent table under all
+characters wrong as it uses its own, locale-independent table under all
 locales).
 .PP
 Rxvt-unicode uses the \f(CW\*(C`LC_CTYPE\*(C'\fR locale category to select encoding. All
 programs doing the same (that is, most) will automatically agree in the
 interpretation of characters.
 .PP
 Yes, using an escape sequence. Try something like this, which sets
 rxvt\-unicode's idea of \f(CW\*(C`LC_CTYPE\*(C'\fR.
 .PP
 .Vb 1
-\&  printf '\ee]701;%s\e007' ja_JP.SJIS
+\&  printf '\e33]701;%s\e007' ja_JP.SJIS
 .Ve
 .PP
 See also the previous answer.
 .PP
 Sometimes this capability is rather handy when you want to work in
 one locale (e.g. \f(CW\*(C`de_DE.UTF\-8\*(C'\fR) but some programs don't support it
 (e.g. \s-1UTF\-8\s0). For example, I use this script to start \f(CW\*(C`xjdic\*(C'\fR, which
 first switches to a locale supported by xjdic and back later:
 .PP
 .Vb 3
-\&   printf '\ee]701;%s\e007' ja_JP.SJIS
+\&   printf '\e33]701;%s\e007' ja_JP.SJIS
-\&   xjdic -js
+\&   xjdic \-js
-\&   printf '\ee]701;%s\e007' de_DE.UTF-8
+\&   printf '\e33]701;%s\e007' de_DE.UTF\-8
 .Ve
 .PP
 You can also use xterm's \f(CW\*(C`luit\*(C'\fR program, which usually works fine, except
 for some locales where character width differs between program\- and
 rxvt\-unicode\-locales.
 .PP
+\fII have problems getting my input method working.\fR
+.IX Subsection "I have problems getting my input method working."
+.PP
+Try a search engine, as this is slightly different for every input method server.
+.PP
+Here is a checklist:
+.IP "\- Make sure your locale \fIand\fR the imLocale are supported on your \s-1OS\s0." 4
+.IX Item "- Make sure your locale and the imLocale are supported on your OS."
+Try \f(CW\*(C`locale \-a\*(C'\fR or check the documentation for your \s-1OS\s0.
+.IP "\- Make sure your locale or imLocale matches a locale supported by your \s-1XIM\s0." 4
+.IX Item "- Make sure your locale or imLocale matches a locale supported by your XIM."
+For example, \fBkinput2\fR does not support \s-1UTF\-8\s0 locales, you should use
+\&\f(CW\*(C`ja_JP.EUC\-JP\*(C'\fR or equivalent.
+.IP "\- Make sure your \s-1XIM\s0 server is actually running." 4
+.IX Item "- Make sure your XIM server is actually running."
+.PD 0
+.ie n .IP "\- Make sure the ""XMODIFIERS""\fR environment variable is set correctly when \fIstarting rxvt\-unicode." 4
+.el .IP "\- Make sure the \f(CWXMODIFIERS\fR environment variable is set correctly when \fIstarting\fR rxvt\-unicode." 4
+.IX Item "- Make sure the XMODIFIERS environment variable is set correctly when starting rxvt-unicode."
+.PD
+When you want to use e.g. \fBkinput2\fR, it must be set to
+\&\f(CW\*(C`@im=kinput2\*(C'\fR. For \fBscim\fR, use \f(CW\*(C`@im=SCIM\*(C'\fR. You can see what input
+method servers are running with this command:
+.Sp
+.Vb 1
+\&   xprop \-root XIM_SERVERS
+.Ve
+.IP "" 4
+.PP
 \fIMy input method wants <some encoding> but I want \s-1UTF\-8\s0, what can I do?\fR
 .IX Subsection "My input method wants <some encoding> but I want UTF-8, what can I do?"
 .PP
 You can specify separate locales for the input method and the rest of the
 terminal, using the resource \f(CW\*(C`imlocale\*(C'\fR:
 .PP
 .Vb 1
-\&   URxvt.imlocale: ja_JP.EUC-JP
+\&   URxvt.imlocale: ja_JP.EUC\-JP
 .Ve
 .PP
 Now you can start your terminal with \f(CW\*(C`LC_CTYPE=ja_JP.UTF\-8\*(C'\fR and still
-use your input method. Please note, however, that you will not be able to
+use your input method. Please note, however, that, depending on your Xlib
-input characters outside \f(CW\*(C`EUC\-JP\*(C'\fR in a normal way then, as your input
+version, you may not be able to input characters outside \f(CW\*(C`EUC\-JP\*(C'\fR in a
-method limits you.
+normal way then, as your input method limits you.
 .PP
 \fIRxvt-unicode crashes when the X Input Method changes or exits.\fR
 .IX Subsection "Rxvt-unicode crashes when the X Input Method changes or exits."
 .PP
 Unfortunately, this is unavoidable, as the \s-1XIM\s0 protocol is racy by
 \fII am maintaining rxvt-unicode for distribution/OS \s-1XXX\s0, any recommendation?\fR
 .IX Subsection "I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation?"
 .PP
 You should build one binary with the default options. \fIconfigure\fR
 now enables most useful options, and the trend goes to making them
-runtime\-switchable, too, so there is usually no drawback to enbaling them,
+runtime\-switchable, too, so there is usually no drawback to enabling them,
 except higher disk and possibly memory usage. The perl interpreter should
 be enabled, as important functionality (menus, selection, likely more in
 the future) depends on it.
 .PP
 You should not overwrite the \f(CW\*(C`perl\-ext\-common\*(C'\fR snd \f(CW\*(C`perl\-ext\*(C'\fR resources
 \fII am on FreeBSD and rxvt-unicode does not seem to work at all.\fR
 .IX Subsection "I am on FreeBSD and rxvt-unicode does not seem to work at all."
 .PP
 Rxvt-unicode requires the symbol \f(CW\*(C`_\|_STDC_ISO_10646_\|_\*(C'\fR to be defined
 in your compile environment, or an implementation that implements it,
-wether it defines the symbol or not. \f(CW\*(C`_\|_STDC_ISO_10646_\|_\*(C'\fR requires that
+whether it defines the symbol or not. \f(CW\*(C`_\|_STDC_ISO_10646_\|_\*(C'\fR requires that
 \&\fBwchar_t\fR is represented as unicode.
 .PP
-As you might have guessed, FreeBSD does neither define this symobl nor
+As you might have guessed, FreeBSD does neither define this symbol nor
-does it support it. Instead, it uses it's own internal representation of
+does it support it. Instead, it uses its own internal representation of
 \&\fBwchar_t\fR. This is, of course, completely fine with respect to standards.
 .PP
 However, that means rxvt-unicode only works in \f(CW\*(C`POSIX\*(C'\fR, \f(CW\*(C`ISO\-8859\-1\*(C'\fR and
 \&\f(CW\*(C`UTF\-8\*(C'\fR locales under FreeBSD (which all use Unicode as \fBwchar_t\fR.
 .PP
 At the time of this writing, cygwin didn't seem to support any multi-byte
 encodings (you might try \f(CW\*(C`LC_CTYPE=C\-UTF\-8\*(C'\fR), so you are likely limited
 to 8\-bit encodings.
 .SH "RXVT-UNICODE TECHNICAL REFERENCE"
 .IX Header "RXVT-UNICODE TECHNICAL REFERENCE"
-.SH "DESCRIPTION"
-.IX Header "DESCRIPTION"
 The rest of this document describes various technical aspects of
 \&\fBrxvt-unicode\fR. First the description of supported command sequences,
 followed by pixmap support and last by a description of all features
 selectable at \f(CW\*(C`configure\*(C'\fR time.
-.SH "Definitions"
+.Sh "Definitions"
-.IX Header "Definitions"
+.IX Subsection "Definitions"
 .ie n .IP "\fB\fB""c""\fB\fR" 4
 .el .IP "\fB\f(CBc\fB\fR" 4
 .IX Item "c"
 The literal character c.
 .ie n .IP "\fB\fB""C""\fB\fR" 4
 parameters, separated by \f(CW\*(C`;\*(C'\fR character(s).
 .ie n .IP "\fB\fB""Pt""\fB\fR" 4
 .el .IP "\fB\f(CBPt\fB\fR" 4
 .IX Item "Pt"
 A text parameter composed of printable characters.
-.SH "Values"
+.Sh "Values"
-.IX Header "Values"
+.IX Subsection "Values"
 .ie n .IP "\fB\fB""ENQ""\fB\fR" 4
 .el .IP "\fB\f(CBENQ\fB\fR" 4
 .IX Item "ENQ"
 Enquiry (Ctrl\-E) = Send Device Attributes (\s-1DA\s0)
 request attributes from terminal. See \fB\f(CB\*(C`ESC [ Ps c\*(C'\fB\fR.
 Switch to Standard Character Set
 .ie n .IP "\fB\fB""SPC""\fB\fR" 4
 .el .IP "\fB\f(CBSPC\fB\fR" 4
 .IX Item "SPC"
 Space Character
-.SH "Escape Sequences"
+.Sh "Escape Sequences"
-.IX Header "Escape Sequences"
+.IX Subsection "Escape Sequences"
 .ie n .IP "\fB\fB""ESC # 8""\fB\fR" 4
 .el .IP "\fB\f(CBESC # 8\fB\fR" 4
 .IX Item "ESC # 8"
 \&\s-1DEC\s0 Screen Alignment Test (\s-1DECALN\s0)
 .ie n .IP "\fB\fB""ESC 7""\fB\fR" 4
 C = <	Multinational character set unimplemented
 C = 5 	Finnish character set unimplemented
 C = C 	Finnish character set unimplemented
 C = K 	German character set unimplemented
 .TE
 .PP
 .IX Xref "CSI"
-.SH "CSI (Command Sequence Introducer) Sequences"
+.Sh "\s-1CSI\s0 (Command Sequence Introducer) Sequences"
-.IX Header "CSI (Command Sequence Introducer) Sequences"
+.IX Subsection "CSI (Command Sequence Introducer) Sequences"
 .ie n .IP "\fB\fB""ESC [ Ps @""\fB\fR" 4
 .el .IP "\fB\f(CBESC [ Ps @\fB\fR" 4
 .IX Item "ESC [ Ps @"
 Insert \fB\f(CB\*(C`Ps\*(C'\fB\fR (Blank) Character(s) [default: 1] (\s-1ICH\s0)
 .IX Xref "ESCOBPsA"
 l l .
 Ps = 0	Clear Below (default)
 Ps = 1	Clear Above
 Ps = 2	Clear All
 .TE
 .ie n .IP "\fB\fB""ESC [ Ps K""\fB\fR" 4
 .el .IP "\fB\f(CBESC [ Ps K\fB\fR" 4
 .IX Item "ESC [ Ps K"
 Erase in Line (\s-1EL\s0)
 .TS
 l l .
 Ps = 0	Clear to Right (default)
 Ps = 1	Clear to Left
 Ps = 2	Clear All
 .TE
 .ie n .IP "\fB\fB""ESC [ Ps L""\fB\fR" 4
 .el .IP "\fB\f(CBESC [ Ps L\fB\fR" 4
 .IX Item "ESC [ Ps L"
 Insert \fB\f(CB\*(C`Ps\*(C'\fB\fR Line(s) [default: 1] (\s-1IL\s0)
 .ie n .IP "\fB\fB""ESC [ Ps M""\fB\fR" 4
 l l .
 Ps = 0	Tab Set (HTS)
 Ps = 2	Tab Clear (TBC), Clear Current Column (default)
 Ps = 5	Tab Clear (TBC), Clear All
 .TE
 .ie n .IP "\fB\fB""ESC [ Ps X""\fB\fR" 4
 .el .IP "\fB\f(CBESC [ Ps X\fB\fR" 4
 .IX Item "ESC [ Ps X"
 Erase \fB\f(CB\*(C`Ps\*(C'\fB\fR Character(s) [default: 1] (\s-1ECH\s0)
 .ie n .IP "\fB\fB""ESC [ Ps Z""\fB\fR" 4
 .TS
 l l .
 Ps = 0	Clear Current Column (default)
 Ps = 3	Clear All (TBC)
 .TE
 .ie n .IP "\fB\fB""ESC [ Pm h""\fB\fR" 4
 .el .IP "\fB\f(CBESC [ Pm h\fB\fR" 4
 .IX Item "ESC [ Pm h"
 Set Mode (\s-1SM\s0). See \fB\f(CB\*(C`ESC [ Pm l\*(C'\fB\fR sequence for description of \f(CW\*(C`Pm\*(C'\fR.
 .ie n .IP "\fB\fB""ESC [ Ps i""\fB\fR" 4
 l l .
 Ps = 0	print screen (MC0)
 Ps = 4	disable transparent print mode (MC4)
 Ps = 5	enable transparent print mode (MC5)
 .TE
 .ie n .IP "\fB\fB""ESC [ Pm l""\fB\fR" 4
 .el .IP "\fB\f(CBESC [ Pm l\fB\fR" 4
 .IX Item "ESC [ Pm l"
 Reset Mode (\s-1RM\s0)
 .RS 4
 .TS
 l l .
 h	Insert Mode (SMIR)
 l	Replace Mode (RMIR)
 .TE
 .PD 0
 .ie n .IP "\fB\fB""Ps = 20""\fB\fR (partially implemented)" 4
 .el .IP "\fB\f(CBPs = 20\fB\fR (partially implemented)" 4
 .IX Item "Ps = 20 (partially implemented)"
 .TS
 l l .
 h	Automatic Newline (LNM)
 l	Normal Linefeed (LNM)
 .TE
 .RE
 .RS 4
 .RE
 .ie n .IP "\fB\fB""ESC [ Pm m""\fB\fR" 4
 .el .IP "\fB\f(CBESC [ Pm m\fB\fR" 4
 Ps = 95 / 105	fg/bg Bright Magenta
 Ps = 96 / 106	fg/bg Bright Cyan
 Ps = 97 / 107	fg/bg Bright White
 Ps = 99 / 109	fg/bg Bright Default
 .TE
 .ie n .IP "\fB\fB""ESC [ Ps n""\fB\fR" 4
 .el .IP "\fB\f(CBESC [ Ps n\fB\fR" 4
 .IX Item "ESC [ Ps n"
 Device Status Report (\s-1DSR\s0)
 .TS
 Ps = 5	Status Report ESC [ 0 n (``OK'')
 Ps = 6	Report Cursor Position (CPR) [row;column] as ESC [ r ; c R
 Ps = 7	Request Display Name
 Ps = 8	Request Version Number (place in window title)
 .TE
 .ie n .IP "\fB\fB""ESC [ Ps;Ps r""\fB\fR" 4
 .el .IP "\fB\f(CBESC [ Ps;Ps r\fB\fR" 4
 .IX Item "ESC [ Ps;Ps r"
 Set Scrolling Region [top;bottom]
 [default: full size of window] (\s-1CSR\s0)
 Ps = 19	Currently the same as Ps = 18, but responds with Ps = 9
 Ps = 20	Reports icon label (ESC ] L NAME \234)
 Ps = 21	Reports window title (ESC ] l NAME \234)
 Ps = 24..	Set window height to Ps rows
 .TE
 .ie n .IP "\fB\fB""ESC [ u""\fB\fR" 4
 .el .IP "\fB\f(CBESC [ u\fB\fR" 4
 .IX Item "ESC [ u"
 Restore Cursor
 .ie n .IP "\fB\fB""ESC [ Ps x""\fB\fR" 4
 .IX Item "ESC [ Ps x"
 Request Terminal Parameters (\s-1DECREQTPARM\s0)
 .PP
 .IX Xref "PrivateModes"
-.SH "DEC Private Modes"
+.Sh "\s-1DEC\s0 Private Modes"
-.IX Header "DEC Private Modes"
+.IX Subsection "DEC Private Modes"
 .ie n .IP "\fB\fB""ESC [ ? Pm h""\fB\fR" 4
 .el .IP "\fB\f(CBESC [ ? Pm h\fB\fR" 4
 .IX Item "ESC [ ? Pm h"
 \&\s-1DEC\s0 Private Mode Set (\s-1DECSET\s0)
 .ie n .IP "\fB\fB""ESC [ ? Pm l""\fB\fR" 4
 .ie n .IP "\fB\fB""ESC [ ? Pm t""\fB\fR" 4
 .el .IP "\fB\f(CBESC [ ? Pm t\fB\fR" 4
 .IX Item "ESC [ ? Pm t"
 Toggle \s-1DEC\s0 Private Mode Values (rxvt extension). \fIwhere\fR
 .RS 4
-.ie n .IP "\fB\fB""Ps = 1""\fB\fR (\s-1DECCKM\s0)" 4
+.ie n .IP "\fB\fB""Pm = 1""\fB\fR (\s-1DECCKM\s0)" 4
-.el .IP "\fB\f(CBPs = 1\fB\fR (\s-1DECCKM\s0)" 4
+.el .IP "\fB\f(CBPm = 1\fB\fR (\s-1DECCKM\s0)" 4
-.IX Item "Ps = 1 (DECCKM)"
+.IX Item "Pm = 1 (DECCKM)"
 .TS
 l l .
 h	Application Cursor Keys
 l	Normal Cursor Keys
 .TE
 .PD 0
-.ie n .IP "\fB\fB""Ps = 2""\fB\fR (\s-1ANSI/VT52\s0 mode)" 4
+.ie n .IP "\fB\fB""Pm = 2""\fB\fR (\s-1ANSI/VT52\s0 mode)" 4
-.el .IP "\fB\f(CBPs = 2\fB\fR (\s-1ANSI/VT52\s0 mode)" 4
+.el .IP "\fB\f(CBPm = 2\fB\fR (\s-1ANSI/VT52\s0 mode)" 4
-.IX Item "Ps = 2 (ANSI/VT52 mode)"
+.IX Item "Pm = 2 (ANSI/VT52 mode)"
 .TS
 l l .
 h	Enter VT52 mode
 l	Enter VT52 mode
 .TE
-.ie n .IP "\fB\fB""Ps = 3""\fB\fR" 4
+.ie n .IP "\fB\fB""Pm = 3""\fB\fR" 4
-.el .IP "\fB\f(CBPs = 3\fB\fR" 4
+.el .IP "\fB\f(CBPm = 3\fB\fR" 4
-.IX Item "Ps = 3"
+.IX Item "Pm = 3"
 .TS
 l l .
 h	132 Column Mode (DECCOLM)
 l	80 Column Mode (DECCOLM)
 .TE
-.ie n .IP "\fB\fB""Ps = 4""\fB\fR" 4
+.ie n .IP "\fB\fB""Pm = 4""\fB\fR" 4
-.el .IP "\fB\f(CBPs = 4\fB\fR" 4
+.el .IP "\fB\f(CBPm = 4\fB\fR" 4
-.IX Item "Ps = 4"
+.IX Item "Pm = 4"
 .TS
 l l .
 h	Smooth (Slow) Scroll (DECSCLM)
 l	Jump (Fast) Scroll (DECSCLM)
 .TE
-.ie n .IP "\fB\fB""Ps = 5""\fB\fR" 4
+.ie n .IP "\fB\fB""Pm = 5""\fB\fR" 4
-.el .IP "\fB\f(CBPs = 5\fB\fR" 4
+.el .IP "\fB\f(CBPm = 5\fB\fR" 4
-.IX Item "Ps = 5"
+.IX Item "Pm = 5"
 .TS
 l l .
 h	Reverse Video (DECSCNM)
 l	Normal Video (DECSCNM)
 .TE
-.ie n .IP "\fB\fB""Ps = 6""\fB\fR" 4
+.ie n .IP "\fB\fB""Pm = 6""\fB\fR" 4
-.el .IP "\fB\f(CBPs = 6\fB\fR" 4
+.el .IP "\fB\f(CBPm = 6\fB\fR" 4
-.IX Item "Ps = 6"
+.IX Item "Pm = 6"
 .TS
 l l .
 h	Origin Mode (DECOM)
 l	Normal Cursor Mode (DECOM)
 .TE
-.ie n .IP "\fB\fB""Ps = 7""\fB\fR" 4
+.ie n .IP "\fB\fB""Pm = 7""\fB\fR" 4
-.el .IP "\fB\f(CBPs = 7\fB\fR" 4
+.el .IP "\fB\f(CBPm = 7\fB\fR" 4
-.IX Item "Ps = 7"
+.IX Item "Pm = 7"
 .TS
 l l .
 h	Wraparound Mode (DECAWM)
 l	No Wraparound Mode (DECAWM)
 .TE
-.ie n .IP "\fB\fB""Ps = 8""\fB\fR \fIunimplemented\fR" 4
+.ie n .IP "\fB\fB""Pm = 8""\fB\fR \fIunimplemented\fR" 4
-.el .IP "\fB\f(CBPs = 8\fB\fR \fIunimplemented\fR" 4
+.el .IP "\fB\f(CBPm = 8\fB\fR \fIunimplemented\fR" 4
-.IX Item "Ps = 8 unimplemented"
+.IX Item "Pm = 8 unimplemented"
 .TS
 l l .
 h	Auto-repeat Keys (DECARM)
 l	No Auto-repeat Keys (DECARM)
 .TE
-.ie n .IP "\fB\fB""Ps = 9""\fB\fR X10 XTerm" 4
+.ie n .IP "\fB\fB""Pm = 9""\fB\fR X10 XTerm" 4
-.el .IP "\fB\f(CBPs = 9\fB\fR X10 XTerm" 4
+.el .IP "\fB\f(CBPm = 9\fB\fR X10 XTerm" 4
-.IX Item "Ps = 9 X10 XTerm"
+.IX Item "Pm = 9 X10 XTerm"
 .TS
 l l .
 h	Send Mouse X & Y on button press.
 l	No mouse reporting.
 .TE
-.ie n .IP "\fB\fB""Ps = 25""\fB\fR" 4
+.ie n .IP "\fB\fB""Pm = 25""\fB\fR" 4
-.el .IP "\fB\f(CBPs = 25\fB\fR" 4
+.el .IP "\fB\f(CBPm = 25\fB\fR" 4
-.IX Item "Ps = 25"
+.IX Item "Pm = 25"
 .TS
 l l .
 h	Visible cursor {cnorm/cvvis}
 l	Invisible cursor {civis}
 .TE
-.ie n .IP "\fB\fB""Ps = 30""\fB\fR" 4
+.ie n .IP "\fB\fB""Pm = 30""\fB\fR" 4
-.el .IP "\fB\f(CBPs = 30\fB\fR" 4
+.el .IP "\fB\f(CBPm = 30\fB\fR" 4
-.IX Item "Ps = 30"
+.IX Item "Pm = 30"
 .TS
 l l .
 h	scrollBar visisble
 l	scrollBar invisisble
 .TE
-.ie n .IP "\fB\fB""Ps = 35""\fB\fR (\fBrxvt\fR)" 4
+.ie n .IP "\fB\fB""Pm = 35""\fB\fR (\fBrxvt\fR)" 4
-.el .IP "\fB\f(CBPs = 35\fB\fR (\fBrxvt\fR)" 4
+.el .IP "\fB\f(CBPm = 35\fB\fR (\fBrxvt\fR)" 4
-.IX Item "Ps = 35 (rxvt)"
+.IX Item "Pm = 35 (rxvt)"
 .TS
 l l .
 h	Allow XTerm Shift+key sequences
 l	Disallow XTerm Shift+key sequences
 .TE
-.ie n .IP "\fB\fB""Ps = 38""\fB\fR \fIunimplemented\fR" 4
+.ie n .IP "\fB\fB""Pm = 38""\fB\fR \fIunimplemented\fR" 4
-.el .IP "\fB\f(CBPs = 38\fB\fR \fIunimplemented\fR" 4
+.el .IP "\fB\f(CBPm = 38\fB\fR \fIunimplemented\fR" 4
-.IX Item "Ps = 38 unimplemented"
+.IX Item "Pm = 38 unimplemented"
 .PD
 Enter Tektronix Mode (\s-1DECTEK\s0)
-.ie n .IP "\fB\fB""Ps = 40""\fB\fR" 4
+.ie n .IP "\fB\fB""Pm = 40""\fB\fR" 4
-.el .IP "\fB\f(CBPs = 40\fB\fR" 4
+.el .IP "\fB\f(CBPm = 40\fB\fR" 4
-.IX Item "Ps = 40"
+.IX Item "Pm = 40"
 .TS
 l l .
 h	Allow 80/132 Mode
 l	Disallow 80/132 Mode
 .TE
 .PD 0
-.ie n .IP "\fB\fB""Ps = 44""\fB\fR \fIunimplemented\fR" 4
+.ie n .IP "\fB\fB""Pm = 44""\fB\fR \fIunimplemented\fR" 4
-.el .IP "\fB\f(CBPs = 44\fB\fR \fIunimplemented\fR" 4
+.el .IP "\fB\f(CBPm = 44\fB\fR \fIunimplemented\fR" 4
-.IX Item "Ps = 44 unimplemented"
+.IX Item "Pm = 44 unimplemented"
 .TS
 l l .
 h	Turn On Margin Bell
 l	Turn Off Margin Bell
 .TE
-.ie n .IP "\fB\fB""Ps = 45""\fB\fR \fIunimplemented\fR" 4
+.ie n .IP "\fB\fB""Pm = 45""\fB\fR \fIunimplemented\fR" 4
-.el .IP "\fB\f(CBPs = 45\fB\fR \fIunimplemented\fR" 4
+.el .IP "\fB\f(CBPm = 45\fB\fR \fIunimplemented\fR" 4
-.IX Item "Ps = 45 unimplemented"
+.IX Item "Pm = 45 unimplemented"
 .TS
 l l .
 h	Reverse-wraparound Mode
 l	No Reverse-wraparound Mode
 .TE
-.ie n .IP "\fB\fB""Ps = 46""\fB\fR \fIunimplemented\fR" 4
+.ie n .IP "\fB\fB""Pm = 46""\fB\fR \fIunimplemented\fR" 4
-.el .IP "\fB\f(CBPs = 46\fB\fR \fIunimplemented\fR" 4
+.el .IP "\fB\f(CBPm = 46\fB\fR \fIunimplemented\fR" 4
-.IX Item "Ps = 46 unimplemented"
+.IX Item "Pm = 46 unimplemented"
-.ie n .IP "\fB\fB""Ps = 47""\fB\fR" 4
+.ie n .IP "\fB\fB""Pm = 47""\fB\fR" 4
-.el .IP "\fB\f(CBPs = 47\fB\fR" 4
+.el .IP "\fB\f(CBPm = 47\fB\fR" 4
-.IX Item "Ps = 47"
+.IX Item "Pm = 47"
 .TS
 l l .
 h	Use Alternate Screen Buffer
 l	Use Normal Screen Buffer
 .TE
 .PD
 .IX Xref "Priv66"
-.ie n .IP "\fB\fB""Ps = 66""\fB\fR" 4
+.ie n .IP "\fB\fB""Pm = 66""\fB\fR" 4
-.el .IP "\fB\f(CBPs = 66\fB\fR" 4
+.el .IP "\fB\f(CBPm = 66\fB\fR" 4
-.IX Item "Ps = 66"
+.IX Item "Pm = 66"
 .TS
 l l .
 h	Application Keypad (DECPAM) == ESC =
 l	Normal Keypad (DECPNM) == ESC >
 .TE
 .PD 0
-.ie n .IP "\fB\fB""Ps = 67""\fB\fR" 4
+.ie n .IP "\fB\fB""Pm = 67""\fB\fR" 4
-.el .IP "\fB\f(CBPs = 67\fB\fR" 4
+.el .IP "\fB\f(CBPm = 67\fB\fR" 4
-.IX Item "Ps = 67"
+.IX Item "Pm = 67"
 .TS
 l l .
 h	Backspace key sends BS (DECBKM)
 l	Backspace key sends DEL
 .TE
-.ie n .IP "\fB\fB""Ps = 1000""\fB\fR (X11 XTerm)" 4
+.ie n .IP "\fB\fB""Pm = 1000""\fB\fR (X11 XTerm)" 4
-.el .IP "\fB\f(CBPs = 1000\fB\fR (X11 XTerm)" 4
+.el .IP "\fB\f(CBPm = 1000\fB\fR (X11 XTerm)" 4
-.IX Item "Ps = 1000 (X11 XTerm)"
+.IX Item "Pm = 1000 (X11 XTerm)"
 .TS
 l l .
 h	Send Mouse X & Y on button press and release.
 l	No mouse reporting.
 .TE
-.ie n .IP "\fB\fB""Ps = 1001""\fB\fR (X11 XTerm) \fIunimplemented\fR" 4
+.ie n .IP "\fB\fB""Pm = 1001""\fB\fR (X11 XTerm) \fIunimplemented\fR" 4
-.el .IP "\fB\f(CBPs = 1001\fB\fR (X11 XTerm) \fIunimplemented\fR" 4
+.el .IP "\fB\f(CBPm = 1001\fB\fR (X11 XTerm) \fIunimplemented\fR" 4
-.IX Item "Ps = 1001 (X11 XTerm) unimplemented"
+.IX Item "Pm = 1001 (X11 XTerm) unimplemented"
 .TS
 l l .
 h	Use Hilite Mouse Tracking.
 l	No mouse reporting.
 .TE
-.ie n .IP "\fB\fB""Ps = 1010""\fB\fR (\fBrxvt\fR)" 4
+.ie n .IP "\fB\fB""Pm = 1010""\fB\fR (\fBrxvt\fR)" 4
-.el .IP "\fB\f(CBPs = 1010\fB\fR (\fBrxvt\fR)" 4
+.el .IP "\fB\f(CBPm = 1010\fB\fR (\fBrxvt\fR)" 4
-.IX Item "Ps = 1010 (rxvt)"
+.IX Item "Pm = 1010 (rxvt)"
 .TS
 l l .
 h	Don't scroll to bottom on TTY output
 l	Scroll to bottom on TTY output
 .TE
-.ie n .IP "\fB\fB""Ps = 1011""\fB\fR (\fBrxvt\fR)" 4
+.ie n .IP "\fB\fB""Pm = 1011""\fB\fR (\fBrxvt\fR)" 4
-.el .IP "\fB\f(CBPs = 1011\fB\fR (\fBrxvt\fR)" 4
+.el .IP "\fB\f(CBPm = 1011\fB\fR (\fBrxvt\fR)" 4
-.IX Item "Ps = 1011 (rxvt)"
+.IX Item "Pm = 1011 (rxvt)"
 .TS
 l l .
 h	Scroll to bottom when a key is pressed
 l	Don't scroll to bottom when a key is pressed
 .TE
-.ie n .IP "\fB\fB""Ps = 1021""\fB\fR (\fBrxvt\fR)" 4
+.ie n .IP "\fB\fB""Pm = 1021""\fB\fR (\fBrxvt\fR)" 4
-.el .IP "\fB\f(CBPs = 1021\fB\fR (\fBrxvt\fR)" 4
+.el .IP "\fB\f(CBPm = 1021\fB\fR (\fBrxvt\fR)" 4
-.IX Item "Ps = 1021 (rxvt)"
+.IX Item "Pm = 1021 (rxvt)"
 .TS
 l l .
 h	Bold/italic implies high intensity (see option -is)
 l	Font styles have no effect on intensity (Compile styles)
 .TE
-.ie n .IP "\fB\fB""Ps = 1047""\fB\fR" 4
+.ie n .IP "\fB\fB""Pm = 1047""\fB\fR" 4
-.el .IP "\fB\f(CBPs = 1047\fB\fR" 4
+.el .IP "\fB\f(CBPm = 1047\fB\fR" 4
-.IX Item "Ps = 1047"
+.IX Item "Pm = 1047"
 .TS
 l l .
 h	Use Alternate Screen Buffer
 l	Use Normal Screen Buffer - clear Alternate Screen Buffer if returning from it
 .TE
-.ie n .IP "\fB\fB""Ps = 1048""\fB\fR" 4
+.ie n .IP "\fB\fB""Pm = 1048""\fB\fR" 4
-.el .IP "\fB\f(CBPs = 1048\fB\fR" 4
+.el .IP "\fB\f(CBPm = 1048\fB\fR" 4
-.IX Item "Ps = 1048"
+.IX Item "Pm = 1048"
 .TS
 l l .
 h	Save cursor position
 l	Restore cursor position
 .TE
-.ie n .IP "\fB\fB""Ps = 1049""\fB\fR" 4
+.ie n .IP "\fB\fB""Pm = 1049""\fB\fR" 4
-.el .IP "\fB\f(CBPs = 1049\fB\fR" 4
+.el .IP "\fB\f(CBPm = 1049\fB\fR" 4
-.IX Item "Ps = 1049"
+.IX Item "Pm = 1049"
 .TS
 l l .
 h	Use Alternate Screen Buffer - clear Alternate Screen Buffer if switching to it
 l	Use Normal Screen Buffer
 .TE
 .RE
 .RS 4
 .RE
 .PD
 .PP
 .IX Xref "XTerm"
-.SH "XTerm Operating System Commands"
+.Sh "XTerm Operating System Commands"
-.IX Header "XTerm Operating System Commands"
+.IX Subsection "XTerm Operating System Commands"
 .ie n .IP "\fB\fB""ESC ] Ps;Pt ST""\fB\fR" 4
 .el .IP "\fB\f(CBESC ] Ps;Pt ST\fB\fR" 4
 .IX Item "ESC ] Ps;Pt ST"
 Set XTerm Parameters. 8\-bit \s-1ST:\s0 0x9c, 7\-bit \s-1ST\s0 sequence: \s-1ESC\s0 \e (0x1b,
 0x5c), backwards compatible terminator \s-1BEL\s0 (0x07) is also accepted. any
 Ps = 713	Set bold-italic fontset to Pt. Similar to Ps = 50 (Compile styles).
 Ps = 720	Move viewing window up by Pt lines, or clear scrollback buffer if Pt = 0 (Compile frills).
 Ps = 721	Move viewing window down by Pt lines, or clear scrollback buffer if Pt = 0 (Compile frills).
 Ps = 777	Call the perl extension with the given string, which should be of the form extension:parameters (Compile perl).
 .TE
-.PP
-.IX Xref "XPM"
 .SH "XPM"
 .IX Header "XPM"
 For the \s-1XPM\s0 XTerm escape sequence \fB\f(CB\*(C`ESC ] 20 ; Pt ST\*(C'\fB\fR then value
 of \fB\f(CB\*(C`Pt\*(C'\fB\fR can be the name of the background pixmap followed by a
 sequence of scaling/positioning commands separated by semi\-colons. The
 0	Button1 pressed
 1	Button2 pressed
 2	Button3 pressed
 3	button released (X11 mouse report)
 .TE
 .PP
 The upper bits of \fB\f(CB\*(C`<b>\*(C'\fB\fR indicate the modifiers when the
 button was pressed and are added together (X11 mouse report only):
 .ie n .IP "State = \fB\fB""(<b> \- SPACE) & 60""\fB\fR" 4
 .el .IP "State = \fB\f(CB(<b> \- SPACE) & 60\fB\fR" 4
 4	Shift
 8	Meta
 16	Control
 32	Double Click (rxvt extension)
 .TE
 Col = \fB\f(CB\*(C`<x> \- SPACE\*(C'\fB\fR
 .Sp
 Row = \fB\f(CB\*(C`<y> \- SPACE\*(C'\fB\fR
 .SH "Key Codes"
 .IX Header "Key Codes"
 XK_KP_6	6			ESC O v
 XK_KP_7	7			ESC O w
 XK_KP_8	8			ESC O x
 XK_KP_9	9			ESC O y
 .TE
 .SH "CONFIGURE OPTIONS"
 .IX Header "CONFIGURE OPTIONS"
 General hint: if you get compile errors, then likely your configuration
 hasn't been tested well. Either try with \f(CW\*(C`\-\-enable\-everything\*(C'\fR or use
 the \fI./reconf\fR script as a base for experiments. \fI./reconf\fR is used by
 zh_ext	rarely used but very big chinese encodigs
 jp	common japanese encodings
 jp_ext	rarely used but big japanese encodings
 kr	korean encodings
 .TE
 .IP "\-\-enable\-xim (default: on)" 4
 .IX Item "--enable-xim (default: on)"
 Add support for \s-1XIM\s0 (X Input Method) protocol. This allows using
 alternative input methods (e.g. kinput2) and will also correctly
 set up the input for people using dead keys or compose keys.
 disable this.
 .Sp
 A non-exhaustive list of features enabled by \f(CW\*(C`\-\-enable\-frills\*(C'\fR (possibly
 in combination with other switches) is:
 .Sp
-.Vb 15
+.Vb 10
-\&  MWM-hints
+\&  MWM\-hints
-\&  EWMH-hints (pid, utf8 names) and protocols (ping)
+\&  EWMH\-hints (pid, utf8 names) and protocols (ping)
-\&  seperate underline colour (-underlineColor)
+\&  seperate underline colour (\-underlineColor)
-\&  settable border widths and borderless switch (-w, -b, -bl)
+\&  settable border widths and borderless switch (\-w, \-b, \-bl)
-\&  visual depth selection (-depth)
+\&  visual depth selection (\-depth)
-\&  settable extra linespacing /-lsp)
+\&  settable extra linespacing /\-lsp)
-\&  iso-14755-2 and -3, and visual feedback
+\&  iso\-14755\-2 and \-3, and visual feedback
-\&  tripleclickwords (-tcw)
+\&  tripleclickwords (\-tcw)
-\&  settable insecure mode (-insecure)
+\&  settable insecure mode (\-insecure)
 \&  keysym remapping support
-\&  cursor blinking and underline cursor (-cb, -uc)
+\&  cursor blinking and underline cursor (\-cb, \-uc)
-\&  XEmbed support (-embed)
+\&  XEmbed support (\-embed)
-\&  user-pty (-pty-fd)
+\&  user\-pty (\-pty\-fd)
-\&  hold on exit (-hold)
+\&  hold on exit (\-hold)
-\&  skip builtin block graphics (-sbg)
+\&  skip builtin block graphics (\-sbg)
+\&  separate highlightcolor support (\-hc)
 .Ve
 .Sp
-It also enabled some non-essential features otherwise disabled, such as:
+It also enables some non-essential features otherwise disabled, such as:
 .Sp
 .Vb 11
-\&  some round-trip time optimisations
+\&  some round\-trip time optimisations
 \&  nearest color allocation on pseudocolor screens
 \&  UTF8_STRING supporr for selection
 \&  sgr modes 90..97 and 100..107
 \&  backindex and forwardindex escape sequences
 \&  view change/zero scorllback esacpe sequences
 .IX Item "--disable-new-selection"
 Remove support for mouse selection style like that of xterm.
 .IP "\-\-enable\-dmalloc (default: off)" 4
 .IX Item "--enable-dmalloc (default: off)"
 Use Gray Watson's malloc \- which is good for debugging See
-http://www.letters.com/dmalloc/ for details If you use either this or the
+<http://www.letters.com/dmalloc/> for details If you use either this or the
 next option, you may need to edit src/Makefile after compiling to point
 \&\s-1DINCLUDE\s0 and \s-1DLIB\s0 to the right places.
 .Sp
 You can only use either this option and the following (should
 you use either) .
 .IX Header "AUTHORS"
 Marc Lehmann <rxvt@schmorp.de> converted this document to pod and
 reworked it from the original Rxvt documentation, which was done by Geoff
 Wing <gcw@pobox.com>, who in turn used the XTerm documentation and other
 sources.
+.SH "POD ERRORS"
+.IX Header "POD ERRORS"
+Hey! \fBThe above document had some coding errors, which are explained below:\fR
+.IP "Around line 2952:" 4
+.IX Item "Around line 2952:"
+=back doesn't take any parameters, but you said =back  X<Mouse>
+.IP "Around line 3048:" 4
+.IX Item "Around line 3048:"
+=back doesn't take any parameters, but you said =back  X<KeyCodes>

Diff Legend

-–
+Removed lines
-+
+Added lines
-<
+Changed lines
->
+Changed lines

Comparing rxvt-unicode/doc/rxvt.7.man.in (file contents): Revision 1.66 by root, Tue Jan 31 21:04:14 2006 UTC vs. Revision 1.79 by root, Mon Aug 7 16:17:30 2006 UTC

Diff Legend

Comparing rxvt-unicode/doc/rxvt.7.man.in (file contents):
Revision 1.66 by root, Tue Jan 31 21:04:14 2006 UTC vs.
Revision 1.79 by root, Mon Aug 7 16:17:30 2006 UTC