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

Comparing rxvt-unicode/doc/rxvt.7.html (file contents):
Revision 1.20 by root, Thu Jun 30 14:00:49 2005 UTC vs.
Revision 1.54 by root, Tue Jan 31 00:25:16 2006 UTC

 	<li><a href="#values">Values</a></li>
 	<li><a href="#escape_sequences">Escape Sequences</a></li>
 	<li><a href="#csi__command_sequence_introducer__sequences">CSI (Command Sequence Introducer) Sequences</a></li>
 	<li><a href="#dec_private_modes">DEC Private Modes</a></li>
 	<li><a href="#xterm_operating_system_commands">XTerm Operating System Commands</a></li>
-	<li><a href="#menubar">menuBar</a></li>
-	<ul>
-		<li><a href="#overview_of_menubar_operation">Overview of menuBar operation</a></li>
-		<li><a href="#commands">Commands</a></li>
-		<li><a href="#adding_and_accessing_menus">Adding and accessing menus</a></li>
-		<li><a href="#removing_menus">Removing menus</a></li>
-		<li><a href="#quick_arrows">Quick Arrows</a></li>
-		<li><a href="#command_summary">Command Summary</a></li>
-	</ul>
 	<li><a href="#xpm">XPM</a></li>
 	<li><a href="#mouse_reporting">Mouse Reporting</a></li>
 	<li><a href="#key_codes">Key Codes</a></li>
 	<li><a href="#configure_options">CONFIGURE OPTIONS</a></li>
 	<li><a href="#authors">AUTHORS</a></li>
 </p>
 <hr />
 <h1><a name="description">DESCRIPTION</a></h1>
 <p>This document contains the FAQ, the RXVT TECHNICAL REFERENCE documenting
 all escape sequences, and other background information.</p>
-<p>The newest version of this document is
+<p>The newest version of this document is also available on the World Wide Web at
-also available on the World Wide Web at
 <a href="http://cvs.schmorp.de/browse/*checkout*/rxvt-unicode/doc/rxvt.7.html">http://cvs.schmorp.de/browse/*checkout*/rxvt-unicode/doc/rxvt.7.html</a>.</p>
 <p>
 </p>
 <hr />
 <h1><a name="frequently_asked_questions">FREQUENTLY ASKED QUESTIONS</a></h1>
 <dl>
+<dt><strong><a name="item_the_new_selection_selects_pieces_that_are_too_big_">The new selection selects pieces that are too big, how can I select
+single words?</a></strong><br />
+</dt>
+<dd>
+Yes. For example, if you want to select alphanumeric words, you can use
+the following resource:
+</dd>
+<dd>
+<pre>
+   URxvt.selection.pattern-0: ([[:word:]]+)</pre>
+</dd>
+<dd>
+<p>If you click more than twice, the selection will be extended
+more and more.</p>
+</dd>
+<dd>
+<p>To get a selection that is very similar to the old code, try this pattern:</p>
+</dd>
+<dd>
+<pre>
+   URxvt.selection.pattern-0: ([^&quot;&amp;'()*,;&lt;=&gt;?@[\\\\]^`{|})]+)</pre>
+</dd>
+<dd>
+<p>Please also note that the <em>LeftClick Shift-LeftClik</em> combination also
+selects words like the old code.</p>
+</dd>
+<p></p>
+<dt><strong><a name="item_i_don_27t_like_the_new_selection_2fpopups_2fhotkey">I don't like the new selection/popups/hotkeys/perl, how do I
+change/disable it?</a></strong><br />
+</dt>
+<dd>
+You can disable the perl extension completely by setting the
+<strong>perl-ext-common</strong> resource to the empty string, which also keeps
+rxvt-unicode from initialising perl, saving memory.
+</dd>
+<dd>
+<p>If you only want to disable specific features, you first have to
+identify which perl extension is responsible. For this, read the section
+<strong>PREPACKAGED EXTENSIONS</strong> in the <code>rxvtperl(3)</code> manpage. For
+example, to disable the <strong>selection-popup</strong> and <strong>option-popup</strong>, specify
+this <strong>perl-ext-common</strong> resource:</p>
+</dd>
+<dd>
+<pre>
+   URxvt.perl-ext-common: default,-selection-popup,-option-popup</pre>
+</dd>
+<dd>
+<p>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 <strong>M-s</strong>. You can move it to any
+other combination either by setting the <strong>searchable-scrollback</strong> resource:</p>
+</dd>
+<dd>
+<pre>
+   URxvt.searchable-scrollback: CM-s</pre>
+</dd>
+<p></p>
+<dt><strong><a name="item_why_doesn_27t_rxvt_2dunicode_read_my_resources_3f">Why doesn't rxvt-unicode read my resources?</a></strong><br />
+</dt>
+<dd>
+Well, why, indeed? It does, in a way very similar to other X
+applications. Most importantly, this means that if you or your OS 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
+<em>$HOME/.Xdefaults</em> when no resources are attached to the display.
+</dd>
+<dd>
+<p>If you have or use an <em>$HOME/.Xresources</em> file, chances are that
+resources are loaded into your X-server. In this case, you have to
+re-login after every change (or run <em>xrdb -merge $HOME/.Xresources</em>).</p>
+</dd>
+<dd>
+<p>Also consider the form resources have to use:</p>
+</dd>
+<dd>
+<pre>
+  URxvt.resource: value</pre>
+</dd>
+<dd>
+<p>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.</p>
+</dd>
+<p></p>
+<dt><strong><a name="item_i_can_27t_get_transparency_working_2c_what_am_i_do">I can't get transparency working, what am I doing wrong?</a></strong><br />
+</dt>
+<dd>
+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.
+</dd>
+<dd>
+<p>Here are four ways to get transparency. <strong>Do</strong> read the manpage and option
+descriptions for the programs mentioned and rxvt-unicode. Really, do it!</p>
+</dd>
+<dd>
+<p>1. Use inheritPixmap:</p>
+</dd>
+<dd>
+<pre>
+   Esetroot wallpaper.jpg
+   rxvt -ip -tint red -sh 40</pre>
+</dd>
+<dd>
+<p>That works. If you think it doesn't, you lack transparency and tinting
+support, or you are unable to read.</p>
+</dd>
+<dd>
+<p>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:</p>
+</dd>
+<dd>
+<pre>
+   convert wallpaper.jpg -blur 20x20 -modulate 30 background.xpm
+   rxvt -pixmap background.xpm -pe automove-background</pre>
+</dd>
+<dd>
+<p>That works. If you think it doesn't, you lack XPM and Perl support, or you
+are unable to read.</p>
+</dd>
+<dd>
+<p>3. Use an ARGB visual:</p>
+</dd>
+<dd>
+<pre>
+   rxvt -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc</pre>
+</dd>
+<dd>
+<p>This requires XFT support, and the support of your X-server. If that
+doesn't work for you, blame Xorg and Keith Packard. ARGB 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 WM has the required kludges in place.</p>
+</dd>
+<dd>
+<p>4. Use xcompmgr and let it do the job:</p>
+</dd>
+<dd>
+<pre>
+  xprop -frame -f _NET_WM_WINDOW_OPACITY 32c \
+        -set _NET_WM_WINDOW_OPACITY 0xc0000000</pre>
+</dd>
+<dd>
+<p>Then click on a window you want to make transparent. Replace <code>0xc0000000</code>
+by other values to change the degree of opacity. If it doesn't work and
+your server crashes, you got to keep the pieces.</p>
+</dd>
+<p></p>
+<dt><strong><a name="item_isn_27t_rxvt_supposed_to_be_small_3f_don_27t_all_t">Isn't rxvt supposed to be small? Don't all those features bloat?</a></strong><br />
+</dt>
+<dd>
+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 (RSS) after startup. Even
+with <code>--disable-everything</code>, this comparison is a bit unfair, as many
+features unique to urxvt (locale, encoding conversion, iso14755 etc.) are
+already in use in this mode.
+</dd>
+<dd>
+<pre>
+    text    data     bss     drs     rss filename
+   98398    1664      24   15695    1824 rxvt --disable-everything
+  188985    9048   66616   18222    1788 urxvt --disable-everything</pre>
+</dd>
+<dd>
+<p>When you <a href="#item__2d_2denable_2deverything"><code>--enable-everything</code></a> (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.</p>
+</dd>
+<dd>
+<pre>
+    text    data     bss     drs     rss filename
+  163431    2152      24   20123    2060 rxvt --enable-everything
+ 1035683   49680   66648   29096    3680 urxvt --enable-everything</pre>
+</dd>
+<dd>
+<p>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 BSS 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 RSS. Xft indeed is responsible for a lot of RSS even when
+not used.</p>
+</dd>
+<dd>
+<p>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.</p>
+</dd>
+<dd>
+<p>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*.</p>
+</dd>
+<p></p>
+<dt><strong><a name="item_why_c_2b_2b_2c_isn_27t_that_unportable_2fbloated_2">Why C++, isn't that unportable/bloated/uncool?</a></strong><br />
+</dt>
+<dd>
+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++.
+</dd>
+<dd>
+<p>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.</p>
+</dd>
+<dd>
+<p>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 GCC. Here is what rxvt links against on my
+system with a minimal config:</p>
+</dd>
+<dd>
+<pre>
+   libX11.so.6 =&gt; /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000)
+   libc.so.6 =&gt; /lib/libc.so.6 (0x00002aaaaadde000)
+   libdl.so.2 =&gt; /lib/libdl.so.2 (0x00002aaaab01d000)
+   /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)</pre>
+</dd>
+<dd>
+<p>And here is rxvt-unicode:</p>
+</dd>
+<dd>
+<pre>
+   libX11.so.6 =&gt; /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000)
+   libgcc_s.so.1 =&gt; /lib/libgcc_s.so.1 (0x00002aaaaada2000)
+   libc.so.6 =&gt; /lib/libc.so.6 (0x00002aaaaaeb0000)
+   libdl.so.2 =&gt; /lib/libdl.so.2 (0x00002aaaab0ee000)
+   /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)</pre>
+</dd>
+<dd>
+<p>No large bloated libraries (of course, none were linked in statically),
+except maybe libX11 :)</p>
+</dd>
+<p></p>
+<dt><strong><a name="item_does_it_support_tabs_2c_can_i_have_a_tabbed_rxvt_2">Does it support tabs, can I have a tabbed rxvt-unicode?</a></strong><br />
+</dt>
+<dd>
+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:
+</dd>
+<dd>
+<pre>
+   rxvt -pe tabbed</pre>
+</dd>
+<dd>
+<pre>
+   URxvt.perl-ext-common: default,tabbed</pre>
+</dd>
+<dd>
+<p>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 <em>doc/rxvt-tabbed</em> or
+the upcoming <code>Gtk2::URxvt</code> perl module, which features a tabbed urxvt
+(murxvt) terminal as an example embedding application.</p>
+</dd>
+<p></p>
 <dt><strong><a name="item_how_do_i_know_which_rxvt_2dunicode_version_i_27m_u">How do I know which rxvt-unicode version I'm using?</a></strong><br />
 </dt>
 <dd>
 The version number is displayed with the usage (-h). Also the escape
