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

Comparing rxvt-unicode/doc/rxvt.7.man.in (file contents):
Revision 1.28 by root, Thu Dec 22 16:44:10 2005 UTC vs.
Revision 1.60 by root, Tue Jan 31 01:00:49 2006 UTC

 .\}
 .rm #[ #] #H #V #F C
 .\" ========================================================================
 .\"
 .IX Title "rxvt 7"
-.TH rxvt 7 "2005-12-22" "6.0" "RXVT-UNICODE"
+.TH rxvt 7 "2006-01-31" "7.5" "RXVT-UNICODE"
 .SH "NAME"
 RXVT REFERENCE \- FAQ, command sequences and other background information
 .SH "SYNOPSIS"
 .IX Header "SYNOPSIS"
 .Vb 2
 .SH "DESCRIPTION"
 .IX Header "DESCRIPTION"
 This document contains the \s-1FAQ\s0, the \s-1RXVT\s0 \s-1TECHNICAL\s0 \s-1REFERENCE\s0 documenting
 all escape sequences, and other background information.
 .PP
-The newest version of this document is
+The newest version of this document is also available on the World Wide Web at
-also available on the World Wide Web at
 <http://cvs.schmorp.de/browse/*checkout*/rxvt\-unicode/doc/rxvt.7.html>.
 .SH "FREQUENTLY ASKED QUESTIONS"
 .IX Header "FREQUENTLY ASKED QUESTIONS"
