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

Comparing rxvt-unicode/doc/rxvt.1.html (file contents):
Revision 1.61 by root, Mon Jul 17 19:20:29 2006 UTC vs.
Revision 1.62 by root, Mon Aug 7 16:17:30 2006 UTC

 <p>rxvt-unicode (ouR XVT, unicode) - (a VT102 emulator for the X window system)</p>
 <p>
 </p>
 <hr />
 <h1><a name="synopsis">SYNOPSIS</a></h1>
-<p><strong>urxvt</strong> [options] [-e command [ args ]]</p>
+<p><strong>rxvt</strong> [options] [-e command [ args ]]</p>
 <p>
 </p>
 <hr />
 <h1><a name="description">DESCRIPTION</a></h1>
-<p><strong>rxvt-unicode</strong>, version <strong>7.8</strong>, is a colour vt102 terminal
+<p><strong>rxvt-unicode</strong>, version <strong>7.9</strong>, is a colour vt102 terminal
 emulator intended as an <em>xterm</em>(1) replacement for users who do not
 require features such as Tektronix 4014 emulation and toolkit-style
 configurability. As a result, <strong>rxvt-unicode</strong> uses much less swap space --
 a significant advantage on a machine serving many X sessions.</p>
 <p>
 </p>
 <hr />
 <h1><a name="frequently_asked_questions">FREQUENTLY ASKED QUESTIONS</a></h1>
-<p>See <code>urxvt(7)</code> (try <code>man 7 urxvt</code>) for a list of
+<p>See <code>rxvt(7)</code> (try <code>man 7 rxvt</code>) for a list of
 frequently asked questions and answer to them and some common
 problems. That document is also accessible 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>
 world. Being a terminal emulator, however, some things are very difficult,
 especially cursive scripts such as arabic, vertically written scripts
 like mongolian or scripts requiring extremely complex combining rules,
 like tibetan or devenagari. Don't expect pretty output when using these
 scripts. Most other scripts, latin, cyrillic, kanji, thai etc. should work
-fine, though. A somewhat difficult case are left-to-right scripts, such
+fine, though. A somewhat difficult case are right-to-left scripts, such
 as hebrew: <strong>rxvt-unicode</strong> adopts the view that bidirectional algorithms
 belong into the application, not the terminal emulator (too many things --
 such as cursor-movement while editing -- break otherwise), but that might
 change.</p>
 <p>If you are looking for a terminal that supports more exotic scripts, let
-me recommend <code>mlterm</code>, which is a very userfriendly, lean and clean
+me recommend <code>mlterm</code>, which is a very user friendly, lean and clean
 terminal emulator. In fact, the reason rxvt-unicode was born was solely
 because the author couldn't get <code>mlterm</code> to use one font for latin1 and
 another for japanese.</p>
 <p>Therefore another design rationale was the use of multiple fonts to
 display characters: The idea of a single unicode font which many other
 programs force onto its users never made sense to me: You should be able
 to choose any font for any script freely.</p>
 <p>Apart from that, rxvt-unicode is also much better internationalised than
 its predecessor, supports things such as XFT and ISO 14755 that are handy
-in i18n-environments, is faster, and has a lot less bugs than the original
+in i18n-environments, is faster, and has a lot bugs less than the original
 rxvt. This all in addition to dozens of other small improvements.</p>
 <p>It is still faithfully following the original rxvt idea of being lean
 and nice on resources: for example, you can still configure rxvt-unicode
 without most of its features to get a lean binary. It also comes with
 a client/daemon pair that lets you open any number of terminal windows
 from within a single process, which makes startup time very fast and
-drastically reduces memory usage. See <code>urxvtd(1)</code> (daemon) and
+drastically reduces memory usage. See <code>rxvtd(1)</code> (daemon) and
-<code>urxvtc(1)</code> (client).</p>
+<code>rxvtc(1)</code> (client).</p>
 <p>It also makes technical information about escape sequences (which have
-been extended) easier accessible: see <code>urxvt(7)</code> for technical
+been extended) more accessible: see <code>rxvt(7)</code> for technical
 reference documentation (escape sequences etc.).</p>
 <p>
 </p>
 <hr />
 <h1><a name="options">OPTIONS</a></h1>