-sequence <code>ESC [ 8 n</code> sets the window title to the version number.
+sequence <code>ESC [ 8 n</code> sets the window title to the version number. When
+using the rxvtc client, the version displayed is that of the
+daemon.
 </dd>
 <p></p>
 <dt><strong><a name="item_i_am_using_debian_gnu_2flinux_and_have_a_problem_2">I am using Debian GNU/Linux and have a problem...</a></strong><br />
 </dt>
 <dd>
-The Debian GNU/Linux package of rxvt-unicode contains large patches that
+The Debian GNU/Linux package of rxvt-unicode in sarge contains large
-considerably change the behaviour of rxvt-unicode. Before reporting a
+patches that considerably change the behaviour of rxvt-unicode (but
+unfortunately this notice has been removed). Before reporting a bug to
-bug to the original rxvt-unicode author please download and install the
+the original rxvt-unicode author please download and install the genuine
-genuine version (<a href="http://software.schmorp.de#rxvt-unicode">http://software.schmorp.de#rxvt-unicode</a>) and try to
+version (<a href="http://software.schmorp.de#rxvt-unicode">http://software.schmorp.de#rxvt-unicode</a>) and try to reproduce
-reproduce the problem. If you cannot, chances are that the problems are
+the problem. If you cannot, chances are that the problems are specific to
-specific to Debian GNU/Linux, in which case it should be reported via the
+Debian GNU/Linux, in which case it should be reported via the Debian Bug
-Debian Bug Tracking System (use <code>reportbug</code> to report the bug).
+Tracking System (use <code>reportbug</code> to report the bug).
 </dd>
 <dd>
 <p>For other problems that also affect the Debian package, you can and
 probably should use the Debian BTS, 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.</p>
+</dd>
+<p></p>
+<dt><strong><a name="item_i_am_maintaining_rxvt_2dunicode_for_distribution_2">I am maintaining rxvt-unicode for distribution/OS XXX, any
+recommendation?</a></strong><br />
+</dt>
+<dd>
+You should build one binary with the default options. <em>configure</em>
+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.
+</dd>
+<dd>
+<p>You should not overwrite the <code>perl-ext-common</code> snd <code>perl-ext</code> resources
+system-wide (except maybe with <code>defaults</code>). This will result in useful
+behaviour. If your distribution aims at low memory, add an empty
+<code>perl-ext-common</code> resource to the app-defaults file. This will keep the
+perl interpreter disabled until the user enables it.</p>
+</dd>
+<dd>
+<p>If you can/want build more binaries, I recommend building a minimal
+one with <code>--disable-everything</code> (very useful) and a maximal one with
+<a href="#item__2d_2denable_2deverything"><code>--enable-everything</code></a> (less useful, it will be very big due to a lot of
+encodings built-in that increase download times and are rarely used).</p>
+</dd>
+<p></p>
+<dt><strong><a name="item_i_need_to_make_it_setuid_2fsetgid_to_support_utmp_">I need to make it setuid/setgid to support utmp/ptys on my OS, is this safe?</a></strong><br />
+</dt>
+<dd>
+It should be, starting with release 7.1. You are encouraged to properly
+install urxvt with privileges necessary for your OS now.
+</dd>
+<dd>
+<p>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 ``helpful'' to attackers).</p>
+</dd>
+<dd>
+<p>This forking is done as the very first within main(), which is very early
+and reduces possible bugs to initialisation code run before main(), or
+things like the dynamic loader of your system, which should result in very
+little risk.</p>
 </dd>
 <p></p>
 <dt><strong><a name="item_when_i_log_2din_to_another_system_it_tells_me_abou">When I log-in to another system it tells me about missing terminfo data?</a></strong><br />
 </dt>
 <dd>
    URxvt.termName: rxvt</pre>
 </dd>
 <dd>
 <p>If you don't plan to use <strong>rxvt</strong> (quite common...) you could also replace
 the rxvt terminfo file with the rxvt-unicode one.</p>
+</dd>
+<p></p>
+<dt><strong><a name="item_tic_outputs_some_error_when_compiling_the_terminfo"><code>tic</code> outputs some error when compiling the terminfo entry.</a></strong><br />
+</dt>
+<dd>
+Most likely it's the empty definition for <code>enacs=</code>. Just replace it by
+<code>enacs=\E[0@</code> and try again.
 </dd>
 <p></p>
 <dt><strong><a name="item_bash_27s_readline_does_not_work_correctly_under_rx"><code>bash</code>'s readline does not work correctly under rxvt.</a></strong><br />
 </dt>
 <dt><strong><a name="item_i_need_a_termcap_file_entry_2e">I need a termcap file entry.</a></strong><br />
 <dd>
 Try the diff in <em>doc/solaris9.patch</em> as a base. It fixes the worst
 problems with <code>wcwidth</code> and a compile problem.
 </dd>
 <p></p>
+<dt><strong><a name="item_how_can_i_use_rxvt_2dunicode_under_cygwin_3f">How can I use rxvt-unicode under cygwin?</a></strong><br />
+</dt>
+<dd>
+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 <code>-multiwindow</code> or
+<code>-rootless</code> mode instead, which will result in similar look&amp;feel as the
+old libW11 emulation.
+</dd>
+<dd>
+<p>At the time of this writing, cygwin didn't seem to support any multi-byte
+encodings (you might try <code>LC_CTYPE=C-UTF-8</code>), so you are likely limited
+to 8-bit encodings.</p>
+</dd>
+<p></p>
 <dt><strong><a name="item_how_does_rxvt_2dunicode_determine_the_encoding_to_">How does rxvt-unicode determine the encoding to use?</a></strong><br />
 </dt>
 <dt><strong><a name="item_is_there_an_option_to_switch_encodings_3f">Is there an option to switch encodings?</a></strong><br />
 </dt>
 <dd>
 You can specify separate locales for the input method and the rest of the
 terminal, using the resource <code>imlocale</code>:
 </dd>
 <dd>
 <pre>
-   URxvt*imlocale: ja_JP.EUC-JP</pre>
+   URxvt.imlocale: ja_JP.EUC-JP</pre>
 </dd>
 <dd>
 <p>Now you can start your terminal with <code>LC_CTYPE=ja_JP.UTF-8</code> and still
 use your input method. Please note, however, that you will not be able to
 input characters outside <code>EUC-JP</code> in a normal way then, as your input
 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.
 </dd>
 <dd>
 <p>Also, many people (me included) like large windows and even larger
-scrollback buffers: Without <a href="#item__2d_2denable_2dunicode3"><code>--enable-unicode3</code></a>, rxvt-unicode will use
+scrollback buffers: Without <code>--enable-unicode3</code>, 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 <a href="#item__2d_2denable_2dunicode3"><code>--enable-unicode3</code></a> it gets worse, as
+use 10 Megabytes of memory. With <code>--enable-unicode3</code> it gets worse, as
 rxvt-unicode then uses 8 bytes per screen cell.</p>
 </dd>
 <p></p>
 <dt><strong><a name="item_can_i_speed_up_xft_rendering_somehow_3f">Can I speed up Xft rendering somehow?</a></strong><br />
 </dt>
 <dd>
 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 <code>:antialiasing=false</code>), which saves lots of
+antialiasing (by appending <code>:antialias=false</code>), which saves lots of
 memory and also speeds up rendering considerably.
 </dd>
 <p></p>
 <dt><strong><a name="item_rxvt_2dunicode_doesn_27t_seem_to_anti_2dalias_its_">Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?</a></strong><br />
 </dt>
 <dd>
 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 <code>rxvt(7)</code>
+depressed.
 </dd>
 <p></p>
 <dt><strong><a name="item_what_27s_with_this_bold_2fblink_stuff_3f">What's with this bold/blink stuff?</a></strong><br />
 </dt>
 <dd>
 </dd>
 <p></p>
 <dt><strong><a name="item_how_can_i_start_rxvtd_in_a_race_2dfree_way_3f">How can I start rxvtd in a race-free way?</a></strong><br />
 </dt>
 <dd>
-Despite it's name, rxvtd is not a real daemon, but more like a
+Try <code>rxvtd -f -o</code>, which tells rxvtd to open the
-server that answers rxvtc's requests, so it doesn't background
+display, create the listening socket and then fork.
-itself.
-</dd>
-<dd>
-<p>To ensure rxvtd is listening on it's socket, you can use the
-following method to wait for the startup message before continuing:</p>
-</dd>
-<dd>
-<pre>
-  { rxvtd &amp; } | read</pre>
 </dd>
 <p></p>
 <dt><strong><a name="item_what_27s_with_the_strange_backspace_2fdelete_key_b">What's with the strange Backspace/Delete key behaviour?</a></strong><br />
 </dt>
 <dd>
    # use Backspace = ^?
    $ stty erase ^?
    $ rxvt</pre>
 </dd>
 <dd>
-<p>Toggle with <code>ESC [ 36 h</code> / <code>ESC [ 36 l</code> as documented in rxvt(7).</p>
+<p>Toggle with <code>ESC [ 36 h</code> / <code>ESC [ 36 l</code>.</p>
 </dd>
 <dd>
 <p>For an existing rxvt-unicode:</p>
 </dd>
 <dd>
 </p>
 <hr />
 <h1><a name="description">DESCRIPTION</a></h1>
 <p>The rest of this document describes various technical aspects of
 <strong>rxvt-unicode</strong>. 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 <code>configure</code> time.</p>
+selectable at <code>configure</code> time.</p>
 <p>
 </p>
 <hr />
 <h1><a name="definitions">Definitions</a></h1>
 <dl>
 </table><dt><strong><a name="item_ps__3d_9_x10_xterm"><strong><code>Ps = 9</code> </strong>&gt; X10 XTerm</a></strong><br />
 </dt>
 <table>
 <tr><td>h</td><td>Send Mouse X & Y on button press.</td></tr>
 <tr><td>l</td><td>No mouse reporting.</td></tr>
-</table><dt><strong><a name="item_10"><strong><code>Ps = 10</code> </strong>&gt; (<strong>rxvt</strong>)</a></strong><br />
-</dt>
-<table>
-<tr><td>h</td><td>menuBar visible</td></tr>
-<tr><td>l</td><td>menuBar invisible</td></tr>
 </table><dt><strong><a name="item_ps__3d_25"><strong><code>Ps = 25</code> </strong>&gt;</a></strong><br />
 </dt>
 <table>
 <tr><td>h</td><td>Visible cursor {cnorm/cvvis}</td></tr>
 <tr><td>l</td><td>Invisible cursor {civis}</td></tr>
 </table><dt><strong><a name="item_1011"><strong><code>Ps = 1011</code> </strong>&gt; (<strong>rxvt</strong>)</a></strong><br />
 </dt>
 <table>
 <tr><td>h</td><td>Scroll to bottom when a key is pressed</td></tr>
 <tr><td>l</td><td>Don't scroll to bottom when a key is pressed</td></tr>
+</table><dt><strong><a name="item_1021"><strong><code>Ps = 1021</code> </strong>&gt; (<strong>rxvt</strong>)</a></strong><br />
+</dt>
+<table>
+<tr><td>h</td><td>Bold/italic implies high intensity (see option -is)</td></tr>
+<tr><td>l</td><td>Font styles have no effect on intensity (Compile styles)</td></tr>
 </table><dt><strong><a name="item_ps__3d_1047"><strong><code>Ps = 1047</code> </strong>&gt;</a></strong><br />
 </dt>
 <table>
 <tr><td>h</td><td>Use Alternate Screen Buffer</td></tr>
 <tr><td>l</td><td>Use Normal Screen Buffer - clear Alternate Screen Buffer if returning from it</td></tr>
 <tr><td>Ps = 10</td><td>Change colour of text foreground to Pt (NB: may change in future)</td></tr>
 <tr><td>Ps = 11</td><td>Change colour of text background to Pt (NB: may change in future)</td></tr>
 <tr><td>Ps = 12</td><td>Change colour of text cursor foreground to Pt</td></tr>
 <tr><td>Ps = 13</td><td>Change colour of mouse foreground to Pt</td></tr>
 <tr><td>Ps = 17</td><td>Change colour of highlight characters to Pt</td></tr>
-<tr><td>Ps = 18</td><td>Change colour of bold characters to Pt</td></tr>
+<tr><td>Ps = 18</td><td>Change colour of bold characters to Pt [deprecated, see 706]</td></tr>
-<tr><td>Ps = 19</td><td>Change colour of underlined characters to Pt</td></tr>
+<tr><td>Ps = 19</td><td>Change colour of underlined characters to Pt [deprecated, see 707]</td></tr>
-<tr><td>Ps = 20</td><td>Change default background to Pt</td></tr>
+<tr><td>Ps = 20</td><td>Change background pixmap parameters (see section XPM) (Compile XPM).</td></tr>
 <tr><td>Ps = 39</td><td>Change default foreground colour to Pt.</td></tr>
 <tr><td>Ps = 46</td><td>Change Log File to Pt unimplemented</td></tr>
 <tr><td>Ps = 49</td><td>Change default background colour to Pt.</td></tr>
 <tr><td>Ps = 50</td><td>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</td></tr>
 <tr><td>Ps = 55</td><td>Log all scrollback buffer and all of screen to Pt</td></tr>
 <tr><td>Ps = 701</td><td>Change current locale to Pt, or, if Pt is ?, return the current locale (Compile frills).</td></tr>
-<tr><td>Ps = 703</td><td>Menubar command Pt (Compile menubar).</td></tr>
+<tr><td>Ps = 702</td><td>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.</td></tr>
 <tr><td>Ps = 704</td><td>Change colour of italic characters to Pt</td></tr>
 <tr><td>Ps = 705</td><td>Change background pixmap tint colour to Pt (Compile transparency).</td></tr>
+<tr><td>Ps = 706</td><td>Change colour of bold characters to Pt</td></tr>
+<tr><td>Ps = 707</td><td>Change colour of underlined characters to Pt</td></tr>
 <tr><td>Ps = 710</td><td>Set normal fontset to Pt. Same as Ps = 50.</td></tr>
 <tr><td>Ps = 711</td><td>Set bold fontset to Pt. Similar to Ps = 50 (Compile styles).</td></tr>
 <tr><td>Ps = 712</td><td>Set italic fontset to Pt. Similar to Ps = 50 (Compile styles).</td></tr>
 <tr><td>Ps = 713</td><td>Set bold-italic fontset to Pt. Similar to Ps = 50 (Compile styles).</td></tr>
 <tr><td>Ps = 720</td><td>Move viewing window up by Pt lines, or clear scrollback buffer if Pt = 0 (Compile frills).</td></tr>
 <tr><td>Ps = 721</td><td>Move viewing window down by Pt lines, or clear scrollback buffer if Pt = 0 (Compile frills).</td></tr>
+<tr><td>Ps = 777</td><td>Call the perl extension with the given string, which should be of the form extension:parameters (Compile perl).</td></tr>
 </table><p></p></dl>
 <p></p>
-<p>
-</p>
-<hr />
-<h1><a name="menubar">menuBar</a></h1>
-<p><strong>The exact syntax used is <em>almost</em> solidified. </strong>&gt;
-In the menus, <strong>DON'T</strong> try to use menuBar commands that add or remove a
-menuBar.</p>
-<p>Note that in all of the commands, the <strong><em>/path/</em> </strong>&gt; <em>cannot</em> be
-omitted: use <strong>./</strong> to specify a menu relative to the current menu.</p>
-<p>
-</p>
-<h2><a name="overview_of_menubar_operation">Overview of menuBar operation</a></h2>
-<p>For the menuBar XTerm escape sequence <code>ESC ] 703 ; Pt ST</code>, the syntax
-of <a href="#item_pt"><code>Pt</code></a> can be used for a variety of tasks:</p>
-<p>At the top level is the current menuBar which is a member of a circular
-linked-list of other such menuBars.</p>
-<p>The menuBar acts as a parent for the various drop-down menus, which in
-turn, may have labels, separator lines, menuItems and subMenus.</p>
-<p>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.</p>
-<p>The menuBar syntax is intended to provide a simple yet robust method of
-constructing and manipulating menus and navigating through the
-menuBars.</p>
-<p>The first step is to use the tag <strong>[menu:<em>name</em>] </strong>&gt; which creates
-the menuBar called <em>name</em> and allows access. You may now or menus,
-subMenus, and menuItems. Finally, use the tag <strong>[done]</strong> to set the
-menuBar access as <strong>readonly</strong> to prevent accidental corruption of the
-menus. To re-access the current menuBar for alterations, use the tag
-<strong>[menu]</strong>, make the alterations and then use <strong>[done]</strong></p>
-<p></p>
-<p>
-</p>
-<h2><a name="commands">Commands</a></h2>
-<dl>
-<dt><strong><a name="item__5bmenu_3a_2bname_5d"><strong>[menu:+<em>name</em>] </strong>&gt;</a></strong><br />
-</dt>
-<dd>
-access the named menuBar for creation or alteration. If a new menuBar
-is created, it is called <em>name</em> (max of 15 chars) and the current
-menuBar is pushed onto the stack
-</dd>
-<p></p>
-<dt><strong><a name="item__5bmenu_5d"><strong>[menu]</strong></a></strong><br />
-</dt>
-<dd>
-access the current menuBar for alteration
-</dd>
-<p></p>
-<dt><strong><a name="item__5btitle_3a_2bstring_5d"><strong>[title:+<em>string</em>] </strong>&gt;</a></strong><br />
-</dt>
-<dd>
-set the current menuBar's title to <em>string</em>, which may contain the
-following format specifiers:
-</dd>
-<dd>
-<pre>
-   B&lt;%n&gt;  rxvt name (as per the B&lt;-name&gt; command-line option)
-   B&lt;%v&gt;  rxvt version
-   B&lt;%%&gt;  literal B&lt;%&gt; character</pre>
-</dd>
-<p></p>
-<dt><strong><a name="item__5bdone_5d"><strong>[done]</strong></a></strong><br />
-</dt>
-<dd>
-set menuBar access as <strong>readonly</strong>.
-End-of-file tag for <strong>[read:+<em>file</em>] </strong>&gt; operations.
-</dd>
-<p></p>
-<dt><strong><a name="item__5bread_3a_2bfile_5d"><strong>[read:+<em>file</em>] </strong>&gt;</a></strong><br />
-</dt>
-<dd>
-read menu commands directly from <em>file</em> (extension ``.menu'' will be
-appended if required.) Start reading at a line with <strong>[menu]</strong> or <strong>&lt;
-[menu:+<em>name</em> </strong>&gt; and continuing until <strong>[done]</strong> is encountered.
-</dd>
-<dd>
-<p>Blank and comment lines (starting with <strong>#</strong>) 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!.</p>
-</dd>
-<p></p>
-<dt><strong><a name="item__5bread_3a_2bfile_3b_2bname_5d"><strong>[read:+<em>file</em>;+<em>name</em>] </strong>&gt;</a></strong><br />
-</dt>
-<dd>
-The same as <strong>[read:+<em>file</em>] </strong>&gt;, but start reading at a line with
-<strong>[menu:+<em>name</em>] </strong>&gt; and continuing until <strong>[done:+<em>name</em>] </strong>&gt; or
-<strong>[done]</strong> is encountered.
-</dd>
-<p></p>
-<dt><strong><a name="item__5bdump_5d"><strong>[dump]</strong></a></strong><br />
-</dt>
-<dd>
-dump all menuBars to the file <strong>/tmp/rxvt-PID</strong> in a format suitable for
-later rereading.
-</dd>
-<p></p>
-<dt><strong><a name="item__5brm_3aname_5d"><strong>[rm:name]</strong></a></strong><br />
-</dt>
-<dd>
-remove the named menuBar
-</dd>
-<p></p>
-<dt><strong><a name="item__5brm_5d__5brm_3a_5d"><strong>[rm] [rm:]</strong></a></strong><br />
-</dt>
-<dd>
-remove the current menuBar
-</dd>
-<p></p>
-<dt><strong><a name="item__5brm_2a_5d__5brm_3a_2a_5d"><strong>[rm*] [rm:*]</strong></a></strong><br />
-</dt>
-<dd>
-remove all menuBars
-</dd>
-<p></p>
-<dt><strong><a name="item__5bswap_5d"><strong>[swap]</strong></a></strong><br />
-</dt>
-<dd>
-swap the top two menuBars
-</dd>
-<p></p>
-<dt><strong><a name="item__5bprev_5d"><strong>[prev]</strong></a></strong><br />
-</dt>
-<dd>
-access the previous menuBar
-</dd>
-<p></p>
-<dt><strong><a name="item__5bnext_5d"><strong>[next]</strong></a></strong><br />
-</dt>
-<dd>
-access the next menuBar
-</dd>
-<p></p>
-<dt><strong><a name="item__5bshow_5d"><strong>[show]</strong></a></strong><br />
-</dt>
-<dd>
-Enable display of the menuBar
-</dd>
-<p></p>
-<dt><strong><a name="item__5bhide_5d"><strong>[hide]</strong></a></strong><br />
-</dt>
-<dd>
-Disable display of the menuBar
-</dd>
-<p></p>
-<dt><strong><a name="item__5bpixmap_3a_2bname_5d"><strong>[pixmap:+<em>name</em>] </strong>&gt;</a></strong><br />
-</dt>
-<dt><strong><a name="item__5bpixmap_3a_2bname_3bscaling_5d"><strong>[pixmap:+<em>name</em>;<em>scaling</em>] </strong>&gt;</a></strong><br />
-</dt>
-<dd>
-(set the background pixmap globally
-</dd>
-<dd>
-<p><strong>A Future implementation <em>may</em> make this local to the menubar </strong>&gt;)</p>
-</dd>
-<p></p>
-<dt><strong><a name="item__5b_3a_2bcommand_3a_5d"><strong>[:+<em>command</em>:] </strong>&gt;</a></strong><br />
-</dt>
-<dd>
-ignore the menu readonly status and issue a <em>command</em> to or a menu or
-menuitem or change the ; a useful shortcut for setting the quick arrows
-from a menuBar.
-</dd>
-<p></p></dl>
-<p></p>
-<p>
-</p>
-<h2><a name="adding_and_accessing_menus">Adding and accessing menus</a></h2>
-<p>The following commands may also be <strong>+</strong> prefixed.</p>
-<dl>
-<dt><strong><a name="item__2f_2b"><strong>/+</strong></a></strong><br />
-</dt>
-<dd>
-access menuBar top level
-</dd>
-<p></p>
-<dt><strong><a name="item__2e_2f_2b"><strong>./+</strong></a></strong><br />
-</dt>
-<dd>
-access current menu level
-</dd>
-<p></p>
-<dt><strong><a name="item__2e_2e_2f_2b"><strong>../+</strong></a></strong><br />
-</dt>
-<dd>
-access parent menu (1 level up)
-</dd>
-<p></p>
-<dt><strong><a name="item__2e_2e_2f_2e_2e_2f"><strong>../../</strong></a></strong><br />
-</dt>
-<dd>
-access parent menu (multiple levels up)
-</dd>
-<p></p>
-<dt><strong><a name="item__2fpath_2fmenu"><strong><em>/path/</em>menu </strong>&gt;</a></strong><br />
-</dt>
-<dd>
-add/access menu
-</dd>
-<p></p>
-<dt><strong><a name="item__2fpath_2fmenu_2f_2a"><strong><em>/path/</em>menu/* </strong>&gt;</a></strong><br />
-</dt>
-<dd>
-add/access menu and clear it if it exists
-</dd>
-<p></p>
-<dt><strong><a name="item__2fpath_2f_7b_2d_7d"><strong><em>/path/</em>{-} </strong>&gt;</a></strong><br />
-</dt>
-<dd>
-add separator
-</dd>
-<p></p>
-<dt><strong><a name="item__2fpath_2f_7bitem_7d"><strong><em>/path/</em>{item} </strong>&gt;</a></strong><br />
-</dt>
-<dd>
-add <strong>item</strong> as a label
-</dd>
-<p></p>
-<dt><strong><a name="item__2fpath_2f_7bitem_7d_action"><strong><em>/path/</em>{item} action </strong>&gt;</a></strong><br />
-</dt>
-<dd>
-add/alter <em>menuitem</em> with an associated <em>action</em>
-</dd>
-<p></p>
-<dt><strong><a name="item__2fpath_2f_7bitem_7d_7bright_2dtext_7d"><strong><em>/path/</em>{item}{right-text} </strong>&gt;</a></strong><br />
-</dt>
-<dd>
-add/alter <em>menuitem</em> with <strong>right-text</strong> as the right-justified text
-and as the associated <em>action</em>
-</dd>
-<p></p>
-<dt><strong><a name="item__2fpath_2f_7bitem_7d_7brtext_7d_action"><strong><em>/path/</em>{item}{rtext} action </strong>&gt;</a></strong><br />
-</dt>
-<dd>
-add/alter <em>menuitem</em> with an associated <em>action</em> and with <strong>rtext</strong> as
-the right-justified text.
-</dd>
-<p></p></dl>
-<dl>
-<dt><strong><a name="item_special_characters_in_action_must_be_backslash_2de">Special characters in <em>action</em> must be backslash-escaped:</a></strong><br />
-</dt>
-<dd>
-<strong>\a \b \E \e \n \r \t \octal</strong>
-</dd>
-<p></p>
-<dt><strong><a name="item_or_in_control_2dcharacter_notation_3a">or in control-character notation:</a></strong><br />
-</dt>
-<dd>
-<strong>^@, ^A .. ^Z .. ^_, ^?</strong>
-</dd>
-<p></p></dl>
-<p>To send a string starting with a <strong>NUL</strong> (<strong>^@</strong>) character to the
-program, start <em>action</em> with a pair of <strong>NUL</strong> characters (<strong>^@^@</strong>),
-the first of which will be stripped off and the balance directed to the
-program. Otherwise if <em>action</em> begins with <strong>NUL</strong> followed by
-non-+<strong>NUL</strong> characters, the leading <strong>NUL</strong> is stripped off and the
-balance is sent back to rxvt.</p>
-<p>As a convenience for the many Emacs-type editors, <em>action</em> may start
-with <strong>M-</strong> (eg, <strong>M-$</strong> is equivalent to <strong>\E$</strong>) and a <strong>CR</strong> will be
-appended if missed from <strong>M-x</strong> commands.</p>
-<p>As a convenience for issuing XTerm <strong>ESC ]</strong> sequences from a menubar (or
-quick arrow), a <strong>BEL</strong> (<strong>^G</strong>) will be appended if needed.</p>
-<dl>
-<dt><strong><a name="item_for_example_2c">For example,</a></strong><br />
-</dt>
-<dd>
-<strong>M-xapropos</strong> is equivalent to <strong>\Exapropos\r</strong>
-</dd>
-<p></p>
-<dt><strong><a name="item_and">and</a></strong><br />
-</dt>
-<dd>
-<strong>\E]703;mona;100</strong> is equivalent to <strong>\E]703;mona;100\a</strong>
-</dd>
-<p></p></dl>
-<p>The option <strong>{<em>right-rtext</em>} </strong>&gt; will be right-justified. In the
-absence of a specified action, this text will be used as the <em>action</em>
-as well.</p>
-<dl>
-<dt><strong>For example,</strong><br />
-</dt>
-<dd>
-<strong>/File/{Open}{^X^F}</strong> is equivalent to <strong>/File/{Open}{^X^F} ^X^F</strong>
-</dd>
-<p></p></dl>
-<p>The left label <em>is</em> 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.</p>
-<dl>
-<dt><strong>For example,</strong><br />
-</dt>
-<dd>
-<strong>/File/{Open}{Open} Open-File-Action</strong>
-</dd>
-<p></p>
-<dt><strong><a name="item_or_hiding_it">or hiding it</a></strong><br />
-</dt>
-<dd>
-<strong>/File/{.anylabel}{Open} Open-File-Action</strong>
-</dd>
-<p></p></dl>
-<p></p>
-<p>
-</p>
-<h2><a name="removing_menus">Removing menus</a></h2>
-<dl>
-<dt><strong><a name="item__2d_2f_2a_2b"><strong>-/*+ </strong>&gt;</a></strong><br />
-</dt>
-<dd>
-remove all menus from the menuBar, the same as <strong>[clear]</strong>
-</dd>
-<p></p>
-<dt><strong><a name="item__2d_2b_2fpathmenu_2b"><strong>-+<em>/path</em>menu+ </strong>&gt;</a></strong><br />
-</dt>
-<dd>
-remove menu
-</dd>
-<p></p>
-<dt><strong><a name="item__2d_2b_2fpath_7bitem_7d_2b"><strong>-+<em>/path</em>{item}+ </strong>&gt;</a></strong><br />
-</dt>
-<dd>
-remove item
-</dd>
-<p></p>
-<dt><strong><a name="item__2d_2b_2fpath_7b_2d_7d"><strong>-+<em>/path</em>{-} </strong>&gt;</a></strong><br />
-</dt>
-<dd>
-remove separator)
-</dd>
-<p></p>
-<dt><strong><a name="item__2d_2fpath_2fmenu_2f_2a"><strong>-/path/menu/*</strong></a></strong><br />
-</dt>
-<dd>
-remove all items, separators and submenus from menu
-</dd>
-<p></p></dl>
-<p></p>
-<p>
-</p>
-<h2><a name="quick_arrows">Quick Arrows</a></h2>
-<p>The menus also provide a hook for <em>quick arrows</em> 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:</p>
-<dl>
-<dt><strong><a name="item__3cr_3e_2bright"><strong>&lt;r</strong>+<em>Right</em> &gt;&gt;</a></strong><br />
-</dt>
-<dt><strong><a name="item__3cl_3e_2bleft"><strong>&lt;l</strong>+<em>Left</em> &gt;&gt;</a></strong><br />
-</dt>
-<dt><strong><a name="item__3cu_3e_2bup"><strong>&lt;u</strong>+<em>Up</em> &gt;&gt;</a></strong><br />
-</dt>
-<dt><strong><a name="item__3cd_3e_2bdown"><strong>&lt;d</strong>+<em>Down</em> &gt;&gt;</a></strong><br />
-</dt>
-<dd>
-Define actions for the respective arrow buttons
-</dd>
-<p></p>
-<dt><strong><a name="item__3cb_3e_2bbegin"><strong>&lt;b</strong>+<em>Begin</em> &gt;&gt;</a></strong><br />
-</dt>
-<dt><strong><a name="item__3ce_3e_2bend"><strong>&lt;e</strong>+<em>End</em> &gt;&gt;</a></strong><br />
-</dt>
-<dd>
-Define common beginning/end parts for <em>quick arrows</em> which used in
-conjunction with the above &lt;r&gt; &lt;l&gt; &lt;u&gt; &lt;d&gt; constructs
-</dd>
-<p></p></dl>
-<dl>
-<dt><strong><a name="item_for_example_2c_define_arrows_individually_2c">For example, define arrows individually,</a></strong><br />
-</dt>
-<dd>
-<pre>
- &lt;u&gt;\E[A</pre>
-</dd>
-<dd>
-<pre>
- &lt;d&gt;\E[B</pre>
-</dd>
-<dd>
-<pre>
- &lt;r&gt;\E[C</pre>
-</dd>
-<dd>
-<pre>
- &lt;l&gt;\E[D</pre>
-</dd>
-<dt><strong><a name="item_or_all_at_once">or all at once</a></strong><br />
-</dt>
-<dd>
-<pre>
- &lt;u&gt;\E[AZ&lt;&gt;&lt;d&gt;\E[BZ&lt;&gt;&lt;r&gt;\E[CZ&lt;&gt;&lt;l&gt;\E[D</pre>
-</dd>
-<dt><strong><a name="item_compactly">or more compactly (factoring out common parts)</a></strong><br />
-</dt>
-<dd>
-<pre>
- &lt;b&gt;\E[&lt;u&gt;AZ&lt;&gt;&lt;d&gt;BZ&lt;&gt;&lt;r&gt;CZ&lt;&gt;&lt;l&gt;D</pre>
-</dd>
-</dl>
-<p></p>
-<p>
-</p>
-<h2><a name="command_summary">Command Summary</a></h2>
-<p>A short summary of the most <em>common</em> commands:</p>
-<dl>
-<dt><strong><a name="item__5bmenu_3aname_5d">[menu:name]</a></strong><br />
-</dt>
-<dd>
-use an existing named menuBar or start a new one
-</dd>
-<p></p>
-<dt><strong>[menu]</strong><br />
-</dt>
-<dd>
-use the current menuBar
-</dd>
-<p></p>
-<dt><strong><a name="item__5btitle_3astring_5d">[title:string]</a></strong><br />
-</dt>
-<dd>
-set menuBar title
-</dd>
-<p></p>
-<dt><strong>[done]</strong><br />
-</dt>
-<dd>
-set menu access to readonly and, if reading from a file, signal EOF
-</dd>
-<p></p>
-<dt><strong><a name="item__5bdone_3aname_5d">[done:name]</a></strong><br />
-</dt>
-<dd>
-if reading from a file using [read:file;name] signal EOF
-</dd>
-<p></p>
-<dt><strong>[rm:name]</strong><br />
-</dt>
-<dd>
-remove named <code>menuBar(s)</code>
-</dd>
-<p></p>
-<dt><strong>[rm] [rm:]</strong><br />
-</dt>
-<dd>
-remove current menuBar
-</dd>
-<p></p>
-<dt><strong>[rm*] [rm:*]</strong><br />
-</dt>
-<dd>
-remove all <code>menuBar(s)</code>
-</dd>
-<p></p>
-<dt><strong>[swap]</strong><br />
-</dt>
-<dd>
-swap top two menuBars
-</dd>
-<p></p>
-<dt><strong>[prev]</strong><br />
-</dt>
-<dd>
-access the previous menuBar
-</dd>
-<p></p>
-<dt><strong>[next]</strong><br />
-</dt>
-<dd>
-access the next menuBar
-</dd>
-<p></p>
-<dt><strong>[show]</strong><br />
-</dt>
-<dd>
-map menuBar
-</dd>
-<p></p>
-<dt><strong>[hide]</strong><br />
-</dt>
-<dd>
-unmap menuBar
-</dd>
-<p></p>
-<dt><strong><a name="item__5bpixmap_3bfile_5d">[pixmap;file]</a></strong><br />
-</dt>
-<dt><strong><a name="item__5bpixmap_3bfile_3bscaling_5d">[pixmap;file;scaling]</a></strong><br />
-</dt>
-<dd>
-set a background pixmap
-</dd>
-<p></p>
-<dt><strong><a name="item__5bread_3afile_5d">[read:file]</a></strong><br />
-</dt>
-<dt><strong><a name="item__5bread_3afile_3bname_5d">[read:file;name]</a></strong><br />
-</dt>
-<dd>
-read in a menu from a file
-</dd>
-<p></p>
-<dt><strong>[dump]</strong><br />
-</dt>
-<dd>
-dump out all menuBars to /tmp/rxvt-PID
-</dd>
-<p></p>
-<dt><strong><a name="item__2f">/</a></strong><br />
-</dt>
-<dd>
-access menuBar top level
-</dd>
-<p></p>
-<dt><strong><a name="item__2e_2f">./</a></strong><br />
-</dt>
-<dt><strong><a name="item__2e_2e_2f">../</a></strong><br />
-</dt>
-<dt><strong>../../</strong><br />
-</dt>
-<dd>
-access current or parent menu level
-</dd>
-<p></p>
-<dt><strong>/path/menu</strong><br />
-</dt>
-<dd>
-add/access menu
-</dd>
-<p></p>
-<dt><strong>/path/{-}</strong><br />
-</dt>
-<dd>
-add separator
-</dd>
-<p></p>
-<dt><strong>/path/{item}{rtext} action</strong><br />
-</dt>
-<dd>
-add/alter menu item
-</dd>
-<p></p>
-<dt><strong><a name="item__2d_2f_2a">-/*</a></strong><br />
-</dt>
-<dd>
-remove all menus from the menuBar
-</dd>
-<p></p>
-<dt><strong><a name="item__2d_2fpath_2fmenu">-/path/menu</a></strong><br />
-</dt>
-<dd>
-remove menu items, separators and submenus from menu
-</dd>
-<p></p>
-<dt><strong>-/path/menu</strong><br />
-</dt>
-<dd>
-remove menu
-</dd>
-<p></p>
-<dt><strong><a name="item__2d_2fpath_2f_7bitem_7d">-/path/{item}</a></strong><br />
-</dt>
-<dd>
-remove item
-</dd>
-<p></p>
-<dt><strong><a name="item__2d_2fpath_2f_7b_2d_7d">-/path/{-}</a></strong><br />
-</dt>
-<dd>
-remove separator
-</dd>
-<p></p>
-<dt><strong><a name="item__3cb_3ebegin_3cr_3eright_3cl_3eleft_3cu_3eup_3cd_3">&lt;b&gt;Begin&lt;r&gt;Right&lt;l&gt;Left&lt;u&gt;Up&lt;d&gt;Down&lt;e&gt;End</a></strong><br />
-</dt>
-<dd>
-menu quick arrows
-</dd>
-<p></p></dl>
 <p>
 </p>
 <hr />
 <h1><a name="xpm">XPM</a></h1>
 <p>For the XPM XTerm escape sequence <strong><code>ESC ] 20 ; Pt ST</code> </strong>&gt; then value
 </table><p>
 </p>
 <hr />
 <h1><a name="configure_options">CONFIGURE OPTIONS</a></h1>
 <p>General hint: if you get compile errors, then likely your configuration
-hasn't been tested well. Either try with --enable-everything or use the
+hasn't been tested well. Either try with <a href="#item__2d_2denable_2deverything"><code>--enable-everything</code></a> or use
-./reconf script as a base for experiments. ./reconf is used by myself,
+the <em>./reconf</em> script as a base for experiments. <em>./reconf</em> is used by
-so it should generally be a working config. Of course, you should always
+myself, so it should generally be a working config. Of course, you should
-report when a combination doesn't work, so it can be fixed. Marc Lehmann
+always report when a combination doesn't work, so it can be fixed. Marc
-&lt;<a href="mailto:rxvt@schmorp.de">rxvt@schmorp.de</a>&gt;.</p>
+Lehmann &lt;<a href="mailto:rxvt@schmorp.de">rxvt@schmorp.de</a>&gt;.</p>
+<p>All</p>
 <dl>
 <dt><strong><a name="item__2d_2denable_2deverything">--enable-everything</a></strong><br />
 </dt>
 <dd>
-Add support for all non-multichoice options listed in ``./configure
+Add (or remove) support for all non-multichoice options listed in ``./configure
---help''. Note that unlike other enable options this is order dependant.
+--help''.
-You can specify this and then disable options which this enables by
+</dd>
-<em>following</em> this with the appropriate commands.
-</dd>
+<dd>
+<p>You can specify this and then disable options you do not like by
+<em>following</em> this with the appropriate <code>--disable-...</code> arguments,
+or you can start with a minimal configuration by specifying
+<code>--disable-everything</code> and than adding just the <code>--enable-...</code> arguments
+you want.</p>
+</dd>
 <p></p>
-<dt><strong><a name="item__2d_2denable_2dxft">--enable-xft</a></strong><br />
+<dt><strong><a name="item_xft">--enable-xft (default: enabled)</a></strong><br />
 </dt>
 <dd>
 Add support for Xft (anti-aliases, among others) fonts. Xft fonts are
 slower and require lots of memory, but as long as you don't use them, you
 don't pay for them.
 </dd>
 <p></p>
-<dt><strong><a name="item__2d_2denable_2dfont_2dstyles">--enable-font-styles</a></strong><br />
+<dt><strong><a name="item_styles">--enable-font-styles (default: on)</a></strong><br />
 </dt>
 <dd>
 Add support for <strong>bold</strong>, <em>italic</em> and <strong><em>bold italic</em> </strong>&gt; font
 styles. The fonts can be set manually or automatically.
 </dd>
 <p></p>
-<dt><strong><a name="item__2d_2dwith_2dcodesets_3dname_2c_2e_2e_2e">--with-codesets=NAME,...</a></strong><br />
+<dt><strong><a name="item__2d_2dwith_2dcodesets_3dname_2c_2e_2e_2e__28defaul">--with-codesets=NAME,... (default: all)</a></strong><br />
 </dt>
 <dd>
 Compile in support for additional codeset (encoding) groups (<code>eu</code>, <code>vn</code>
 are always compiled in, which includes most 8-bit character sets). These
 codeset tables are used for driving X11 core fonts, they are not required
 <tr><td>zh_ext</td><td>rarely used but very big chinese encodigs</td></tr>
 <tr><td>jp</td><td>common japanese encodings</td></tr>
 <tr><td>jp_ext</td><td>rarely used but big japanese encodings</td></tr>
 <tr><td>kr</td><td>korean encodings</td></tr>
 </table><p></p>
-<dt><strong><a name="item__2d_2denable_2dxim">--enable-xim</a></strong><br />
+<dt><strong><a name="item_xim">--enable-xim (default: on)</a></strong><br />
 </dt>
 <dd>
 Add support for XIM (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.
 </dd>
 <p></p>
-<dt><strong><a name="item__2d_2denable_2dunicode3">--enable-unicode3</a></strong><br />
+<dt><strong><a name="item_unicode3">--enable-unicode3 (default: off)</a></strong><br />
 </dt>
+<dd>
+Recommended to stay off unless you really need non-BMP characters.
-<dd>
+</dd>
+<dd>
-Enable direct support for displaying unicode codepoints above
+<p>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.
+support these extra characters, but Xft does.</p>
 </dd>
 <dd>
 <p>Please note that rxvt-unicode can store unicode code points &gt;65535
 even without this flag, but the number of such characters is
 limited to a view thousand (shared with combining characters,
 see next switch), and right now rxvt-unicode cannot display them
 (input/output and cut&amp;paste still work, though).</p>
 </dd>
 <p></p>
-<dt><strong><a name="item__2d_2denable_2dcombining">--enable-combining</a></strong><br />
+<dt><strong><a name="item_combining">--enable-combining (default: on)</a></strong><br />
 </dt>
 <dd>
 Enable automatic composition of combining characters into
 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.
 </dd>
 <dd>
-<p>Without --enable-unicode3, the number of additional precomposed characters
+<p>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.</p>
+(ab-)used). With --enable-unicode3, no practical limit exists.</p>
 </dd>
 <dd>
 <p>This option will also enable storage (but not display) of characters
 beyond plane 0 (&gt;65535) when --enable-unicode3 was not specified.</p>
 </dd>
 <p>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...).</p>
 </dd>
 <p></p>
-<dt><strong><a name="item_fallback">--enable-fallback(=CLASS)</a></strong><br />
+<dt><strong><a name="item_fallback">--enable-fallback(=CLASS) (default: Rxvt)</a></strong><br />
 </dt>
 <dd>
-When reading resource settings, also read settings for class CLASS
+When reading resource settings, also read settings for class CLASS. To
-(default: Rxvt). To disable resource fallback use --disable-fallback.
+disable resource fallback use --disable-fallback.
-</dd>
-<p></p>
-<dt><strong><a name="item__2d_2dwith_2dres_2dname_3dname">--with-res-name=NAME</a></strong><br />
-</dt>
-<dd>
+</dd>
+<p></p>
+<dt><strong><a name="item_name">--with-res-name=NAME (default: urxvt)</a></strong><br />
+</dt>
+<dd>
-Use the given name (default: urxvt) as default application name when
+Use the given name as default application name when
 reading resources. Specify --with-res-name=rxvt to replace rxvt.
 </dd>
 <p></p>
-<dt><strong><a name="item__2d_2dwith_2dres_2dclass_3dclass">--with-res-class=CLASS</a></strong><br />
+<dt><strong><a name="item__2d_2dwith_2dres_2dclass_3dclass__2fdefault_3a_urx">--with-res-class=CLASS /default: URxvt)</a></strong><br />
 </dt>
 <dd>
-Use the given class (default: URxvt) as default application class
+Use the given class as default application class
-when reading resources.  Specify --with-res-class=Rxvt to replace
+when reading resources. Specify --with-res-class=Rxvt to replace
 rxvt.
 </dd>
 <p></p>
-<dt><strong><a name="item__2d_2denable_2dutmp">--enable-utmp</a></strong><br />
+<dt><strong><a name="item_utmp">--enable-utmp (default: on)</a></strong><br />
 </dt>
 <dd>
 Write user and tty to utmp file (used by programs like <em>w</em>) at
 start of rxvt execution and delete information when rxvt exits.
 </dd>
 <p></p>
-<dt><strong><a name="item__2d_2denable_2dwtmp">--enable-wtmp</a></strong><br />
+<dt><strong><a name="item_wtmp">--enable-wtmp (default: on)</a></strong><br />
 </dt>
 <dd>
 Write user and tty to wtmp file (used by programs like <em>last</em>) at
 start of rxvt execution and write logout when rxvt exits.  This
 option requires --enable-utmp to also be specified.
 </dd>
 <p></p>
-<dt><strong><a name="item__2d_2denable_2dlastlog">--enable-lastlog</a></strong><br />
+<dt><strong><a name="item_lastlog">--enable-lastlog (default: on)</a></strong><br />
 </dt>
 <dd>
 Write user and tty to lastlog file (used by programs like
 <em>lastlogin</em>) at start of rxvt execution.  This option requires
 --enable-utmp to also be specified.
 </dd>
 <p></p>
-<dt><strong><a name="item__2d_2denable_2dxpm_2dbackground">--enable-xpm-background</a></strong><br />
+<dt><strong><a name="item_background">--enable-xpm-background (default: on)</a></strong><br />
 </dt>
 <dd>
 Add support for XPM background pixmaps.
 </dd>
 <p></p>
-<dt><strong><a name="item__2d_2denable_2dtransparency">--enable-transparency</a></strong><br />
+<dt><strong><a name="item_transparency">--enable-transparency (default: on)</a></strong><br />
 </dt>
 <dd>
 Add support for inheriting parent backgrounds thus giving a fake
 transparency to the term.
 </dd>
 <p></p>
-<dt><strong><a name="item__2d_2denable_2dfading">--enable-fading</a></strong><br />
+<dt><strong><a name="item_fading">--enable-fading (default: on)</a></strong><br />
 </dt>
-<dd>
-Add support for fading the text when focus is lost.
-</dd>
+<dd>
-<p></p>
+Add support for fading the text when focus is lost (requires <code>--enable-transparency</code>).
-<dt><strong><a name="item__2d_2denable_2dtinting">--enable-tinting</a></strong><br />
-</dt>
-<dd>
+</dd>
-Add support for tinting of transparent backgrounds.
+<p></p>
+<dt><strong><a name="item_tinting">--enable-tinting (default: on)</a></strong><br />
+</dt>
-</dd>
+<dd>
-<p></p>
+Add support for tinting of transparent backgrounds (requires <code>--enable-transparency</code>).
-<dt><strong><a name="item__2d_2denable_2dmenubar">--enable-menubar</a></strong><br />
-</dt>
-<dd>
+</dd>
-Add support for our menu bar system (this interacts badly with
-dynamic locale switching currently).
-</dd>
 <p></p>
-<dt><strong><a name="item__2d_2denable_2drxvt_2dscroll">--enable-rxvt-scroll</a></strong><br />
+<dt><strong><a name="item_scroll">--enable-rxvt-scroll (default: on)</a></strong><br />
 </dt>
 <dd>
 Add support for the original rxvt scrollbar.
 </dd>
 <p></p>
-<dt><strong><a name="item__2d_2denable_2dnext_2dscroll">--enable-next-scroll</a></strong><br />
+<dt><strong>--enable-next-scroll (default: on)</strong><br />
 </dt>
 <dd>
 Add support for a NeXT-like scrollbar.
 </dd>
 <p></p>
-<dt><strong><a name="item__2d_2denable_2dxterm_2dscroll">--enable-xterm-scroll</a></strong><br />
+<dt><strong>--enable-xterm-scroll (default: on)</strong><br />
 </dt>
 <dd>
 Add support for an Xterm-like scrollbar.
 </dd>
 <p></p>
-<dt><strong><a name="item__2d_2denable_2dplain_2dscroll">--enable-plain-scroll</a></strong><br />
+<dt><strong>--enable-plain-scroll (default: on)</strong><br />
 </dt>
 <dd>
 Add support for a very unobtrusive, plain-looking scrollbar that
 is the favourite of the rxvt-unicode author, having used it for
 many years.
 </dd>
 <p></p>
-<dt><strong><a name="item__2d_2denable_2dhalf_2dshadow">--enable-half-shadow</a></strong><br />
-</dt>
-<dd>
-Make shadows on the scrollbar only half the normal width &amp; height.
-only applicable to rxvt scrollbars.
-</dd>
-<p></p>
-<dt><strong><a name="item__2d_2denable_2dttygid">--enable-ttygid</a></strong><br />
+<dt><strong><a name="item_ttygid">--enable-ttygid (default: off)</a></strong><br />
 </dt>
 <dd>
 Change tty device setting to group ``tty'' - only use this if
 your system uses this type of security.
 </dd>
 <p></p>
 <dt><strong><a name="item__2d_2ddisable_2dbackspace_2dkey">--disable-backspace-key</a></strong><br />
 </dt>
 <dd>
-Disable any handling of the backspace key by us - let the X server
+Removes any handling of the backspace key by us - let the X server do it.
+</dd>
+<p></p>
+<dt><strong><a name="item__2d_2ddisable_2ddelete_2dkey">--disable-delete-key</a></strong><br />
+</dt>
+<dd>
+Removes any handling of the delete key by us - let the X server
 do it.
 </dd>
 <p></p>
-<dt><strong><a name="item__2d_2ddisable_2ddelete_2dkey">--disable-delete-key</a></strong><br />
-</dt>
-<dd>
-Disable any handling of the delete key by us - let the X server
-do it.
-</dd>
-<p></p>
 <dt><strong><a name="item__2d_2ddisable_2dresources">--disable-resources</a></strong><br />
 </dt>
 <dd>
-Remove all resources checking.
+Removes any support for resource checking.
-</dd>
-<p></p>
-<dt><strong><a name="item__2d_2denable_2dxgetdefault">--enable-xgetdefault</a></strong><br />
-</dt>
-<dd>
-Make resources checking via <code>XGetDefault()</code> instead of our small
-version which only checks ~/.Xdefaults, or if that doesn't exist then
-~/.Xresources.
-</dd>
-<dd>
-<p>Please note that nowadays, things like XIM will automatically pull in and
-use the full X resource manager, so the overhead of using it might be very
-small, if nonexistant.</p>
-</dd>
-<p></p>
-<dt><strong><a name="item__2d_2denable_2dstrings">--enable-strings</a></strong><br />
-</dt>
-<dd>
-Add support for our possibly faster <code>memset()</code> 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).
 </dd>
 <p></p>
 <dt><strong><a name="item__2d_2ddisable_2dswapscreen">--disable-swapscreen</a></strong><br />
 </dt>
 <dd>
-Remove support for swap screen.
+Remove support for secondary/swap screen.
 </dd>
 <p></p>
-<dt><strong><a name="item__2d_2denable_2dfrills">--enable-frills</a></strong><br />
+<dt><strong><a name="item_frills">--enable-frills (default: on)</a></strong><br />
 </dt>
 <dd>
 Add support for many small features that are not essential but nice to
 have. Normally you want this, but for very small binaries you may want to
 disable this.
 </dd>
 <dd>
-<p>A non-exhaustive list of features enabled by <a href="#item__2d_2denable_2dfrills"><code>--enable-frills</code></a> (possibly
+<p>A non-exhaustive list of features enabled by <code>--enable-frills</code> (possibly
 in combination with other switches) is:</p>
 </dd>
 <dd>
 <pre>
   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)</pre>
+</dd>
+<dd>
+<p>It also enabled some non-essential features otherwise disabled, such as:</p>
+</dd>
+<dd>
+<pre>
+  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</pre>
-  cursor blinking and underline cursor
-  -embed and -pty-fd options</pre>
 </dd>
 <p></p>
-<dt><strong><a name="item__2d_2denable_2diso14755">--enable-iso14755</a></strong><br />
+<dt><strong><a name="item_iso14755">--enable-iso14755 (default: on)</a></strong><br />
 </dt>
 <dd>
 Enable extended ISO 14755 support (see rxvt(1), or
 <em>doc/rxvt.1.txt</em>). Basic support (section 5.1) is enabled by
-<a href="#item__2d_2denable_2dfrills"><code>--enable-frills</code></a>, while support for 5.2, 5.3 and 5.4 is enabled with
+<code>--enable-frills</code>, while support for 5.2, 5.3 and 5.4 is enabled with
 this switch.
 </dd>
 <p></p>
-<dt><strong><a name="item__2d_2denable_2dkeepscrolling">--enable-keepscrolling</a></strong><br />
+<dt><strong><a name="item_keepscrolling">--enable-keepscrolling (default: on)</a></strong><br />
 </dt>
 <dd>
 Add support for continual scrolling of the display when you hold
 the mouse button down on a scrollbar arrow.
 </dd>
 <p></p>
-<dt><strong><a name="item__2d_2denable_2dmousewheel">--enable-mousewheel</a></strong><br />
+<dt><strong><a name="item_mousewheel">--enable-mousewheel (default: on)</a></strong><br />
 </dt>
 <dd>
 Add support for scrolling via mouse wheel or buttons 4 &amp; 5.
 </dd>
 <p></p>
-<dt><strong><a name="item__2d_2denable_2dslipwheeling">--enable-slipwheeling</a></strong><br />
+<dt><strong><a name="item_slipwheeling">--enable-slipwheeling (default: on)</a></strong><br />
 </dt>
 <dd>
 Add support for continual scrolling (using the mouse wheel as an
 accelerator) while the control key is held down.  This option
 requires --enable-mousewheel to also be specified.
 </dt>
 <dd>
 Remove support for mouse selection style like that of xterm.
 </dd>
 <p></p>
-<dt><strong><a name="item__2d_2denable_2ddmalloc">--enable-dmalloc</a></strong><br />
+<dt><strong><a name="item_dmalloc">--enable-dmalloc (default: off)</a></strong><br />
 </dt>
 <dd>
 Use Gray Watson's malloc - which is good for debugging See
 <a href="http://www.letters.com/dmalloc/">http://www.letters.com/dmalloc/</a> for details If you use either this or the
 next option, you may need to edit src/Makefile after compiling to point
 <dd>
 <p>You can only use either this option and the following (should
 you use either) .</p>
 </dd>
 <p></p>
-<dt><strong><a name="item__2d_2denable_2ddlmalloc">--enable-dlmalloc</a></strong><br />
+<dt><strong><a name="item_dlmalloc">--enable-dlmalloc (default: off)</a></strong><br />
 </dt>
 <dd>
 Use Doug Lea's malloc - which is good for a production version
 See <a href="http://g.oswego.edu/dl/html/malloc.html">http://g.oswego.edu/dl/html/malloc.html</a> for details.
 </dd>
 <p></p>
-<dt><strong><a name="item__2d_2denable_2dsmart_2dresize">--enable-smart-resize</a></strong><br />
+<dt><strong><a name="item_resize">--enable-smart-resize (default: on)</a></strong><br />
 </dt>
 <dd>
-Add smart growth/shrink behaviour when changing font size via from hot
+Add smart growth/shrink behaviour when changing font size via hot
-keys. This should keep in a fixed position the rxvt corner which is
+keys. This should keep the window corner which is closest to a corner of
-closest to a corner of the screen.
+the screen in a fixed position.
 </dd>
 <p></p>
-<dt><strong><a name="item__2d_2denable_2dpointer_2dblank">--enable-pointer-blank</a></strong><br />
+<dt><strong><a name="item_blank">--enable-pointer-blank (default: on)</a></strong><br />
 </dt>
 <dd>
 Add support to have the pointer disappear when typing or inactive.
 </dd>
 <p></p>
-<dt><strong><a name="item__2d_2dwith_2dname_3dname">--with-name=NAME</a></strong><br />
+<dt><strong><a name="item_perl">--enable-perl (default: on)</a></strong><br />
 </dt>
+<dd>
+Enable an embedded perl interpreter. See the <strong>rxvtperl(3)</strong>
+manpage (<em>doc/rxvtperl.txt</em>) for more info on this feature, or the files
+in <em>src/perl-ext/</em> for the extensions that are installed by default. The
+perl interpreter that is used can be specified via the <code>PERL</code> environment
+variable when running configure.
-<dd>
+</dd>
+<p></p>
+<dt><strong>--with-name=NAME (default: urxvt)</strong><br />
+</dt>
+<dd>
-Set the basename for the installed binaries (default: <code>urxvt</code>, resulting
+Set the basename for the installed binaries, resulting
 in <code>urxvt</code>, <code>urxvtd</code> etc.). Specify <code>--with-name=rxvt</code> to replace with
 <code>rxvt</code>.
 </dd>
 <p></p>
-<dt><strong><a name="item__2d_2dwith_2dterm_3dname">--with-term=NAME</a></strong><br />
+<dt><strong>--with-term=NAME (default: rxvt-unicode)</strong><br />
 </dt>
 <dd>
-Change the environmental variable for the terminal to NAME (default
+Change the environmental variable for the terminal to NAME.
-<code>rxvt-unicode</code>)
 </dd>
 <p></p>
 <dt><strong><a name="item__2d_2dwith_2dterminfo_3dpath">--with-terminfo=PATH</a></strong><br />
 </dt>
 <dd>

Diff Legend

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

Comparing rxvt-unicode/doc/rxvt.7.html (file contents): Revision 1.20 by root, Thu Jun 30 14:00:49 2005 UTC vs. Revision 1.54 by root, Tue Jan 31 00:25:16 2006 UTC

Diff Legend

Comparing rxvt-unicode/doc/rxvt.7.html (file contents):
Revision 1.20 by root, Thu Jun 30 14:00:49 2005 UTC vs.
Revision 1.54 by root, Tue Jan 31 00:25:16 2006 UTC