+.Sh "The new selection selects pieces that are too big, how can I select single words?"
+.IX Subsection "The new selection selects pieces that are too big, how can I select single words?"
+If you want to select e.g. alphanumeric words, you can use the following
+setting:
+.PP
+.Vb 1
+\&   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]^`{|})]+)
+.Ve
+.PP
+Please also note that the \fILeftClick Shift-LeftClik\fR combination also
+selects words like the old code.
+.Sh "I don't like the new selection/popups/hotkeys/perl, how do I change/disable it?"
+.IX Subsection "I don't like the new selection/popups/hotkeys/perl, how do I change/disable it?"
+You can disable the perl extension completely by setting the
+\&\fBperl-ext-common\fR resource to the empty string, which also keeps
+rxvt-unicode from initialising perl, saving memory.
+.PP
+If you only want to disable specific features, you first have to
+identify which perl extension is responsible. For this, read the section
+\&\fB\s-1PREPACKAGED\s0 \s-1EXTENSIONS\s0\fR in the @@RXVT_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
+.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
+.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
+See next entry.
+.Sh "During rlogin/ssh/telnet/etc. sessions, clicking near the cursor outputs strange escape sequences, how do I fix this?"
+.IX Subsection "During rlogin/ssh/telnet/etc. sessions, clicking near the cursor outputs strange escape sequences, how do I fix this?"
+These are caused by the \f(CW\*(C`readline\*(C'\fR perl extension. Under normal
+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
+extension:
+.PP
+.Vb 1
+\&   URxvt.perl-ext-common: default,-readline
+.Ve
+.Sh "Why doesn't rxvt-unicode read my resources?"
+.IX Subsection "Why doesn't rxvt-unicode read my resources?"
+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.
+.PP
+If you have or use an \fI$HOME/.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
+works. If unsure, use the form above.
+.Sh "I can't get transparency working, what am I doing wrong?"
+.IX Subsection "I can't get transparency working, what am I doing wrong?"
+First of all, transparency isn't officially supported in rxvt\-unicode, so
+you are mostly on your own. Do not bug the author about it (but you may
+bug everybody else). Also, if you can't get it working consider it a rite
+of passage: ... and you failed.
+.PP
+Here are four ways to get transparency. \fBDo\fR read the manpage and option
+descriptions for the programs mentioned and rxvt\-unicode. Really, do it!
+.PP
+1. Use inheritPixmap:
+.PP
+.Vb 2
+\&   Esetroot wallpaper.jpg
+\&   @@RXVT_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:
+.PP
+.Vb 2
+\&   convert wallpaper.jpg -blur 20x20 -modulate 30 background.xpm
+\&   @@RXVT_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
+\&   @@RXVT_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
+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
+\&        -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.
+.Sh "Isn't rxvt supposed to be small? Don't all those features bloat?"
+.IX Subsection "Isn't rxvt supposed to be small? Don't all those features bloat?"
+I often get asked about this, and I think, no, they didn't cause extra
+bloat. If you compare a minimal rxvt and a minimal urxvt, you can see
+that the urxvt binary is larger (due to some encoding tables always being
+compiled in), but it actually uses less memory (\s-1RSS\s0) after startup. Even
+with \f(CW\*(C`\-\-disable\-everything\*(C'\fR, this comparison is a bit unfair, as many
+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
+\&  188985    9048   66616   18222    1788 urxvt --disable-everything
+.Ve
+.PP
+When you \f(CW\*(C`\-\-enable\-everything\*(C'\fR (which _is_ 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.
+.PP
+.Vb 3
+\&    text    data     bss     drs     rss filename
+\&  163431    2152      24   20123    2060 rxvt --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
+encodings. The \s-1BSS\s0 size comes from the 64k emergency buffer that my c++
+compiler allocates (but of course doesn't use unless you are out of
+memory). Also, using an xft font instead of a core font immediately adds a
+few megabytes of \s-1RSS\s0. Xft indeed is responsible for a lot of \s-1RSS\s0 even when
+not used.
+.PP
+Of course, due to every character using two or four bytes instead of one,
+a large scrollback buffer will ultimately make rxvt-unicode use more
+memory.
+.PP
+Compared to e.g. Eterm (5112k), aterm (3132k) and xterm (4680k), this
+still fares rather well. And compared to some monsters like gnome-terminal
+(21152k + extra 4204k in separate processes) or konsole (22200k + extra
+43180k in daemons that stay around after exit, plus half a minute of
+startup time, including the hundreds of warnings it spits out), it fares
+extremely well *g*.
+.Sh "Why \*(C+, isn't that unportable/bloated/uncool?"
+.IX Subsection "Why , isn't that unportable/bloated/uncool?"
+Is this a question? :) It comes up very often. The simple answer is: I had
+to write it, and \*(C+ allowed me to write and maintain it in a fraction
+of the time and effort (which is a scarce resource for me). Put even
+shorter: It simply wouldn't exist without \*(C+.
+.PP
+My personal stance on this is that \*(C+ is less portable than C, but in
+the case of rxvt-unicode this hardly matters, as its portability limits
+are defined by things like X11, pseudo terminals, locale support and unix
+domain sockets, which are all less portable than \*(C+ itself.
+.PP
+Regarding the bloat, see the above question: It's easy to write programs
+in C that use gobs of memory, an certainly possible to write programs in
+\&\*(C+ that don't. \*(C+ also often comes with large libraries, but this is
+not necessarily the case with \s-1GCC\s0. Here is what rxvt links against on my
+system with a minimal config:
+.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)
+.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)
+.Ve
+.PP
+No large bloated libraries (of course, none were linked in statically),
+except maybe libX11 :)
+.Sh "Does it support tabs, can I have a tabbed rxvt\-unicode?"
+.IX Subsection "Does it support tabs, can I have a tabbed rxvt-unicode?"
+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
+\&   @@RXVT_NAME@@ -pe tabbed
+.Ve
+.PP
+.Vb 1
+\&   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
+the upcoming \f(CW\*(C`Gtk2::URxvt\*(C'\fR perl module, which features a tabbed urxvt
+(murxvt) terminal as an example embedding application.
-.IP "How do I know which rxvt-unicode version I'm using?" 4
+.Sh "How do I know which rxvt-unicode version I'm using?"
-.IX Item "How do I know which rxvt-unicode version I'm using?"
+.IX Subsection "How do I know which rxvt-unicode version I'm using?"
 The version number is displayed with the usage (\-h). Also the escape
-sequence \f(CW\*(C`ESC [ 8 n\*(C'\fR sets the window title to the version number.
+sequence \f(CW\*(C`ESC [ 8 n\*(C'\fR sets the window title to the version number. When
+using the @@RXVT_NAME@@c client, the version displayed is that of the
+daemon.
-.IP "I am using Debian GNU/Linux and have a problem..." 4
+.Sh "I am using Debian GNU/Linux and have a problem..."
-.IX Item "I am using Debian GNU/Linux and have a problem..."
+.IX Subsection "I am using Debian GNU/Linux and have a problem..."
 The Debian GNU/Linux package of rxvt-unicode in sarge contains large
-patches that considerably change the behaviour of rxvt\-unicode. Before
+patches that considerably change the behaviour of rxvt-unicode (but
-reporting a bug to the original rxvt-unicode author please download and
+unfortunately this notice has been removed). Before reporting a bug to
-install the genuine version (<http://software.schmorp.de#rxvt\-unicode>)
+the original rxvt-unicode author please download and install the genuine
-and try to reproduce the problem. If you cannot, chances are that the
+version (<http://software.schmorp.de#rxvt\-unicode>) and try to reproduce
-problems are specific to Debian GNU/Linux, in which case it should be
+the problem. If you cannot, chances are that the problems are specific to
+Debian GNU/Linux, in which case it should be reported via the Debian Bug
-reported via the Debian Bug Tracking System (use \f(CW\*(C`reportbug\*(C'\fR to report
+Tracking System (use \f(CW\*(C`reportbug\*(C'\fR to report the bug).
-the bug).
+.PP
-.Sp
 For other problems that also affect the Debian package, you can and
 probably should use the Debian \s-1BTS\s0, too, because, after all, it's also a
 bug in the Debian version and it serves as a reminder for other users that
 might encounter the same issue.
+.Sh "I am maintaining rxvt-unicode for distribution/OS \s-1XXX\s0, any recommendation?"
+.IX Subsection "I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation?"
+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,
+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
+system-wide (except maybe with \f(CW\*(C`defaults\*(C'\fR). This will result in useful
+behaviour. If your distribution aims at low memory, add an empty
+\&\f(CW\*(C`perl\-ext\-common\*(C'\fR resource to the app-defaults file. This will keep the
+perl interpreter disabled until the user enables it.
+.PP
+If you can/want build more binaries, I recommend building a minimal
+one with \f(CW\*(C`\-\-disable\-everything\*(C'\fR (very useful) and a maximal one with
+\&\f(CW\*(C`\-\-enable\-everything\*(C'\fR (less useful, it will be very big due to a lot of
+encodings built-in that increase download times and are rarely used).
+.Sh "I need to make it setuid/setgid to support utmp/ptys on my \s-1OS\s0, is this safe?"
+.IX Subsection "I need to make it setuid/setgid to support utmp/ptys on my OS, is this safe?"
+It should be, starting with release 7.1. You are encouraged to properly
+install urxvt with privileges necessary for your \s-1OS\s0 now.
+.PP
+When rxvt-unicode detects that it runs setuid or setgid, it will fork
+into a helper process for privileged operations (pty handling on some
+systems, utmp/wtmp/lastlog handling on others) and drop privileges
+immediately. This is much safer than most other terminals that keep
+privileges while running (but is more relevant to urxvt, as it contains
+things as perl interpreters, which might be \*(L"helpful\*(R" to attackers).
+.PP
+This forking is done as the very first within \fImain()\fR, which is very early
+and reduces possible bugs to initialisation code run before \fImain()\fR, or
+things like the dynamic loader of your system, which should result in very
+little risk.
-.IP "When I log-in to another system it tells me about missing terminfo data?" 4
+.Sh "When I log-in to another system it tells me about missing terminfo data?"
-.IX Item "When I log-in to another system it tells me about missing terminfo data?"
+.IX Subsection "When I log-in to another system it tells me about missing terminfo data?"
 The terminal description used by rxvt-unicode is not as widely available
 as that for xterm, or even rxvt (for which the same problem often arises).
-.Sp
+.PP
 The correct solution for this problem is to install the terminfo, this can
 be done like this (with ncurses' infocmp):
-.Sp
+.PP
 .Vb 2
 \&   REMOTE=remotesystem.domain
 \&   infocmp rxvt-unicode | ssh $REMOTE "cat >/tmp/ti && tic /tmp/ti"
 .Ve
-.Sp
+.PP
 \&... or by installing rxvt-unicode normally on the remote system,
-.Sp
+.PP
 If you cannot or do not want to do this, then you can simply set
 \&\f(CW\*(C`TERM=rxvt\*(C'\fR or even \f(CW\*(C`TERM=xterm\*(C'\fR, and live with the small number of
 problems arising, which includes wrong keymapping, less and different
 colours and some refresh errors in fullscreen applications. It's a nice
 quick-and-dirty workaround for rare cases, though.
-.Sp
+.PP
 If you always want to do this (and are fine with the consequences) you
 can either recompile rxvt-unicode with the desired \s-1TERM\s0 value or use a
 resource to set it:
-.Sp
+.PP
 .Vb 1
 \&   URxvt.termName: rxvt
 .Ve
-.Sp
+.PP
 If you don't plan to use \fBrxvt\fR (quite common...) you could also replace
 the rxvt terminfo file with the rxvt-unicode one.
-.ie n .IP """tic"" outputs some error when compiling the terminfo entry." 4
+.ie n .Sh """tic"" outputs some error when compiling the terminfo entry."
-.el .IP "\f(CWtic\fR outputs some error when compiling the terminfo entry." 4
+.el .Sh "\f(CWtic\fP outputs some error when compiling the terminfo entry."
-.IX Item "tic outputs some error when compiling the terminfo entry."
+.IX Subsection "tic outputs some error when compiling the terminfo entry."
 Most likely it's the empty definition for \f(CW\*(C`enacs=\*(C'\fR. Just replace it by
 \&\f(CW\*(C`enacs=\eE[0@\*(C'\fR and try again.
-.ie n .IP """bash""'s readline does not work correctly under @@RXVT_NAME@@." 4
+.ie n .Sh """bash""'s readline does not work correctly under @@RXVT_NAME@@."
-.el .IP "\f(CWbash\fR's readline does not work correctly under @@RXVT_NAME@@." 4
+.el .Sh "\f(CWbash\fP's readline does not work correctly under @@RXVT_NAME@@."
-.IX Item "bash's readline does not work correctly under @@RXVT_NAME@@."
+.IX Subsection "bash's readline does not work correctly under @@RXVT_NAME@@."
-.PD 0
+See next entry.
-.IP "I need a termcap file entry." 4
+.Sh "I need a termcap file entry."
-.IX Item "I need a termcap file entry."
+.IX Subsection "I need a termcap file entry."
-.PD
 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.
-.Sp
+.PP
 You could use rxvt's termcap entry with resonable results in many cases.
 You can also create a termcap entry by using terminfo's infocmp program
 like this:
-.Sp
+.PP
 .Vb 1
 \&   infocmp -C rxvt-unicode
 .Ve
-.Sp
+.PP
 Or you could use this termcap entry, generated by the command above:
-.Sp
+.PP
 .Vb 20
 \&   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
 \&           :sc=\eE7:se=\eE[27m:sf=^J:so=\eE[7m:sr=\eEM:st=\eEH:ta=^I:\e
 \&           :te=\eE[r\eE[?1049l:ti=\eE[?1049h:ue=\eE[24m:up=\eE[A:\e
 \&           :us=\eE[4m:vb=\eE[?5h\eE[?5l:ve=\eE[?25h:vi=\eE[?25l:\e
 \&           :vs=\eE[?25h:
 .Ve
-.ie n .IP "Why does ""ls"" no longer have coloured output?" 4
+.ie n .Sh "Why does ""ls"" no longer have coloured output?"
-.el .IP "Why does \f(CWls\fR no longer have coloured output?" 4
+.el .Sh "Why does \f(CWls\fP no longer have coloured output?"
-.IX Item "Why does ls no longer have coloured output?"
+.IX Subsection "Why does ls no longer have coloured output?"
 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
 file. Needless to say, \f(CW\*(C`rxvt\-unicode\*(C'\fR is not in it's default file (among
 with most other terminals supporting colour). Either add:
-.Sp
+.PP
 .Vb 1
 \&   TERM rxvt-unicode
 .Ve
-.Sp
+.PP
 to \f(CW\*(C`/etc/DIR_COLORS\*(C'\fR or simply add:
-.Sp
+.PP
 .Vb 1
 \&   alias ls='ls --color=auto'
 .Ve
-.Sp
+.PP
 to your \f(CW\*(C`.profile\*(C'\fR or \f(CW\*(C`.bashrc\*(C'\fR.
-.IP "Why doesn't vim/emacs etc. use the 88 colour mode?" 4
+.Sh "Why doesn't vim/emacs etc. use the 88 colour mode?"
-.IX Item "Why doesn't vim/emacs etc. use the 88 colour mode?"
+.IX Subsection "Why doesn't vim/emacs etc. use the 88 colour mode?"
-.PD 0
+See next entry.
-.IP "Why doesn't vim/emacs etc. make use of italic?" 4
+.Sh "Why doesn't vim/emacs etc. make use of italic?"
-.IX Item "Why doesn't vim/emacs etc. make use of italic?"
+.IX Subsection "Why doesn't vim/emacs etc. make use of italic?"
+See next entry.
-.IP "Why are the secondary screen-related options not working properly?" 4
+.Sh "Why are the secondary screen-related options not working properly?"
-.IX Item "Why are the secondary screen-related options not working properly?"
+.IX Subsection "Why are the secondary screen-related options not working properly?"
-.PD
 Make sure you are using \f(CW\*(C`TERM=rxvt\-unicode\*(C'\fR. Some pre-packaged
 distributions (most notably Debian GNU/Linux) break rxvt-unicode
 by setting \f(CW\*(C`TERM\*(C'\fR to \f(CW\*(C`rxvt\*(C'\fR, which doesn't have these extra
 features. Unfortunately, some of these (most notably, again, Debian
 GNU/Linux) furthermore fail to even install the \f(CW\*(C`rxvt\-unicode\*(C'\fR terminfo
 file, so you will need to install it on your own (See the question \fBWhen
 I log-in to another system it tells me about missing terminfo data?\fR on
 how to do this).
-.IP "My numerical keypad acts weird and generates differing output?" 4
+.Sh "My numerical keypad acts weird and generates differing output?"
-.IX Item "My numerical keypad acts weird and generates differing output?"
+.IX Subsection "My numerical keypad acts weird and generates differing output?"
 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
 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.
-.IP "Rxvt-unicode does not seem to understand the selected encoding?" 4
+.Sh "Rxvt-unicode does not seem to understand the selected encoding?"
-.IX Item "Rxvt-unicode does not seem to understand the selected encoding?"
+.IX Subsection "Rxvt-unicode does not seem to understand the selected encoding?"
-.PD 0
+See next entry.
-.IP "Unicode does not seem to work?" 4
+.Sh "Unicode does not seem to work?"
-.IX Item "Unicode does not seem to work?"
+.IX Subsection "Unicode does not seem to work?"
-.PD
 If you encounter strange problems like typing an accented character but
 getting two unrelated other characters or similar, or if program output is
 subtly garbled, then you should check your locale settings.
-.Sp
+.PP
 Rxvt-unicode must be started with the same \f(CW\*(C`LC_CTYPE\*(C'\fR setting as the
 programs. Often rxvt-unicode is started in the \f(CW\*(C`C\*(C'\fR locale, while the
 login script running within the rxvt-unicode window changes the locale to
 something else, e.g. \f(CW\*(C`en_GB.UTF\-8\*(C'\fR. Needless to say, this is not going to work.
-.Sp
+.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.
-.Sp
+.PP
 .Vb 1
 \&  printf '\ee]701;%s\e007' "$LC_CTYPE"
 .Ve
-.Sp
+.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
 it will complain loudly if it cannot set the locale). If it displays something
 like:
-.Sp
+.PP
 .Vb 1
 \&  locale: Cannot set LC_CTYPE to default locale: ...
 .Ve
-.Sp
+.PP
 Then the locale you specified is not supported on your system.
-.Sp
+.PP
 If nothing works and you are sure that everything is set correctly then
 you will need to remember a little known fact: Some programs just don't
 support locales :(
-.IP "Why do some characters look so much different than others?" 4
+.Sh "Why do some characters look so much different than others?"
-.IX Item "Why do some characters look so much different than others?"
+.IX Subsection "Why do some characters look so much different than others?"
-.PD 0
+See next entry.
-.IP "How does rxvt-unicode choose fonts?" 4
+.Sh "How does rxvt-unicode choose fonts?"
-.IX Item "How does rxvt-unicode choose fonts?"
+.IX Subsection "How does rxvt-unicode choose fonts?"
-.PD
 Most fonts do not contain the full range of Unicode, which is
 fine. Chances are that the font you (or the admin/package maintainer of
 your system/os) have specified does not cover all the characters you want
 to display.
-.Sp
+.PP
 \&\fBrxvt-unicode\fR makes a best-effort try at finding a replacement
 font. Often the result is fine, but sometimes the chosen font looks
 bad/ugly/wrong. Some fonts have totally strange characters that don't
 resemble the correct glyph at all, and rxvt-unicode lacks the artificial
 intelligence to detect that a specific glyph is wrong: it has to believe
 the font that the characters it claims to contain indeed look correct.
-.Sp
+.PP
 In that case, select a font of your taste and add it to the font list,
 e.g.:
-.Sp
+.PP
 .Vb 1
 \&   @@RXVT_NAME@@ -fn basefont,font2,font3...
 .Ve
-.Sp
+.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.
-.Sp
+.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.
-.IP "Why do some chinese characters look so different than others?" 4
+.Sh "Why do some chinese characters look so different than others?"
-.IX Item "Why do some chinese characters look so different than others?"
+.IX Subsection "Why do some chinese characters look so different than others?"
 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.
-.Sp
+.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.
-.Sp
+.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).
-.Sp
+.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).
-.IP "Why does rxvt-unicode sometimes leave pixel droppings?" 4
+.Sh "Why does rxvt-unicode sometimes leave pixel droppings?"
-.IX Item "Why does rxvt-unicode sometimes leave pixel droppings?"
+.IX Subsection "Why does rxvt-unicode sometimes leave pixel droppings?"
 Most fonts were not designed for terminal use, which means that character
 size varies a lot. A font that is otherwise fine for terminal use might
 contain some characters that are simply too wide. Rxvt-unicode will avoid
 these characters. For characters that are just \*(L"a bit\*(R" too wide a special
 \&\*(L"careful\*(R" rendering mode is used that redraws adjacent characters.
-.Sp
+.PP
 All of this requires that fonts do not lie about character sizes,
 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).
-.Sp
+.PP
 It's not clear (to me at least), wether 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.
-.Sp
+.PP
 All of this is not a problem when using X11 core fonts, as their bounding
 box data is correct.
-.IP "On Solaris 9, many line-drawing characters are too wide." 4
+.Sh "On Solaris 9, many line-drawing characters are too wide."
-.IX Item "On Solaris 9, many line-drawing characters are too wide."
+.IX Subsection "On Solaris 9, many line-drawing characters are too wide."
 Seems to be a known bug, read
 <http://nixdoc.net/files/forum/about34198.html>. Some people use the
 following ugly workaround to get non-double-wide-characters working:
-.Sp
+.PP
 .Vb 1
 \&   #define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x)
 .Ve
-.IP "My Compose (Multi_key) key is no longer working." 4
+.Sh "My Compose (Multi_key) key is no longer working."
-.IX Item "My Compose (Multi_key) key is no longer working."
+.IX Subsection "My Compose (Multi_key) key is no longer working."
 The most common causes for this are that either your locale is not set
 correctly, or you specified a \fBpreeditStyle\fR that is not supported by
 your input method. For example, if you specified \fBOverTheSpot\fR and
 your input method (e.g. the default input method handling Compose keys)
 does not support this (for instance because it is not visual), then
 rxvt-unicode will continue without an input method.
-.Sp
+.PP
 In this case either do not specify a \fBpreeditStyle\fR or specify more than
 one pre-edit style, such as \fBOverTheSpot,Root,None\fR.
-.ie n .IP "I cannot type ""Ctrl\-Shift\-2"" to get an \s-1ASCII\s0 \s-1NUL\s0 character due to \s-1ISO\s0 14755" 4
+.ie n .Sh "I cannot type ""Ctrl\-Shift\-2"" to get an \s-1ASCII\s0 \s-1NUL\s0 character due to \s-1ISO\s0 14755"
-.el .IP "I cannot type \f(CWCtrl\-Shift\-2\fR to get an \s-1ASCII\s0 \s-1NUL\s0 character due to \s-1ISO\s0 14755" 4
+.el .Sh "I cannot type \f(CWCtrl\-Shift\-2\fP to get an \s-1ASCII\s0 \s-1NUL\s0 character due to \s-1ISO\s0 14755"
-.IX Item "I cannot type Ctrl-Shift-2 to get an ASCII NUL character due to ISO 14755"
+.IX Subsection "I cannot type Ctrl-Shift-2 to get an ASCII NUL character due to ISO 14755"
 Either try \f(CW\*(C`Ctrl\-2\*(C'\fR alone (it often is mapped to \s-1ASCII\s0 \s-1NUL\s0 even on
 international keyboards) or simply use \s-1ISO\s0 14755 support to your
 advantage, typing <Ctrl\-Shift\-0> to get a \s-1ASCII\s0 \s-1NUL\s0. This works for other
 codes, too, such as \f(CW\*(C`Ctrl\-Shift\-1\-d\*(C'\fR to type the default telnet escape
 character and so on.
-.IP "How can I keep rxvt-unicode from using reverse video so much?" 4
+.Sh "How can I keep rxvt-unicode from using reverse video so much?"
-.IX Item "How can I keep rxvt-unicode from using reverse video so much?"
+.IX Subsection "How can I keep rxvt-unicode from using reverse video so much?"
 First of all, make sure you are running with the right terminal settings
 (\f(CW\*(C`TERM=rxvt\-unicode\*(C'\fR), which will get rid of most of these effects. Then
 make sure you have specified colours for italic and bold, as otherwise
 rxvt-unicode might use reverse video to simulate the effect:
-.Sp
+.PP
 .Vb 2
 \&   URxvt.colorBD:  white
 \&   URxvt.colorIT:  green
 .Ve
-.IP "Some programs assume totally weird colours (red instead of blue), how can I fix that?" 4
+.Sh "Some programs assume totally weird colours (red instead of blue), how can I fix that?"
-.IX Item "Some programs assume totally weird colours (red instead of blue), how can I fix that?"
+.IX Subsection "Some programs assume totally weird colours (red instead of blue), how can I fix that?"
 For some unexplainable reason, some rare programs assume a very weird
 colour palette when confronted with a terminal with more than the standard
 8 colours (rxvt\-unicode supports 88). The right fix is, of course, to fix
 these programs not to assume non-ISO colours without very good reasons.
-.Sp
+.PP
 In the meantime, you can either edit your \f(CW\*(C`rxvt\-unicode\*(C'\fR terminfo
 definition to only claim 8 colour support or use \f(CW\*(C`TERM=rxvt\*(C'\fR, which will
 fix colours but keep you from using other rxvt-unicode features.
-.IP "I am on FreeBSD and rxvt-unicode does not seem to work at all." 4
+.Sh "I am on FreeBSD and rxvt-unicode does not seem to work at all."
-.IX Item "I am on FreeBSD and rxvt-unicode does not seem to work at all."
+.IX Subsection "I am on FreeBSD and rxvt-unicode does not seem to work at all."
 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
 \&\fBwchar_t\fR is represented as unicode.
-.Sp
+.PP
 As you might have guessed, FreeBSD does neither define this symobl nor
 does it support it. Instead, it uses it's own internal representation of
 \&\fBwchar_t\fR. This is, of course, completely fine with respect to standards.
-.Sp
+.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.
-.Sp
+.PP
 \&\f(CW\*(C`_\|_STDC_ISO_10646_\|_\*(C'\fR is the only sane way to support multi-language
 apps in an \s-1OS\s0, as using a locale-dependent (and non\-standardized)
 representation of \fBwchar_t\fR makes it impossible to convert between
 \&\fBwchar_t\fR (as used by X11 and your applications) and any other encoding
 without implementing OS-specific-wrappers for each and every locale. There
 simply are no APIs to convert \fBwchar_t\fR into anything except the current
 locale encoding.
-.Sp
+.PP
 Some applications (such as the formidable \fBmlterm\fR) work around this
 by carrying their own replacement functions for character set handling
 with them, and either implementing OS-dependent hacks or doing multiple
 conversions (which is slow and unreliable in case the \s-1OS\s0 implements
 encodings slightly different than the terminal emulator).
-.Sp
+.PP
 The rxvt-unicode author insists that the right way to fix this is in the
 system libraries once and for all, instead of forcing every app to carry
 complete replacements for them :)
-.IP "I use Solaris 9 and it doesn't compile/work/etc." 4
+.Sh "I use Solaris 9 and it doesn't compile/work/etc."
-.IX Item "I use Solaris 9 and it doesn't compile/work/etc."
+.IX Subsection "I use Solaris 9 and it doesn't compile/work/etc."
 Try the diff in \fIdoc/solaris9.patch\fR as a base. It fixes the worst
 problems with \f(CW\*(C`wcwidth\*(C'\fR and a compile problem.
-.IP "How can I use rxvt-unicode under cygwin?" 4
+.Sh "How can I use rxvt-unicode under cygwin?"
-.IX Item "How can I use rxvt-unicode under cygwin?"
+.IX Subsection "How can I use rxvt-unicode under cygwin?"
 rxvt-unicode should compile and run out of the box on cygwin, using
 the X11 libraries that come with cygwin. libW11 emulation is no
 longer supported (and makes no sense, either, as it only supported a
 single font). I recommend starting the X\-server in \f(CW\*(C`\-multiwindow\*(C'\fR or
 \&\f(CW\*(C`\-rootless\*(C'\fR mode instead, which will result in similar look&feel as the
 old libW11 emulation.
-.Sp
+.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.
-.IP "How does rxvt-unicode determine the encoding to use?" 4
+.Sh "How does rxvt-unicode determine the encoding to use?"
-.IX Item "How does rxvt-unicode determine the encoding to use?"
+.IX Subsection "How does rxvt-unicode determine the encoding to use?"
-.PD 0
+See next entry.
-.IP "Is there an option to switch encodings?" 4
+.Sh "Is there an option to switch encodings?"
-.IX Item "Is there an option to switch encodings?"
+.IX Subsection "Is there an option to switch encodings?"
-.PD
 Unlike some other terminals, rxvt-unicode has no encoding switch, and no
 specific \*(L"utf\-8\*(R" mode, such as xterm. In fact, it doesn't even know about
 \&\s-1UTF\-8\s0 or any other encodings with respect to terminal I/O.
-.Sp
+.PP
 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
 locales).
-.Sp
+.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.
-.Sp
+.PP
 Unfortunately, there is no system-independent way to select locales, nor
 is there a standard on how locale specifiers will look like.
-.Sp
+.PP
 On most systems, the content of the \f(CW\*(C`LC_CTYPE\*(C'\fR environment variable
 contains an arbitrary string which corresponds to an already-installed
 locale. Common names for locales are \f(CW\*(C`en_US.UTF\-8\*(C'\fR, \f(CW\*(C`de_DE.ISO\-8859\-15\*(C'\fR,
 \&\f(CW\*(C`ja_JP.EUC\-JP\*(C'\fR, i.e. \f(CW\*(C`language_country.encoding\*(C'\fR, but other forms
 (i.e. \f(CW\*(C`de\*(C'\fR or \f(CW\*(C`german\*(C'\fR) are also common.
-.Sp
+.PP
 Rxvt-unicode ignores all other locale categories, and except for
 the encoding, ignores country or language-specific settings,
 i.e. \f(CW\*(C`de_DE.UTF\-8\*(C'\fR and \f(CW\*(C`ja_JP.UTF\-8\*(C'\fR are the normally same to
 rxvt\-unicode.
-.Sp
+.PP
 If you want to use a specific encoding you have to make sure you start
 rxvt-unicode with the correct \f(CW\*(C`LC_CTYPE\*(C'\fR category.
-.IP "Can I switch locales at runtime?" 4
+.Sh "Can I switch locales at runtime?"
-.IX Item "Can I switch locales at runtime?"
+.IX Subsection "Can I switch locales at runtime?"
 Yes, using an escape sequence. Try something like this, which sets
 rxvt\-unicode's idea of \f(CW\*(C`LC_CTYPE\*(C'\fR.
-.Sp
+.PP
 .Vb 1
 \&  printf '\ee]701;%s\e007' ja_JP.SJIS
 .Ve
-.Sp
+.PP
 See also the previous answer.
-.Sp
+.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:
-.Sp
+.PP
 .Vb 3
 \&   printf '\ee]701;%s\e007' ja_JP.SJIS
 \&   xjdic -js
 \&   printf '\ee]701;%s\e007' de_DE.UTF-8
 .Ve
-.Sp
+.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.
-.IP "Can I switch the fonts at runtime?" 4
+.Sh "Can I switch the fonts at runtime?"
-.IX Item "Can I switch the fonts at runtime?"
+.IX Subsection "Can I switch the fonts at runtime?"
 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:
-.Sp
+.PP
 .Vb 1
 \&   printf '\ee]50;%s\e007' "9x15bold,xft:Kochi Gothic"
 .Ve
-.Sp
+.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.
-.Sp
+.PP
 You can think of this as a kind of manual \s-1ISO\-2022\s0 switching.
-.IP "Why do italic characters look as if clipped?" 4
+.Sh "Why do italic characters look as if clipped?"
-.IX Item "Why do italic characters look as if clipped?"
+.IX Subsection "Why do italic characters look as if clipped?"
 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
 enable freetype autohinting, i.e. like this:
-.Sp
+.PP
 .Vb 2
 \&   URxvt.italicFont:        xft:Bitstream Vera Sans Mono:italic:autohint=true
 \&   URxvt.boldItalicFont:    xft:Bitstream Vera Sans Mono:bold:italic:autohint=true
 .Ve
-.IP "My input method wants <some encoding> but I want \s-1UTF\-8\s0, what can I do?" 4
+.Sh "My input method wants <some encoding> but I want \s-1UTF\-8\s0, what can I do?"
-.IX Item "My input method wants <some encoding> but I want UTF-8, what can I do?"
+.IX Subsection "My input method wants <some encoding> but I want UTF-8, what can I do?"
 You can specify separate locales for the input method and the rest of the
 terminal, using the resource \f(CW\*(C`imlocale\*(C'\fR:
-.Sp
+.PP
 .Vb 1
-\&   URxvt*imlocale: ja_JP.EUC-JP
+\&   URxvt.imlocale: ja_JP.EUC-JP
 .Ve
-.Sp
+.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
 input characters outside \f(CW\*(C`EUC\-JP\*(C'\fR in a normal way then, as your input
 method limits you.
-.IP "Rxvt-unicode crashes when the X Input Method changes or exits." 4
+.Sh "Rxvt-unicode crashes when the X Input Method changes or exits."
-.IX Item "Rxvt-unicode crashes when the X Input Method changes or exits."
+.IX Subsection "Rxvt-unicode crashes when the X Input Method changes or exits."
 Unfortunately, this is unavoidable, as the \s-1XIM\s0 protocol is racy by
 design. Applications can avoid some crashes at the expense of memory
 leaks, and Input Methods can avoid some crashes by careful ordering at
 exit time. \fBkinput2\fR (and derived input methods) generally succeeds,
 while \fB\s-1SCIM\s0\fR (or similar input methods) fails. In the end, however,
 crashes cannot be completely avoided even if both sides cooperate.
-.Sp
+.PP
 So the only workaround is not to kill your Input Method Servers.
-.IP "Rxvt-unicode uses gobs of memory, how can I reduce that?" 4
+.Sh "Rxvt-unicode uses gobs of memory, how can I reduce that?"
-.IX Item "Rxvt-unicode uses gobs of memory, how can I reduce that?"
+.IX Subsection "Rxvt-unicode uses gobs of memory, how can I reduce that?"
 Rxvt-unicode tries to obey the rule of not charging you for something you
 don't use. One thing you should try is to configure out all settings that
 you don't need, for example, Xft support is a resource hog by design,
 when used. Compiling it out ensures that no Xft font will be loaded
 accidentally when rxvt-unicode tries to find a font for your characters.
-.Sp
+.PP
 Also, many people (me included) like large windows and even larger
 scrollback buffers: Without \f(CW\*(C`\-\-enable\-unicode3\*(C'\fR, rxvt-unicode will use
 6 bytes per screen cell. For a 160x?? window this amounts to almost a
 kilobyte per line. A scrollback buffer of 10000 lines will then (if full)
 use 10 Megabytes of memory. With \f(CW\*(C`\-\-enable\-unicode3\*(C'\fR it gets worse, as
 rxvt-unicode then uses 8 bytes per screen cell.
-.IP "Can I speed up Xft rendering somehow?" 4
+.Sh "Can I speed up Xft rendering somehow?"
-.IX Item "Can I speed up Xft rendering somehow?"
+.IX Subsection "Can I speed up Xft rendering somehow?"
 Yes, the most obvious way to speed it up is to avoid Xft entirely, as
 it is simply slow. If you still want Xft fonts you might try to disable
 antialiasing (by appending \f(CW\*(C`:antialias=false\*(C'\fR), which saves lots of
 memory and also speeds up rendering considerably.
-.IP "Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?" 4
+.Sh "Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?"
-.IX Item "Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?"
+.IX Subsection "Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?"
 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
 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.
-.Sp
+.PP
 If you want antialiasing, you have to specify the fonts manually.
-.IP "Mouse cut/paste suddenly no longer works." 4
+.Sh "Mouse cut/paste suddenly no longer works."
-.IX Item "Mouse cut/paste suddenly no longer works."
+.IX Subsection "Mouse cut/paste suddenly no longer works."
 Make sure that mouse reporting is actually turned off since killing
 some editors prematurely may leave the mouse in mouse report mode. I've
 heard that tcsh may use mouse reporting unless it otherwise specified. A
 quick check is to see if cut/paste works when the Alt or Shift keys are
-depressed. See @@RXVT_NAME@@(7)
+depressed.
-.IP "What's with this bold/blink stuff?" 4
+.Sh "What's with this bold/blink stuff?"
-.IX Item "What's with this bold/blink stuff?"
+.IX Subsection "What's with this bold/blink stuff?"
 If no bold colour is set via \f(CW\*(C`colorBD:\*(C'\fR, bold will invert text using the
 standard foreground colour.
-.Sp
+.PP
 For the standard background colour, blinking will actually make the
 text blink when compiled with \f(CW\*(C`\-\-enable\-blinking\*(C'\fR. with standard
 colours. Without \f(CW\*(C`\-\-enable\-blinking\*(C'\fR, the blink attribute will be
 ignored.
-.Sp
+.PP
 On \s-1ANSI\s0 colours, bold/blink attributes are used to set high-intensity
 foreground/background colors.
-.Sp
+.PP
 color0\-7 are the low-intensity colors.
-.Sp
+.PP
 color8\-15 are the corresponding high-intensity colors.
-.IP "I don't like the screen colors.  How do I change them?" 4
+.Sh "I don't like the screen colors.  How do I change them?"
-.IX Item "I don't like the screen colors.  How do I change them?"
+.IX Subsection "I don't like the screen colors.  How do I change them?"
 You can change the screen colors at run-time using \fI~/.Xdefaults\fR
 resources (or as long\-options).
-.Sp
+.PP
 Here are values that are supposed to resemble a \s-1VGA\s0 screen,
 including the murky brown that passes for low-intensity yellow:
-.Sp
+.PP
 .Vb 8
 \&   URxvt.color0:   #000000
 \&   URxvt.color1:   #A80000
 \&   URxvt.color2:   #00A800
 \&   URxvt.color3:   #A8A800
 \&   URxvt.color4:   #0000A8
 \&   URxvt.color5:   #A800A8
 \&   URxvt.color6:   #00A8A8
 \&   URxvt.color7:   #A8A8A8
 .Ve
-.Sp
+.PP
 .Vb 8
 \&   URxvt.color8:   #000054
 \&   URxvt.color9:   #FF0054
 \&   URxvt.color10:  #00FF54
 \&   URxvt.color11:  #FFFF54
 \&   URxvt.color12:  #0000FF
 \&   URxvt.color13:  #FF00FF
 \&   URxvt.color14:  #00FFFF
 \&   URxvt.color15:  #FFFFFF
 .Ve
-.Sp
+.PP
 And here is a more complete set of non-standard colors described (not by
 me) as \*(L"pretty girly\*(R".
-.Sp
+.PP
 .Vb 18
 \&   URxvt.cursorColor:  #dc74d1
 \&   URxvt.pointerColor: #dc74d1
 \&   URxvt.background:   #0e0e0e
 \&   URxvt.foreground:   #4ad5e1
 \&   URxvt.color6:       #73f7ff
 \&   URxvt.color14:      #73f7ff
 \&   URxvt.color7:       #e1dddd
 \&   URxvt.color15:      #e1dddd
 .Ve
-.IP "How can I start @@RXVT_NAME@@d in a race-free way?" 4
+.Sh "How can I start @@RXVT_NAME@@d in a race-free way?"
-.IX Item "How can I start @@RXVT_NAME@@d in a race-free way?"
+.IX Subsection "How can I start @@RXVT_NAME@@d in a race-free way?"
 Try \f(CW\*(C`@@RXVT_NAME@@d \-f \-o\*(C'\fR, which tells @@RXVT_NAME@@d to open the
 display, create the listening socket and then fork.
-.IP "What's with the strange Backspace/Delete key behaviour?" 4
+.Sh "What's with the strange Backspace/Delete key behaviour?"
-.IX Item "What's with the strange Backspace/Delete key behaviour?"
+.IX Subsection "What's with the strange Backspace/Delete key behaviour?"
 Assuming that the physical Backspace key corresponds to the
 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.
-.Sp
+.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
 choice :).
-.Sp
+.PP
 Rxvt-unicode tries to inherit the current stty settings and uses the value
 of `erase' to guess the value for backspace.  If rxvt-unicode wasn't
 started from a terminal (say, from a menu or by remote shell), then the
 system value of `erase', which corresponds to \s-1CERASE\s0 in <termios.h>, will
 be used (which may not be the same as your stty setting).
-.Sp
+.PP
 For starting a new rxvt\-unicode:
-.Sp
+.PP
 .Vb 3
 \&   # use Backspace = ^H
 \&   $ stty erase ^H
 \&   $ @@RXVT_NAME@@
 .Ve
-.Sp
+.PP
 .Vb 3
 \&   # use Backspace = ^?
 \&   $ stty erase ^?
 \&   $ @@RXVT_NAME@@
 .Ve
-.Sp
+.PP
-Toggle with \f(CW\*(C`ESC [ 36 h\*(C'\fR / \f(CW\*(C`ESC [ 36 l\*(C'\fR as documented in @@RXVT_NAME@@(7).
+Toggle with \f(CW\*(C`ESC [ 36 h\*(C'\fR / \f(CW\*(C`ESC [ 36 l\*(C'\fR.
-.Sp
+.PP
 For an existing rxvt\-unicode:
-.Sp
+.PP
 .Vb 3
 \&   # use Backspace = ^H
 \&   $ stty erase ^H
 \&   $ echo -n "^[[36h"
 .Ve
-.Sp
+.PP
 .Vb 3
 \&   # use Backspace = ^?
 \&   $ stty erase ^?
 \&   $ echo -n "^[[36l"
 .Ve
-.Sp
+.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.
-.Sp
+.PP
 The Delete key is a another casualty of the ill-defined Backspace problem.
 To avoid confusion between the Backspace and Delete keys, the Delete
 key has been assigned an escape sequence to match the vt100 for Execute
 (\f(CW\*(C`ESC [ 3 ~\*(C'\fR) and is in the supplied termcap/terminfo.
-.Sp
+.PP
 Some other Backspace problems:
-.Sp
+.PP
 some editors use termcap/terminfo,
 some editors (vim I'm told) expect Backspace = ^H,
 \&\s-1GNU\s0 Emacs (and Emacs-like editors) use ^H for help.
-.Sp
+.PP
 Perhaps someday this will all be resolved in a consistent manner.
-.IP "I don't like the key\-bindings.  How do I change them?" 4
+.Sh "I don't like the key\-bindings.  How do I change them?"
-.IX Item "I don't like the key-bindings.  How do I change them?"
+.IX Subsection "I don't like the key-bindings.  How do I change them?"
 There are some compile-time selections available via configure. Unless
 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.
-.Sp
+.PP
 Here's an example for a URxvt session started using \f(CW\*(C`@@RXVT_NAME@@ \-name URxvt\*(C'\fR
-.Sp
+.PP
 .Vb 20
 \&   URxvt.keysym.Home:          \e033[1~
 \&   URxvt.keysym.End:           \e033[4~
 \&   URxvt.keysym.C-apostrophe:  \e033<C-'>
 \&   URxvt.keysym.C-slash:       \e033<C-/>
 \&   URxvt.keysym.M-Right:       \e033<M-Right>
 \&   URxvt.keysym.M-C-0:         list \e033<M-C- 0123456789 >
 \&   URxvt.keysym.M-C-a:         list \e033<M-C- abcdefghijklmnopqrstuvwxyz >
 \&   URxvt.keysym.F12:           command:\e033]701;zh_CN.GBK\e007
 .Ve
-.Sp
+.PP
 See some more examples in the documentation for the \fBkeysym\fR resource.
-.IP "I'm using keyboard model \s-1XXX\s0 that has extra Prior/Next/Insert keys. How do I make use of them?  For example, the Sun Keyboard type 4 has the following mappings that rxvt-unicode doesn't recognize." 4
+.Sh "I'm using keyboard model \s-1XXX\s0 that has extra Prior/Next/Insert keys. How do I make use of them?  For example, the Sun Keyboard type 4 has the following mappings that rxvt-unicode doesn't recognize."
-.IX Item "I'm using keyboard model XXX that has extra Prior/Next/Insert keys. How do I make use of them?  For example, the Sun Keyboard type 4 has the following mappings that rxvt-unicode doesn't recognize."
+.IX Subsection "I'm using keyboard model XXX that has extra Prior/Next/Insert keys. How do I make use of them?  For example, the Sun Keyboard type 4 has the following mappings that rxvt-unicode doesn't recognize."
 .Vb 6
 \&   KP_Insert == Insert
 \&   F22 == Print
 \&   F27 == Home
 \&   F29 == Prior
 \&   F33 == End
 \&   F35 == Next
 .Ve
-.Sp
+.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.
-.IP "How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc." 4
+.Sh "How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc."
-.IX Item "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 wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc."
 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.
-.IP "How do I set the correct, full \s-1IP\s0 address for the \s-1DISPLAY\s0 variable?" 4
+.Sh "How do I set the correct, full \s-1IP\s0 address for the \s-1DISPLAY\s0 variable?"
-.IX Item "How do I set the correct, full IP address for the DISPLAY variable?"
+.IX Subsection "How do I set the correct, full IP address for the DISPLAY variable?"
 If you've compiled rxvt-unicode with \s-1DISPLAY_IS_IP\s0 and have enabled
 insecure mode then it is possible to use the following shell script
 snippets to correctly set the display. If your version of rxvt-unicode
 wasn't also compiled with \s-1ESCZ_ANSWER\s0 (as assumed in these snippets) then
 the \s-1COLORTERM\s0 variable can be used to distinguish rxvt-unicode from a
 regular xterm.
-.Sp
+.PP
 Courtesy of Chuck Blake <cblake@BBN.COM> with the following shell script
 snippets:
-.Sp
+.PP
 .Vb 12
 \&   # Bourne/Korn/POSIX family of shells:
 \&   [ ${TERM:-foo} = foo ] && TERM=xterm # assume an xterm if we don't know
 \&   if [ ${TERM:-foo} = xterm ]; then
 \&      stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not
 \&         echo -n '^[[7n'        # query the rxvt we are in for the DISPLAY string
 \&         read DISPLAY           # set it in our local shell
 \&      fi
 \&   fi
 .Ve
-.IP "How do I compile the manual pages for myself?" 4
+.Sh "How do I compile the manual pages for myself?"
-.IX Item "How do I compile the manual pages for myself?"
+.IX Subsection "How do I compile the manual pages for myself?"
 You need to have a recent version of perl installed as \fI/usr/bin/perl\fR,
 one that comes with \fIpod2man\fR, \fIpod2text\fR and \fIpod2html\fR. Then go to
 the doc subdirectory and enter \f(CW\*(C`make alldoc\*(C'\fR.
-.IP "My question isn't answered here, can I ask a human?" 4
+.Sh "My question isn't answered here, can I ask a human?"
-.IX Item "My question isn't answered here, can I ask a human?"
+.IX Subsection "My question isn't answered here, can I ask a human?"
 Before sending me mail, you could go to \s-1IRC:\s0 \f(CW\*(C`irc.freenode.net\*(C'\fR,
 channel \f(CW\*(C`#rxvt\-unicode\*(C'\fR has some rxvt-unicode enthusiasts that might be
 interested in learning about new and exciting problems (but not FAQs :).
 .SH "RXVT TECHNICAL REFERENCE"
 .IX Header "RXVT 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 menu and pixmap support and last by a description of all
+followed by pixmap support and last by a description of all features
-features selectable at \f(CW\*(C`configure\*(C'\fR time.
+selectable at \f(CW\*(C`configure\*(C'\fR time.
 .SH "Definitions"
 .IX Header "Definitions"
 .ie n .IP "\fB\fB""c""\fB\fR" 4
 .el .IP "\fB\f(CBc\fB\fR" 4
 .IX Item "c"
 l l .
 h	Send Mouse X & Y on button press.
 l	No mouse reporting.
 .TE
-.ie n .IP "\fB\fB""Ps = 10""\fB\fR (\fBrxvt\fR)" 4
-.el .IP "\fB\f(CBPs = 10\fB\fR (\fBrxvt\fR)" 4
-.IX Item "Ps = 10 (rxvt)"
-.TS
-l l .
-h	menuBar visible
-l	menuBar invisible
-.TE
 .ie n .IP "\fB\fB""Ps = 25""\fB\fR" 4
 .el .IP "\fB\f(CBPs = 25\fB\fR" 4
 .IX Item "Ps = 25"
 .TS
 l l .
 .IX Item "Ps = 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
+.el .IP "\fB\f(CBPs = 1021\fB\fR (\fBrxvt\fR)" 4
+.IX Item "Ps = 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
 .el .IP "\fB\f(CBPs = 1047\fB\fR" 4
 .IX Item "Ps = 1047"
 Ps = 10	Change colour of text foreground to Pt (NB: may change in future)
 Ps = 11	Change colour of text background to Pt (NB: may change in future)
 Ps = 12	Change colour of text cursor foreground to Pt
 Ps = 13	Change colour of mouse foreground to Pt
 Ps = 17	Change colour of highlight characters to Pt
-Ps = 18	Change colour of bold characters to Pt
+Ps = 18	Change colour of bold characters to Pt [deprecated, see 706]
-Ps = 19	Change colour of underlined characters to Pt
+Ps = 19	Change colour of underlined characters to Pt [deprecated, see 707]
-Ps = 20	Change default background to Pt
+Ps = 20	Change background pixmap parameters (see section XPM) (Compile XPM).
 Ps = 39	Change default foreground colour to Pt.
 Ps = 46	Change Log File to Pt unimplemented
 Ps = 49	Change default background colour to Pt.
 Ps = 50	Set fontset to Pt, with the following special values of Pt (rxvt) #+n change up n #-n change down n if n is missing of 0, a value of 1 is used empty change to font0 n change to font n
 Ps = 55	Log all scrollback buffer and all of screen to Pt
 Ps = 701	Change current locale to Pt, or, if Pt is ?, return the current locale (Compile frills).
-Ps = 703	Menubar command Pt (Compile menubar).
+Ps = 702	Request version if Pt is ?, returning rxvt-unicode, the resource name, the major and minor version numbers, e.g. ESC ] 702 ; rxvt-unicode ; urxvt ; 7 ; 4 ST.
 Ps = 704	Change colour of italic characters to Pt
 Ps = 705	Change background pixmap tint colour to Pt (Compile transparency).
+Ps = 706	Change colour of bold characters to Pt
+Ps = 707	Change colour of underlined characters to Pt
 Ps = 710	Set normal fontset to Pt. Same as Ps = 50.
 Ps = 711	Set bold fontset to Pt. Similar to Ps = 50 (Compile styles).
 Ps = 712	Set italic fontset to Pt. Similar to Ps = 50 (Compile styles).
 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 "menuBar"
+.IX Xref "XPM"
-.SH "menuBar"
-.IX Header "menuBar"
-\&\fBThe exact syntax used is \f(BIalmost\fB solidified.\fR
-In the menus, \fB\s-1DON\s0'T\fR try to use menuBar commands that add or remove a
-menuBar.
-.PP
-Note that in all of the commands, the \fB\f(BI/path/\fB\fR \fIcannot\fR be
-omitted: use \fB./\fR to specify a menu relative to the current menu.
-.Sh "Overview of menuBar operation"
-.IX Subsection "Overview of menuBar operation"
-For the menuBar XTerm escape sequence \f(CW\*(C`ESC ] 703 ; Pt ST\*(C'\fR, the syntax
-of \f(CW\*(C`Pt\*(C'\fR can be used for a variety of tasks:
-.PP
-At the top level is the current menuBar which is a member of a circular
-linked-list of other such menuBars.
-.PP
-The menuBar acts as a parent for the various drop-down menus, which in
-turn, may have labels, separator lines, menuItems and subMenus.
-.PP
-The menuItems are the useful bits: you can use them to mimic keyboard
-input or even to send text or escape sequences back to rxvt.
-.PP
-The menuBar syntax is intended to provide a simple yet robust method of
-constructing and manipulating menus and navigating through the
-menuBars.
-.PP
-The first step is to use the tag \fB[menu:\f(BIname\fB]\fR which creates
-the menuBar called \fIname\fR and allows access. You may now or menus,
-subMenus, and menuItems. Finally, use the tag \fB[done]\fR to set the
-menuBar access as \fBreadonly\fR to prevent accidental corruption of the
-menus. To re-access the current menuBar for alterations, use the tag
-\&\fB[menu]\fR, make the alterations and then use \fB[done]\fR
-.PP
-.IX Xref "menuBarCommands"
-.Sh "Commands"
-.IX Subsection "Commands"
-.IP "\fB[menu:+\f(BIname\fB]\fR" 4
-.IX Item "[menu:+name]"
-access the named menuBar for creation or alteration. If a new menuBar
-is created, it is called \fIname\fR (max of 15 chars) and the current
-menuBar is pushed onto the stack
-.IP "\fB[menu]\fR" 4
-.IX Item "[menu]"
-access the current menuBar for alteration
-.IP "\fB[title:+\f(BIstring\fB]\fR" 4
-.IX Item "[title:+string]"
-set the current menuBar's title to \fIstring\fR, which may contain the
-following format specifiers:
-.Sp
-.Vb 3
-\&   B<%n>  rxvt name (as per the B<-name> command-line option)
-\&   B<%v>  rxvt version
-\&   B<%%>  literal B<%> character
-.Ve
-.IP "\fB[done]\fR" 4
-.IX Item "[done]"
-set menuBar access as \fBreadonly\fR.
-End-of-file tag for \fB[read:+\f(BIfile\fB]\fR operations.
-.IP "\fB[read:+\f(BIfile\fB]\fR" 4
-.IX Item "[read:+file]"
-read menu commands directly from \fIfile\fR (extension \*(L".menu\*(R" will be
-appended if required.) Start reading at a line with \fB[menu]\fR or \fB[menu:+\f(BIname\fB\fR and continuing until \fB[done]\fR is encountered.
-.Sp
-Blank and comment lines (starting with \fB#\fR) are ignored. Actually,
-since any invalid menu commands are also ignored, almost anything could
-be construed as a comment line, but this may be tightened up in the
-future ... so don't count on it!.
-.IP "\fB[read:+\f(BIfile\fB;+\f(BIname\fB]\fR" 4
-.IX Item "[read:+file;+name]"
-The same as \fB[read:+\f(BIfile\fB]\fR, but start reading at a line with
-\&\fB[menu:+\f(BIname\fB]\fR and continuing until \fB[done:+\f(BIname\fB]\fR or
-\&\fB[done]\fR is encountered.
-.IP "\fB[dump]\fR" 4
-.IX Item "[dump]"
-dump all menuBars to the file \fB/tmp/rxvt\-PID\fR in a format suitable for
-later rereading.
-.IP "\fB[rm:name]\fR" 4
-.IX Item "[rm:name]"
-remove the named menuBar
-.IP "\fB[rm] [rm:]\fR" 4
-.IX Item "[rm] [rm:]"
-remove the current menuBar
-.IP "\fB[rm*] [rm:*]\fR" 4
-.IX Item "[rm*] [rm:*]"
-remove all menuBars
-.IP "\fB[swap]\fR" 4
-.IX Item "[swap]"
-swap the top two menuBars
-.IP "\fB[prev]\fR" 4
-.IX Item "[prev]"
-access the previous menuBar
-.IP "\fB[next]\fR" 4
-.IX Item "[next]"
-access the next menuBar
-.IP "\fB[show]\fR" 4
-.IX Item "[show]"
-Enable display of the menuBar
-.IP "\fB[hide]\fR" 4
-.IX Item "[hide]"
-Disable display of the menuBar
-.IP "\fB[pixmap:+\f(BIname\fB]\fR" 4
-.IX Item "[pixmap:+name]"
-.PD 0
-.IP "\fB[pixmap:+\f(BIname\fB;\f(BIscaling\fB]\fR" 4
-.IX Item "[pixmap:+name;scaling]"
-.PD
-(set the background pixmap globally
-.Sp
-\&\fBA Future implementation \f(BImay\fB make this local to the menubar\fR)
-.IP "\fB[:+\f(BIcommand\fB:]\fR" 4
-.IX Item "[:+command:]"
-ignore the menu readonly status and issue a \fIcommand\fR to or a menu or
-menuitem or change the ; a useful shortcut for setting the quick arrows
-from a menuBar.
-.PP
-.IX Xref "menuBarAdd"
-.Sh "Adding and accessing menus"
-.IX Subsection "Adding and accessing menus"
-The following commands may also be \fB+\fR prefixed.
-.IP "\fB/+\fR" 4
-.IX Item "/+"
-access menuBar top level
-.IP "\fB./+\fR" 4
-.IX Item "./+"
-access current menu level
-.IP "\fB../+\fR" 4
-.IX Item "../+"
-access parent menu (1 level up)
-.IP "\fB../../\fR" 4
-.IX Item "../../"
-access parent menu (multiple levels up)
-.IP "\fB\f(BI/path/\fBmenu\fR" 4
-.IX Item "/path/menu"
-add/access menu
-.IP "\fB\f(BI/path/\fBmenu/*\fR" 4
-.IX Item "/path/menu/*"
-add/access menu and clear it if it exists
-.IP "\fB\f(BI/path/\fB{\-}\fR" 4
-.IX Item "/path/{-}"
-add separator
-.IP "\fB\f(BI/path/\fB{item}\fR" 4
-.IX Item "/path/{item}"
-add \fBitem\fR as a label
-.IP "\fB\f(BI/path/\fB{item} action\fR" 4
-.IX Item "/path/{item} action"
-add/alter \fImenuitem\fR with an associated \fIaction\fR
-.IP "\fB\f(BI/path/\fB{item}{right\-text}\fR" 4
-.IX Item "/path/{item}{right-text}"
-add/alter \fImenuitem\fR with \fBright-text\fR as the right-justified text
-and as the associated \fIaction\fR
-.IP "\fB\f(BI/path/\fB{item}{rtext} action\fR" 4
-.IX Item "/path/{item}{rtext} action"
-add/alter \fImenuitem\fR with an associated \fIaction\fR and with \fBrtext\fR as
-the right-justified text.
-.IP "Special characters in \fIaction\fR must be backslash\-escaped:" 4
-.IX Item "Special characters in action must be backslash-escaped:"
-\&\fB\ea \eb \eE \ee \en \er \et \eoctal\fR
-.IP "or in control-character notation:" 4
-.IX Item "or in control-character notation:"
-\&\fB^@, ^A .. ^Z .. ^_, ^?\fR
-.PP
-To send a string starting with a \fB\s-1NUL\s0\fR (\fB^@\fR) character to the
-program, start \fIaction\fR with a pair of \fB\s-1NUL\s0\fR characters (\fB^@^@\fR),
-the first of which will be stripped off and the balance directed to the
-program. Otherwise if \fIaction\fR begins with \fB\s-1NUL\s0\fR followed by
-non\-+\fB\s-1NUL\s0\fR characters, the leading \fB\s-1NUL\s0\fR is stripped off and the
-balance is sent back to rxvt.
-.PP
-As a convenience for the many Emacs-type editors, \fIaction\fR may start
-with \fBM\-\fR (eg, \fBM\-$\fR is equivalent to \fB\eE$\fR) and a \fB\s-1CR\s0\fR will be
-appended if missed from \fBM\-x\fR commands.
-.PP
-As a convenience for issuing XTerm \fB\s-1ESC\s0 ]\fR sequences from a menubar (or
-quick arrow), a \fB\s-1BEL\s0\fR (\fB^G\fR) will be appended if needed.
-.IP "For example," 4
-.IX Item "For example,"
-\&\fBM\-xapropos\fR is equivalent to \fB\eExapropos\er\fR
-.IP "and" 4
-.IX Item "and"
-\&\fB\eE]703;mona;100\fR is equivalent to \fB\eE]703;mona;100\ea\fR
-.PP
-The option \fB{\f(BIright-rtext\fB}\fR will be right\-justified. In the
-absence of a specified action, this text will be used as the \fIaction\fR
-as well.
-.IP "For example," 4
-.IX Item "For example,"
-\&\fB/File/{Open}{^X^F}\fR is equivalent to \fB/File/{Open}{^X^F} ^X^F\fR
-.PP
-The left label \fIis\fR necessary, since it's used for matching, but
-implicitly hiding the left label (by using same name for both left and
-right labels), or explicitly hiding the left label (by preceeding it
-with a dot), makes it possible to have right-justified text only.
-.IP "For example," 4
-.IX Item "For example,"
-\&\fB/File/{Open}{Open} Open-File-Action\fR
-.IP "or hiding it" 4
-.IX Item "or hiding it"
-\&\fB/File/{.anylabel}{Open} Open-File-Action\fR
-.PP
-.IX Xref "menuBarRemove"
-.Sh "Removing menus"
-.IX Subsection "Removing menus"
-.IP "\fB\-/*+\fR" 4
-.IX Item "-/*+"
-remove all menus from the menuBar, the same as \fB[clear]\fR
-.IP "\fB\-+\f(BI/path\fBmenu+\fR" 4
-.IX Item "-+/pathmenu+"
-remove menu
-.IP "\fB\-+\f(BI/path\fB{item}+\fR" 4
-.IX Item "-+/path{item}+"
-remove item
-.IP "\fB\-+\f(BI/path\fB{\-}\fR" 4
-.IX Item "-+/path{-}"
-remove separator)
-.IP "\fB\-/path/menu/*\fR" 4
-.IX Item "-/path/menu/*"
-remove all items, separators and submenus from menu
-.PP
-.IX Xref "menuBarArrows"
-.Sh "Quick Arrows"
-.IX Subsection "Quick Arrows"
-The menus also provide a hook for \fIquick arrows\fR to provide easier
-user access. If nothing has been explicitly set, the default is to
-emulate the curror keys. The syntax permits each arrow to be altered
-individually or all four at once without re-entering their common
-beginning/end text. For example, to explicitly associate cursor actions
-with the arrows, any of the following forms could be used:
-.IP "\fB<r>+\f(BIRight\fB\fR" 4
-.IX Item "<r>+Right"
-.PD 0
-.IP "\fB<l>+\f(BILeft\fB\fR" 4
-.IX Item "<l>+Left"
-.IP "\fB<u>+\f(BIUp\fB\fR" 4
-.IX Item "<u>+Up"
-.IP "\fB<d>+\f(BIDown\fB\fR" 4
-.IX Item "<d>+Down"
-.PD
-Define actions for the respective arrow buttons
-.IP "\fB<b>+\f(BIBegin\fB\fR" 4
-.IX Item "<b>+Begin"
-.PD 0
-.IP "\fB<e>+\f(BIEnd\fB\fR" 4
-.IX Item "<e>+End"
-.PD
-Define common beginning/end parts for \fIquick arrows\fR which used in
-conjunction with the above <r> <l> <u> <d> constructs
-.IP "For example, define arrows individually," 4
-.IX Item "For example, define arrows individually,"
-.Vb 1
-\& <u>\eE[A
-.Ve
-.Sp
-.Vb 1
-\& <d>\eE[B
-.Ve
-.Sp
-.Vb 1
-\& <r>\eE[C
-.Ve
-.Sp
-.Vb 1
-\& <l>\eE[D
-.Ve
-.IP "or all at once" 4
-.IX Item "or all at once"
-.Vb 1
-\& <u>\eE[AZ<><d>\eE[BZ<><r>\eE[CZ<><l>\eE[D
-.Ve
-.IP "or more compactly (factoring out common parts)" 4
-.IX Item "or more compactly (factoring out common parts)"
-.Vb 1
-\& <b>\eE[<u>AZ<><d>BZ<><r>CZ<><l>D
-.Ve
-.PP
-.IX Xref "menuBarSummary"
-.Sh "Command Summary"
-.IX Subsection "Command Summary"
-A short summary of the most \fIcommon\fR commands:
-.IP "[menu:name]" 4
-.IX Item "[menu:name]"
-use an existing named menuBar or start a new one
-.IP "[menu]" 4
-.IX Item "[menu]"
-use the current menuBar
-.IP "[title:string]" 4
-.IX Item "[title:string]"
-set menuBar title
-.IP "[done]" 4
-.IX Item "[done]"
-set menu access to readonly and, if reading from a file, signal \s-1EOF\s0
-.IP "[done:name]" 4
-.IX Item "[done:name]"
-if reading from a file using [read:file;name] signal \s-1EOF\s0
-.IP "[rm:name]" 4
-.IX Item "[rm:name]"
-remove named menuBar(s)
-.IP "[rm] [rm:]" 4
-.IX Item "[rm] [rm:]"
-remove current menuBar
-.IP "[rm*] [rm:*]" 4
-.IX Item "[rm*] [rm:*]"
-remove all menuBar(s)
-.IP "[swap]" 4
-.IX Item "[swap]"
-swap top two menuBars
-.IP "[prev]" 4
-.IX Item "[prev]"
-access the previous menuBar
-.IP "[next]" 4
-.IX Item "[next]"
-access the next menuBar
-.IP "[show]" 4
-.IX Item "[show]"
-map menuBar
-.IP "[hide]" 4
-.IX Item "[hide]"
-unmap menuBar
-.IP "[pixmap;file]" 4
-.IX Item "[pixmap;file]"
-.PD 0
-.IP "[pixmap;file;scaling]" 4
-.IX Item "[pixmap;file;scaling]"
-.PD
-set a background pixmap
-.IP "[read:file]" 4
-.IX Item "[read:file]"
-.PD 0
-.IP "[read:file;name]" 4
-.IX Item "[read:file;name]"
-.PD
-read in a menu from a file
-.IP "[dump]" 4
-.IX Item "[dump]"
-dump out all menuBars to /tmp/rxvt\-PID
-.IP "/" 4
-access menuBar top level
-.IP "./" 4
-.PD 0
-.IP "../" 4
-.IP "../../" 4
-.PD
-access current or parent menu level
-.IP "/path/menu" 4
-.IX Item "/path/menu"
-add/access menu
-.IP "/path/{\-}" 4
-.IX Item "/path/{-}"
-add separator
-.IP "/path/{item}{rtext} action" 4
-.IX Item "/path/{item}{rtext} action"
-add/alter menu item
-.IP "\-/*" 4
-remove all menus from the menuBar
-.IP "\-/path/menu" 4
-.IX Item "-/path/menu"
-remove menu items, separators and submenus from menu
-.IP "\-/path/menu" 4
-.IX Item "-/path/menu"
-remove menu
-.IP "\-/path/{item}" 4
-.IX Item "-/path/{item}"
-remove item
-.IP "\-/path/{\-}" 4
-.IX Item "-/path/{-}"
-remove separator
-.IP "<b>Begin<r>Right<l>Left<u>Up<d>Down<e>End" 4
-.IX Item "<b>Begin<r>Right<l>Left<u>Up<d>Down<e>End"
-menu quick arrows
 .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
 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.
 .IP "\-\-enable\-unicode3 (default: off)" 4
 .IX Item "--enable-unicode3 (default: off)"
+Recommended to stay off unless you really need non-BMP characters.
+.Sp
 Enable direct support for displaying unicode codepoints above
 65535 (the basic multilingual page). This increases storage
 requirements per character from 2 to 4 bytes. X11 fonts do not yet
 support these extra characters, but Xft does.
 .Sp
 composite characters. This is required for proper viewing of text
 where accents are encoded as seperate unicode characters. This is
 done by using precomposited characters when available or creating
 new pseudo-characters when no precomposed form exists.
 .Sp
-Without \-\-enable\-unicode3, the number of additional precomposed characters
+Without \-\-enable\-unicode3, the number of additional precomposed
-is rather limited (2048, if this is full, rxvt-unicode will use the
+characters is somewhat limited (the 6400 private use characters will be
-private use area, extending the number of combinations to 8448). With
-\&\-\-enable\-unicode3, no practical limit exists.
+(ab\-)used). With \-\-enable\-unicode3, no practical limit exists.
 .Sp
 This option will also enable storage (but not display) of characters
 beyond plane 0 (>65535) when \-\-enable\-unicode3 was not specified.
 .Sp
 The combining table also contains entries for arabic presentation forms,
 but these are not currently used. Bug me if you want these to be used (and
 tell me how these are to be used...).
 .IP "\-\-enable\-fallback(=CLASS) (default: Rxvt)" 4
 .IX Item "--enable-fallback(=CLASS) (default: Rxvt)"
-When reading resource settings, also read settings for class \s-1CLASS\s0. To disable resource fallback use \-\-disable\-fallback.
+When reading resource settings, also read settings for class \s-1CLASS\s0. To
+disable resource fallback use \-\-disable\-fallback.
 .IP "\-\-with\-res\-name=NAME (default: urxvt)" 4
 .IX Item "--with-res-name=NAME (default: urxvt)"
 Use the given name as default application name when
 reading resources. Specify \-\-with\-res\-name=rxvt to replace rxvt.
 .IP "\-\-with\-res\-class=CLASS /default: URxvt)" 4
 .IP "\-\-enable\-lastlog (default: on)" 4
 .IX Item "--enable-lastlog (default: on)"
 Write user and tty to lastlog file (used by programs like
 \&\fIlastlogin\fR) at start of rxvt execution.  This option requires
 \&\-\-enable\-utmp to also be specified.
-.IP "\-\-enable\-xpm\-background (default: off)" 4
+.IP "\-\-enable\-xpm\-background (default: on)" 4
-.IX Item "--enable-xpm-background (default: off)"
+.IX Item "--enable-xpm-background (default: on)"
 Add support for \s-1XPM\s0 background pixmaps.
-.IP "\-\-enable\-transparency (default: off)" 4
+.IP "\-\-enable\-transparency (default: on)" 4
-.IX Item "--enable-transparency (default: off)"
+.IX Item "--enable-transparency (default: on)"
 Add support for inheriting parent backgrounds thus giving a fake
 transparency to the term.
 .IP "\-\-enable\-fading (default: on)" 4
 .IX Item "--enable-fading (default: on)"
 Add support for fading the text when focus is lost (requires \f(CW\*(C`\-\-enable\-transparency\*(C'\fR).
 .IP "\-\-enable\-tinting (default: on)" 4
 .IX Item "--enable-tinting (default: on)"
 Add support for tinting of transparent backgrounds (requires \f(CW\*(C`\-\-enable\-transparency\*(C'\fR).
-.IP "\-\-enable\-menubar (default: off)" 4
-.IX Item "--enable-menubar (default: off)"
-Add support for our menu bar system (this interacts badly with
-dynamic locale switching currently).
 .IP "\-\-enable\-rxvt\-scroll (default: on)" 4
 .IX Item "--enable-rxvt-scroll (default: on)"
 Add support for the original rxvt scrollbar.
 .IP "\-\-enable\-next\-scroll (default: on)" 4
 .IX Item "--enable-next-scroll (default: on)"
 .IP "\-\-enable\-plain\-scroll (default: on)" 4
 .IX Item "--enable-plain-scroll (default: on)"
 Add support for a very unobtrusive, plain-looking scrollbar that
 is the favourite of the rxvt-unicode author, having used it for
 many years.
-.IP "\-\-enable\-half\-shadow (default: off)" 4
-.IX Item "--enable-half-shadow (default: off)"
-Make shadows on the scrollbar only half the normal width & height.
-only applicable to rxvt scrollbars.
 .IP "\-\-enable\-ttygid (default: off)" 4
 .IX Item "--enable-ttygid (default: off)"
 Change tty device setting to group \*(L"tty\*(R" \- only use this if
 your system uses this type of security.
 .IP "\-\-disable\-backspace\-key" 4
 Removes any handling of the delete key by us \- let the X server
 do it.
 .IP "\-\-disable\-resources" 4
 .IX Item "--disable-resources"
 Removes any support for resource checking.
-.IP "\-\-enable\-xgetdefault" 4
-.IX Item "--enable-xgetdefault"
-Make resources checking via \fIXGetDefault()\fR instead of our small
-version which only checks ~/.Xdefaults, or if that doesn't exist then
-~/.Xresources.
-.Sp
-Please note that nowadays, things like \s-1XIM\s0 will automatically pull in and
-use the full X resource manager, so the overhead of using it might be very
-small, if nonexistant.
-.IP "\-\-enable\-strings (default: off)" 4
-.IX Item "--enable-strings (default: off)"
-Add support for our possibly faster \fImemset()\fR function and other
-various routines, overriding your system's versions which may
-have been hand-crafted in assembly or may require extra libraries
-to link in. (this breaks ANSI-C rules and has problems on many
-GNU/Linux systems).
 .IP "\-\-disable\-swapscreen" 4
 .IX Item "--disable-swapscreen"
 Remove support for secondary/swap screen.
 .IP "\-\-enable\-frills (default: on)" 4
 .IX Item "--enable-frills (default: on)"
 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 13
+.Vb 15
 \&  MWM-hints
 \&  EWMH-hints (pid, utf8 names) and protocols (ping)
-\&  seperate underline colour
+\&  seperate underline colour (-underlineColor)
-\&  settable border widths and borderless switch
+\&  settable border widths and borderless switch (-w, -b, -bl)
+\&  visual depth selection (-depth)
-\&  settable extra linespacing
+\&  settable extra linespacing /-lsp)
 \&  iso-14755-2 and -3, and visual feedback
+\&  tripleclickwords (-tcw)
+\&  settable insecure mode (-insecure)
+\&  keysym remapping support
+\&  cursor blinking and underline cursor (-cb, -uc)
+\&  XEmbed support (-embed)
+\&  user-pty (-pty-fd)
+\&  hold on exit (-hold)
+\&  skip builtin block graphics (-sbg)
+.Ve
+.Sp
+It also enabled some non-essential features otherwise disabled, such as:
+.Sp
+.Vb 11
+\&  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 sequence
+\&  backindex and forwardindex escape sequences
+\&  view change/zero scorllback esacpe sequences
+\&  locale switching escape sequence
 \&  window op and some xterm/OSC escape sequences
-\&  tripleclickwords
+\&  rectangular selections
-\&  settable insecure mode
+\&  trailing space removal for selections
-\&  keysym remapping support
+\&  verbose X error handling
-\&  cursor blinking and underline cursor
-\&  -embed, -pty-fd and -hold options
 .Ve
 .IP "\-\-enable\-iso14755 (default: on)" 4
 .IX Item "--enable-iso14755 (default: on)"
 Enable extended \s-1ISO\s0 14755 support (see @@RXVT_NAME@@(1), or
 \&\fIdoc/rxvt.1.txt\fR). Basic support (section 5.1) is enabled by
 keys. This should keep the window corner which is closest to a corner of
 the screen in a fixed position.
 .IP "\-\-enable\-pointer\-blank (default: on)" 4
 .IX Item "--enable-pointer-blank (default: on)"
 Add support to have the pointer disappear when typing or inactive.
+.IP "\-\-enable\-perl (default: on)" 4
+.IX Item "--enable-perl (default: on)"
+Enable an embedded perl interpreter. See the \fB@@RXVT_NAME@@\f(BIperl\fB\|(3)\fR
+manpage (\fIdoc/rxvtperl.txt\fR) for more info on this feature, or the files
+in \fIsrc/perl\-ext/\fR for the extensions that are installed by default. The
+perl interpreter that is used can be specified via the \f(CW\*(C`PERL\*(C'\fR environment
+variable when running configure.
 .IP "\-\-with\-name=NAME (default: urxvt)" 4
 .IX Item "--with-name=NAME (default: urxvt)"
 Set the basename for the installed binaries, resulting
 in \f(CW\*(C`urxvt\*(C'\fR, \f(CW\*(C`urxvtd\*(C'\fR etc.). Specify \f(CW\*(C`\-\-with\-name=rxvt\*(C'\fR to replace with
 \&\f(CW\*(C`rxvt\*(C'\fR.

Diff Legend

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

Comparing rxvt-unicode/doc/rxvt.7.man.in (file contents): Revision 1.28 by root, Thu Dec 22 16:44:10 2005 UTC vs. Revision 1.60 by root, Tue Jan 31 01:00:49 2006 UTC

Diff Legend

Comparing rxvt-unicode/doc/rxvt.7.man.in (file contents):
Revision 1.28 by root, Thu Dec 22 16:44:10 2005 UTC vs.
Revision 1.60 by root, Tue Jan 31 01:00:49 2006 UTC