-<p>The <strong>urxvt</strong> options (mostly a subset of <em>xterm</em>'s) are listed
+<p>The <strong>rxvt</strong> options (mostly a subset of <em>xterm</em>'s) are listed
 below. In keeping with the smaller-is-better philosophy, options may be
 eliminated or default values chosen at compile-time, so options and
 defaults listed may not accurately reflect the version installed on
-your system. `urxvt -h' gives a list of major compile-time options on
+your system. `rxvt -h' gives a list of major compile-time options on
 the <em>Options</em> line. Option descriptions may be prefixed with which
 compile option each is dependent upon. e.g. `Compile <em>XIM</em>:' requires
-<em>XIM</em> on the <em>Options</em> line. Note: `urxvt -help' gives a list of all
+<em>XIM</em> on the <em>Options</em> line. Note: `rxvt -help' gives a list of all
 command-line options compiled into your version.</p>
-<p>Note that <strong>urxvt</strong> permits the resource name to be used as a
+<p>Note that <strong>rxvt</strong> permits the resource name to be used as a
 long-option (--/++ option) so the potential command-line options are
-far greater than those listed. For example: `urxvt --loginShell --color1
+far greater than those listed. For example: `rxvt --loginShell --color1
 Orange'.</p>
 <p>The following options are available:</p>
 <dl>
 <dt><strong><a name="item__2dhelp_2c__2d_2dhelp"><strong>-help</strong>, <strong>--help</strong></a></strong>
 <p>Turn on/off inheriting parent window's pixmap. Alternative form is
 <strong>-tr</strong>; resource <strong>inheritPixmap</strong>.</p>
 </dd>
 <dd>
 <p><em>Please note that transparency of any kind if completely unsupported by
-the author. Don't bug him with installation questions!</em></p>
+the author. Don't bug him with installation questions! Read the FAQ (man 7
+rxvt)!</em></p>
 </dd>
 </li>
 <dt><strong><a name="item__2dfade_number"><strong>-fade</strong> <em>number</em></a></strong>
 <dd>
 used to brighten or darken the image in addition to tinting it; resource
 <em>tintColor</em>. Example:</p>
 </dd>
 <dd>
 <pre>
-   urxvt -tr -tint blue -sh 40</pre>
+   rxvt -tr -tint blue -sh 40</pre>
 </dd>
 </li>
 <dt><strong><a name="item__2dsh"><strong>-sh</strong></a></strong>
 <dd>
 with <code>x:</code>. To specify an XFT-font, you need to prefix it with <code>xft:</code>,
 e.g.:</p>
 </dd>
 <dd>
 <pre>
-   urxvt -fn &quot;xft:Bitstream Vera Sans Mono:pixelsize=15&quot;
+   rxvt -fn &quot;xft:Bitstream Vera Sans Mono:pixelsize=15&quot;
-   urxvt -fn &quot;9x15bold,xft:Bitstream Vera Sans Mono&quot;</pre>
+   rxvt -fn &quot;9x15bold,xft:Bitstream Vera Sans Mono&quot;</pre>
 </dd>
 <dd>
 <p>See also the question ``How does rxvt-unicode choose fonts?'' in the FAQ
-section of urxvt(7).</p>
+section of rxvt(7).</p>
 </dd>
 </li>
 <dt><strong><a name="item__2dfb_fontlist"><strong>-fb</strong> <em>fontlist</em></a></strong>
 <dd>
 </dd>
 </li>
 <dt><strong><a name="item__2de_command__5barguments_5d"><strong>-e</strong> <em>command [arguments]</em></a></strong>
 <dd>
-<p>Run the command with its command-line arguments in the <strong>urxvt</strong>
+<p>Run the command with its command-line arguments in the <strong>rxvt</strong>
 window; also sets the window title and icon name to be the basename of
 the program being executed if neither <em>-title</em> (<em>-T</em>) nor <em>-n</em> are
 given on the command line. If this option is used, it must be the last
 on the command-line. If there is no <strong>-e</strong> option then the default is to
 run the program specified by the <strong>SHELL</strong> environment variable or,
 <p>Please note that you must specify a program with arguments. If you want to
 run shell commands, you have to specify the shell, like this:</p>
 </dd>
 <dd>
 <pre>
-  urxvt -e sh -c &quot;shell commands&quot;</pre>
+  rxvt -e sh -c &quot;shell commands&quot;</pre>
 </dd>
 </li>
 <dt><strong><a name="item__2dtitle_text"><strong>-title</strong> <em>text</em></a></strong>
 <dd>
 </dd>
 </li>
 <dt><strong><a name="item__2dhold_7c_2bhold"><strong>-hold</strong>|<strong>+hold</strong></a></strong>
 <dd>
-<p>Turn on/off hold window after exit support. If enabled, urxvt
+<p>Turn on/off hold window after exit support. If enabled, rxvt
 will not immediately destroy its window when the program executed within
 it exits. Instead, it will wait till it is being killed or closed by the
 user; resource <strong>hold</strong>.</p>
 </dd>
 </li>
 </dd>
 </li>
 <dt><strong><a name="item__2dembed_windowid"><strong>-embed</strong> <em>windowid</em></a></strong>
 <dd>
-<p>Tells urxvt to embed its windows into an already-existing window,
+<p>Tells rxvt to embed its windows into an already-existing window,
 which enables applications to easily embed a terminal.</p>
 </dd>
 <dd>
-<p>Right now, urxvt will first unmap/map the specified window, so it
+<p>Right now, rxvt will first unmap/map the specified window, so it
-shouldn't be a top-level window. urxvt will also reconfigure it
+shouldn't be a top-level window. rxvt will also reconfigure it
 quite a bit, so don't expect it to keep some specific state. It's best to
-create an extra subwindow for urxvt and leave it alone.</p>
+create an extra subwindow for rxvt and leave it alone.</p>
-</dd>
-<dd>
+</dd>
+<dd>
-<p>The window will not be destroyed when urxvt exits.</p>
+<p>The window will not be destroyed when rxvt exits.</p>
-</dd>
-<dd>
+</dd>
+<dd>
-<p>It might be useful to know that urxvt will not close file
+<p>It might be useful to know that rxvt will not close file
 descriptors passed to it (except for stdin/out/err, of course), so you
 can use file descriptors to communicate with the programs within the
-terminal. This works regardless of wether the <code>-embed</code> option was used or
+terminal. This works regardless of whether the <code>-embed</code> option was used or
 not.</p>
 </dd>
 <dd>
 <p>Here is a short Gtk2-perl snippet that illustrates how this option can be
 used (a longer example is in <em>doc/embed</em>):</p>
 <dd>
 <pre>
    my $rxvt = new Gtk2::Socket;
    $rxvt-&gt;signal_connect_after (realize =&gt; sub {
       my $xid = $_[0]-&gt;window-&gt;get_xid;
-      system &quot;urxvt -embed $xid &amp;&quot;;
+      system &quot;rxvt -embed $xid &amp;&quot;;
    });</pre>
 </dd>
 </li>
 <dt><strong><a name="item__2dpty_2dfd_file_descriptor"><strong>-pty-fd</strong> <em>file descriptor</em></a></strong>
 <dd>
-<p>Tells urxvt NOT to execute any commands or create a new pty/tty
+<p>Tells rxvt NOT to execute any commands or create a new pty/tty
-pair but instead use the given filehandle as the tty master. This is
+pair but instead use the given file descriptor as the tty master. This is
-useful if you want to drive urxvt as a generic terminal emulator
+useful if you want to drive rxvt as a generic terminal emulator
 without having to run a program within it.</p>
 </dd>
 <dd>
-<p>If this switch is given, urxvt will not create any utmp/wtmp
+<p>If this switch is given, rxvt will not create any utmp/wtmp
 entries and will not tinker with pty/tty permissions - you have to do that
 yourself if you want that.</p>
 </dd>
 <dd>
 <p>As an extremely special case, specifying <code>-1</code> will completely suppress
 </dd>
 <dd>
 <pre>
    my $pty = new IO::Pty;
    fcntl $pty, F_SETFD, 0; # clear close-on-exec
-   system &quot;urxvt -pty-fd &quot; . (fileno $pty) . &quot;&amp;&quot;;
+   system &quot;rxvt -pty-fd &quot; . (fileno $pty) . &quot;&amp;&quot;;
    close $pty;</pre>
 </dd>
 <dd>
 <pre>
    # now communicate with rxvt
 </dl>
 <p>
 </p>
 <hr />
 <h1><a name="resources__available_also_as_longoptions_">RESOURCES (available also as long-options)</a></h1>
-<p>Note: `urxvt --help' gives a list of all resources (long
+<p>Note: `rxvt --help' gives a list of all resources (long
 options) compiled into your version.</p>
 <p>You can set and change the resources using X11 tools like <strong>xrdb</strong>. Many
 distribution do also load settings from the <strong>~/.Xresources</strong> file when X
-starts. urxvt will consult the following files/resources in order,
+starts. rxvt will consult the following files/resources in order,
 with later settings overwriting earlier ones:</p>
 <pre>
   1. system-wide app-defaults file, either locale-dependent OR global
   2. app-defaults file in $XAPPLRESDIR
   3. RESOURCE_MANAGER property on root-window OR $HOME/.Xdefaults
   4. SCREEN_RESOURCES for the current screen
   5. $XENVIRONMENT file OR $HOME/.Xdefaults-&lt;nodename&gt;</pre>
-<p>Note that when reading X resources, <strong>urxvt</strong> recognizes two class
+<p>Note that when reading X resources, <strong>rxvt</strong> recognizes two class
 names: <strong>Rxvt</strong> and <strong>URxvt</strong>. The class name <strong>Rxvt</strong> allows resources
-common to both <strong>urxvt</strong> and the original <em>rxvt</em> to be easily
+common to both <strong>rxvt</strong> and the original <em>rxvt</em> to be easily
 configured, while the class name <strong>URxvt</strong> allows resources unique to
-<strong>urxvt</strong>, to be shared between different <strong>urxvt</strong>
+<strong>rxvt</strong>, to be shared between different <strong>rxvt</strong>
 configurations. If no resources are specified, suitable defaults will
 be used. Command-line arguments can be used to override resource
 settings. The following resources are supported (you might want to
-check the <code>urxvtperl(3)</code> manpage for additional settings by perl
+check the <code>rxvtperl(3)</code> manpage for additional settings by perl
 extensions not documented here):</p>
 <dl>
 <dt><strong><a name="item_depth_3a_bitdepth"><strong>depth:</strong> <em>bitdepth</em></a></strong>
 <dd>
 3=yellow, 4=blue, 5=magenta, 6=cyan, 7=white, but the actual colour
 names used are listed in the <strong>COLORS AND GRAPHICS</strong> section.</p>
 </dd>
 <dd>
 <p>Colours higher than 15 cannot be set using resources (yet), but can be
-changed using an escape command (see urxvt(7)).</p>
+changed using an escape command (see rxvt(7)).</p>
 </dd>
 <dd>
 <p>Colours 16-79 form a standard 4x4x4 colour cube (the same as xterm with
 88 colour support). Colours 80-87 are evenly spaces grey steps.</p>
 </dd>
 <dt><strong><a name="item_intensitystyles_3a_boolean"><strong>intensityStyles:</strong> <em>boolean</em></a></strong>
 <dd>
 <p>When font styles are not enabled, or this option is enabled (<strong>True</strong>,
 option <strong>-is</strong>, the default), bold and italic font styles imply high
-intensity foreground/backround colours. Disabling this option (<strong>False</strong>,
+intensity foreground/background colours. Disabling this option (<strong>False</strong>,
 option <strong>+is</strong>) disables this behaviour, the high intensity colours are not
 reachable.</p>
 </dd>
 </li>
 <dt><strong><a name="item_selectstyle_3a_mode"><strong>selectstyle:</strong> <em>mode</em></a></strong>
 <pre>
    URxvt.print-pipe: cat &gt; $(TMPDIR=$HOME mktemp urxvt.XXXXXX)</pre>
 </dd>
 <dd>
 <p>This creates a new file in your home directory with the screen contents
-everytime you hit <code>Print</code>.</p>
+every time you hit <code>Print</code>.</p>
 </dd>
 </li>
 <dt><strong><a name="item_scrollbar_3a_boolean"><strong>scrollBar:</strong> <em>boolean</em></a></strong>
 <dd>
 <dt><strong><a name="item_scrollwithbuffer_3a_boolean"><strong>scrollWithBuffer:</strong> <em>boolean</em></a></strong>
 <dd>
 <p><strong>True</strong>: scroll with scrollback buffer when tty receives new lines (and
 <strong>scrollTtyOutput</strong> is False); option <strong>-sw</strong>. <strong>False</strong>: do not scroll
-with scrollback buffer when tty recieves new lines; option <strong>+sw</strong>.</p>
+with scrollback buffer when tty receives new lines; option <strong>+sw</strong>.</p>
 </dd>
 </li>
 <dt><strong><a name="item_scrollttykeypress_3a_boolean"><strong>scrollTtyKeypress:</strong> <em>boolean</em></a></strong>
 <dd>
 <p>The characters used as delimiters for double-click word selection
 (whitespace delimiting is added automatically if resource is given).</p>
 </dd>
 <dd>
 <p>When the selection extension is in use (the default if compiled in, see
-the <code>urxvtperl(3)</code> manpage), a suitable regex using these characters
+the <code>rxvtperl(3)</code> manpage), a suitable regex using these characters
 will be created (if the resource exists, otherwise, no regex will be
 created). In this mode, characters outside ISO-8859-1 can be used.</p>
 </dd>
 <dd>
 <p>When the selection extension is not used, only ISO-8859-1 characters can
 <dd>
 <p>Specify the font-set used for XIM styles <code>OverTheSpot</code> or
 <code>OffTheSpot</code>. It must be a standard X font set (XLFD patterns separated
 by commas), i.e. it's not in the same format as the other font lists used
-in urxvt. The default will be set-up to chose *any* suitable found
+in rxvt. The default will be set-up to chose *any* suitable found
 found, preferably one or two pixels differing in size to the base font.
 option <strong>-imfont</strong>.</p>
 </dd>
 </li>
 <dt><strong><a name="item_tripleclickwords_3a_boolean"><strong>tripleclickwords:</strong> <em>boolean</em></a></strong>
 </dd>
 </li>
 <dt><strong><a name="item_hold_3a_boolean"><strong>hold</strong>: <em>boolean</em></a></strong>
 <dd>
-<p>Turn on/off hold window after exit support. If enabled, urxvt
+<p>Turn on/off hold window after exit support. If enabled, rxvt
 will not immediately destroy its window when the program executed within
 it exits. Instead, it will wait till it is being killed or closed by the
 user.</p>
 </dd>
 </li>
 can start or end with whitespace.</p>
 </dd>
 <dd>
 <p>Please note that you need to double the <code>\</code> in resource files, as
 Xlib itself does its own de-escaping (you can use <code>\033</code> instead of
-<code>\e</code> (and so on), which will work with both Xt and urxvt's own
+<code>\e</code> (and so on), which will work with both Xt and rxvt's own
 processing).</p>
 </dd>
 <dd>
 <p>You can define a range of keysyms in one shot by providing a <em>string</em>
-with pattern <strong>list/PREFIX/MIDDLE/SUFFIX</strong>, where the delimeter `/'
+with pattern <strong>list/PREFIX/MIDDLE/SUFFIX</strong>, where the delimiter `/'
 should be a character not used by the strings.</p>
 </dd>
 <dd>
 <p>Its usage can be demonstrated by an example:</p>
 </dd>
   URxvt.keysym.Meta-Control-0x62:    \033&lt;M-C-b&gt;
   URxvt.keysym.Meta-Control-0x63:    \033&lt;M-C-c&gt;</pre>
 </dd>
 <dd>
 <p>If <em>string</em> takes the form of <code>command:STRING</code>, the specified <strong>STRING</strong>
-is interpreted and executed as urxvt's control sequence. For
+is interpreted and executed as rxvt's control sequence. For
 example the following means ``change the current locale to <code>zh_CN.GBK</code>
 when Control-Meta-c is being pressed'':</p>
 </dd>
 <dd>
 <pre>
   URxvt.keysym.M-C-c: command:\033]701;zh_CN.GBK\007</pre>
 </dd>
 <dd>
 <p>If <em>string</em> takes the form <code>perl:STRING</code>, then the specified <strong>STRING</strong>
-is passed to the <code>on_keyboard_command</code> perl handler. See the <code>urxvtperl(3)</code>
+is passed to the <code>on_keyboard_command</code> perl handler. See the <code>rxvtperl(3)</code>
 manpage. For example, the <em>selection</em> extension (activated via
-<code>urxvt -pe selection</code>) listens for <code>selection:rot13</code> events:</p>
+<code>rxvt -pe selection</code>) listens for <code>selection:rot13</code> events:</p>
 </dd>
 <dd>
 <pre>
   URxvt.keysym.M-C-c: perl:selection:rot13</pre>
 </dd>
 definitions for <code>Meta-a</code>, <code>Shift-a</code> and so on, unless some of those are defined
 mappings themselves.</p>
 </dd>
 <dd>
 <p>Unfortunately, this will override built-in key mappings. For example
-if you overwrite the <code>Insert</code> key you will disable urxvt's
+if you overwrite the <code>Insert</code> key you will disable rxvt's
 <code>Shift-Insert</code> mapping. To re-enable that, you can poke ``holes'' into the
 user-defined keymap using the <code>builtin:</code> replacement:</p>
 </dd>
 <dd>
 <pre>
 <pre>
   URxvt.keysym.M-C-1: command:\033]50;suxuseuro\007
   URxvt.keysym.M-C-2: command:\033]50;9x15bold\007</pre>
 </dd>
 <dd>
-<p>Other things are possible, e.g. resizing (see <code>urxvt(7)</code> for more
+<p>Other things are possible, e.g. resizing (see <code>rxvt(7)</code> for more
 info):</p>
 </dd>
 <dd>
 <pre>
   URxvt.keysym.M-C-3: command:\033[8;25;80t
 <code>selection</code>.</p>
 </dd>
 <dd>
 <p>Extension names can also be followed by an argument in angle brackets
 (e.g.  <code>searchable-scrollback&lt;M-s&gt;</code>, which binds the hotkey for
-searchable scorllback to Alt/Meta-s). Mentioning the same extension
+searchable scrollback to Alt/Meta-s). Mentioning the same extension
 multiple times with different arguments will pass multiple arguments to
 the extension.</p>
 </dd>
 <dd>
 <p>Each extension is looked up in the library directories, loaded if
 </li>
 <dt><strong><a name="item_perl_2deval_3a_string"><strong>perl-eval</strong>: <em>string</em></a></strong>
 <dd>
 <p>Perl code to be evaluated when all extensions have been registered. See
-the <code>urxvtperl(3)</code> manpage. Due to security reasons, this resource
+the <code>rxvtperl(3)</code> manpage. Due to security reasons, this resource
 will be ignored when running setuid/setgid.</p>
 </dd>
 </li>
 <dt><strong><a name="item_perl_2dlib_3a_path"><strong>perl-lib</strong>: <em>path</em></a></strong>
 <dd>
 <p>Colon-separated list of additional directories that hold extension
 scripts. When looking for extensions specified by the <code>perl</code> resource,
-urxvt will first look in these directories and then in
+rxvt will first look in these directories and then in
-<em>/usr/local/lib/urxvt/perl/</em>. Due to security reasons, this resource
+<em>/opt/rxvt/lib/urxvt/perl/</em>. Due to security reasons, this resource
 will be ignored when running setuid/setgid.</p>
 </dd>
 <dd>
-<p>See the <code>urxvtperl(3)</code> manpage.</p>
+<p>See the <code>rxvtperl(3)</code> manpage.</p>
 </dd>
 </li>
 <dt><strong><a name="item_selection_2epattern_2didx_3a_perl_2dregex"><strong>selection.pattern-<em>idx</em> </strong>&gt;: <em>perl-regex</em></a></strong>
 <dd>
-<p>Additional selection patterns, see the <code>urxvtperl(3)</code> manpage for
+<p>Additional selection patterns, see the <code>rxvtperl(3)</code> manpage for
 details.</p>
 </dd>
 </li>
 <dt><strong><a name="item_selection_2dautotransform_2eidx_3a_perl_2dtransfor"><strong>selection-autotransform.<em>idx</em> </strong>&gt;: <em>perl-transform</em></a></strong>
 <dd>
-<p>Selection auto-transform patterns, see the <code>urxvtperl(3)</code> manpage
+<p>Selection auto-transform patterns, see the <code>rxvtperl(3)</code> manpage
 for details.</p>
 </dd>
 </li>
 <dt><strong><a name="item_searchable_2dscrollback_3a_keysym"><strong>searchable-scrollback:</strong> <em>keysym</em></a></strong>
 </dl>
 <p>
 </p>
 <hr />
 <h1><a name="the_scrollbar">THE SCROLLBAR</a></h1>
-<p>Lines of text that scroll off the top of the <strong>urxvt</strong> window
+<p>Lines of text that scroll off the top of the <strong>rxvt</strong> window
 (resource: <strong>saveLines</strong>) and can be scrolled back using the scrollbar
-or by keystrokes. The normal <strong>urxvt</strong> scrollbar has arrows and
+or by keystrokes. The normal <strong>rxvt</strong> scrollbar has arrows and
 its behaviour is fairly intuitive. The <strong>xterm-scrollbar</strong> is without
 arrows and its behaviour mimics that of <em>xterm</em></p>
 <p>Scroll down with <strong>Button1</strong> (<strong>xterm-scrollbar</strong>) or <strong>Shift-Next</strong>.
 Scroll up with <strong>Button3</strong> (<strong>xterm-scrollbar</strong>) or <strong>Shift-Prior</strong>.
 Continuous scroll with <strong>Button2</strong>.</p>
 </dd>
 </li>
 <dt><strong><a name="item_insertion_3a"><strong>Insertion</strong>:</a></strong>
 <dd>
-<p>Pressing and releasing the Middle mouse button in an <strong>urxvt</strong>
+<p>Pressing and releasing the Middle mouse button in an <strong>rxvt</strong>
 window causes the value of the PRIMARY selection (or CLIPBOARD with the
 Meta modifier) to be inserted as if it had been typed on the keyboard.</p>
 </dd>
 <dd>
 <p>Pressing <strong>Shift-Insert</strong> causes the value of the PRIMARY selection to be
 both scenario A and B of ISO 14755, including part 5.2.</p>
 <p>
 </p>
 <hr />
 <h1><a name="login_stamp">LOGIN STAMP</a></h1>
-<p><strong>urxvt</strong> tries to write an entry into the <em>utmp</em>(5) file so that
+<p><strong>rxvt</strong> tries to write an entry into the <em>utmp</em>(5) file so that
 it can be seen via the <em>who(1)</em> command, and can accept messages.  To
-allow this feature, <strong>urxvt</strong> may need to be installed setuid root
+allow this feature, <strong>rxvt</strong> may need to be installed setuid root
 on some systems or setgid to root or to some other group on others.</p>
 <p>
 </p>
 <hr />
 <h1><a name="colors_and_graphics">COLORS AND GRAPHICS</a></h1>
 <p>In addition to the default foreground and background colours,
-<strong>urxvt</strong> can display up to 16 colours (8 ANSI colours plus
+<strong>rxvt</strong> can display up to 16 colours (8 ANSI colours plus
 high-intensity bold/blink versions of the same). Here is a list of the
 colours with their names.</p>
 <table>
 <tr><td>color0</td><td>(black)</td><td>= Black</td></tr>
 <tr><td>color1</td><td>(red)</td><td>= Red3</td></tr>
 <tr><td>background</td><td></td><td>= White</td></tr>
 </table><p>It is also possible to specify the colour values of <strong>foreground</strong>,
 <strong>background</strong>, <strong>cursorColor</strong>, <strong>cursorColor2</strong>, <strong>colorBD</strong>, <strong>colorUL</strong> as
 a number 0-15, as a convenient shorthand to reference the colour name of
 color0-color15.</p>
-<p>In addition to the colours defined above, urxvt offers an
+<p>In addition to the colours defined above, rxvt offers an
 additional 72 colours. The first 64 of those (with indices 16 to 79)
 consist of a 4*4*4 RGB colour cube (i.e. <em>index = r * 16 + g * 4 + b +
 16</em>), followed by 8 additional shades of gray (with indices 80 to 87).</p>
 <p>Together, all those colours implement the 88 colour xterm colours. Only
 the first 16 can be changed using resources currently, the rest can only
 <p>Note that <strong>-rv</strong> (<strong>``reverseVideo: True''</strong>) simulates reverse video by
 always swapping the foreground/background colours. This is in contrast to
 <em>xterm</em>(1) where the colours are only swapped if they have not otherwise
 been specified. For example,</p>
 <dl>
-<dt><strong><a name="item_urxvt__2dfg_black__2dbg_white__2drv"><strong>urxvt -fg Black -bg White -rv</strong></a></strong>
+<dt><strong><a name="item_rxvt__2dfg_black__2dbg_white__2drv"><strong>rxvt -fg Black -bg White -rv</strong></a></strong>
 <dd>
 <p>would yield White on Black, while on <em>xterm</em>(1) it would yield Black
 on White.</p>
 </dd>
 your X-server uses ARGB pixel layout, as X is far from just supporting
 ARGB visuals out of the box, and rxvt-unicode just fudges around.</p>
 <p>For example, the following selects an almost completely transparent red
 background, and an almost opaque pink foreground:</p>
 <pre>
-   urxvt -depth 32 -bg rgba:0000/0000/0000/2222 -fg &quot;[e]pink&quot;</pre>
+   rxvt -depth 32 -bg rgba:0000/0000/0000/2222 -fg &quot;[e]pink&quot;</pre>
 <p><em>Please note that transparency of any kind if completely unsupported by
 the author. Don't bug him with installation questions!</em></p>
 <p>
 </p>
 <hr />
 <h1><a name="environment">ENVIRONMENT</a></h1>
-<p><strong>urxvt</strong> sets and/or uses the following environment variables:</p>
+<p><strong>rxvt</strong> sets and/or uses the following environment variables:</p>
 <dl>
 <dt><strong><a name="item_term"><strong>TERM</strong></a></strong>
 <dd>
 <p>Normally set to <code>rxvt-unicode</code>, unless overwritten at configure time, via
-resources or on the commandline.</p>
+resources or on the command line.</p>
 </dd>
 </li>
 <dt><strong><a name="item_colorterm"><strong>COLORTERM</strong></a></strong>
 <dd>
-<p>Either <code>rxvt</code>, <code>rxvt-xpm</code>, depending on wether urxvt was
+<p>Either <code>rxvt</code>, <code>rxvt-xpm</code>, depending on whether rxvt was
 compiled with XPM support, and optionally with the added extension
 <code>-mono</code> to indicate that rxvt-unicode runs on a monochrome screen.</p>
 </dd>
 </li>
 <dt><strong><a name="item_colorfgbg"><strong>COLORFGBG</strong></a></strong>
 <dd>
 <p>Set to a string of the form <code>fg;bg</code> or <code>fg;xpm;bg</code>, where <code>fg</code> is
 the colour code used as default foreground/text colour (or the string
 <code>default</code> to indicate that the default-colour escape sequence is to be
 used), <code>bg</code> is the colour code used as default background colour (or the
-string <code>default</code>), and <code>xpm</code> is the string <code>default</code> if urxvt
+string <code>default</code>), and <code>xpm</code> is the string <code>default</code> if rxvt
 was compiled with XPM support. Libraries like <code>ncurses</code> and <code>slang</code> can
 (and do) use this information to optimize screen output.</p>
 </dd>
 </li>
 <dt><strong><a name="item_windowid"><strong>WINDOWID</strong></a></strong>
 <dd>
-<p>Set to the (decimal) X Window ID of the urxvt window (the toplevel
+<p>Set to the (decimal) X Window ID of the rxvt window (the toplevel
 window, which usually has subwindows for the scrollbar, the terminal
 window and so on).</p>
 </dd>
 </li>
 <dt><strong><a name="item_terminfo"><strong>TERMINFO</strong></a></strong>
 <dd>
-<p>Set to the terminfo directory iff urxvt was configured with
+<p>Set to the terminfo directory iff rxvt was configured with
 <code>--with-terminfo=PATH</code>.</p>
 </dd>
 </li>
 <dt><strong><a name="item_display"><strong>DISPLAY</strong></a></strong>
 <dd>
-<p>Used by urxvt to connect to the display and set to the correct
+<p>Used by rxvt to connect to the display and set to the correct
 display in its child processes.</p>
 </dd>
 </li>
 <dt><strong><a name="item_shell"><strong>SHELL</strong></a></strong>
 </dd>
 </li>
 <dt><strong><a name="item_rxvt_socket"><strong>RXVT_SOCKET</strong></a></strong>
 <dd>
-<p>The unix domain socket path used by <code>urxvtc(1)</code> and
+<p>The unix domain socket path used by <code>rxvtc(1)</code> and
-urxvtd(1).</p>
+rxvtd(1).</p>
 </dd>
 <dd>
 <p>Default <em>$HOME/.rxvt-unicode-<em>&lt;nodename </em></em> &gt;&gt;&gt;.</p>
 </dd>
 </li>
 </li>
 <dt><strong><a name="item_xenvironment"><strong>XENVIRONMENT</strong></a></strong>
 <dd>
 <p>If set and accessible, gives the name of a X resource file to be loaded by
-urxvt.</p>
+rxvt.</p>
 </dd>
 </li>
 </dl>
 <p>
 </p>
 </dl>
 <p>
 </p>
 <hr />
 <h1><a name="see_also">SEE ALSO</a></h1>
-<p>urxvt(7), urxvtc(1), urxvtd(1), xterm(1), sh(1), resize(1), X(1), pty(4), tty(4), <code>utmp(5)</code></p>
+<p>rxvt(7), rxvtc(1), rxvtd(1), xterm(1), sh(1), resize(1), X(1), pty(4), tty(4), <code>utmp(5)</code></p>
 <p>
 </p>
 <hr />
 <h1><a name="current_project_coordinator">CURRENT PROJECT COORDINATOR</a></h1>
 <dl>

Diff Legend

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

Comparing rxvt-unicode/doc/rxvt.1.html (file contents): Revision 1.61 by root, Mon Jul 17 19:20:29 2006 UTC vs. Revision 1.62 by root, Mon Aug 7 16:17:30 2006 UTC

Diff Legend

Comparing rxvt-unicode/doc/rxvt.1.html (file contents):
Revision 1.61 by root, Mon Jul 17 19:20:29 2006 UTC vs.
Revision 1.62 by root, Mon Aug 7 16:17:30 2006 UTC