If you only want to disable specific features, you first have to
identify which perl extension is responsible. For this, read the
- section PREPACKAGED EXTENSIONS in the rxvtperl(3) manpage. For
+ section PREPACKAGED EXTENSIONS in the urxvtperl(3) manpage. For
example, to disable the selection-popup and option-popup, specify
this perl-ext-common resource:
How do I know which rxvt-unicode version I'm using?
The version number is displayed with the usage (-h). Also the escape
sequence "ESC [ 8 n" sets the window title to the version number.
- When using the rxvtc client, the version displayed is that of the
+ When using the urxvtc client, the version displayed is that of the
daemon.
I am using Debian GNU/Linux and have a problem...
Most likely it's the empty definition for "enacs=". Just replace it
by "enacs=\E[0@" and try again.
- "bash"'s readline does not work correctly under rxvt.
+ "bash"'s readline does not work correctly under urxvt.
I need a termcap file entry.
One reason you might want this is that some distributions or
operating systems still compile some programs using the
In that case, select a font of your taste and add it to the font
list, e.g.:
- rxvt -fn basefont,font2,font3...
+ urxvt -fn basefont,font2,font3...
When rxvt-unicode sees a character, it will first look at the base
font. If the base font does not contain the character, it will go to
some editors prematurely may leave the mouse in mouse report mode.
I've heard that tcsh may use mouse reporting unless it otherwise
specified. A quick check is to see if cut/paste works when the Alt
- or Shift keys are depressed. See rxvt(7)
+ or Shift keys are depressed.
What's with this bold/blink stuff?
If no bold colour is set via "colorBD:", bold will invert text using
URxvt.color7: #e1dddd
URxvt.color15: #e1dddd
- How can I start rxvtd in a race-free way?
- Try "rxvtd -f -o", which tells rxvtd to open the display, create the
- listening socket and then fork.
+ How can I start urxvtd in a race-free way?
+ Try "urxvtd -f -o", which tells urxvtd to open the display, create
+ the listening socket and then fork.
What's with the strange Backspace/Delete key behaviour?
Assuming that the physical Backspace key corresponds to the
# use Backspace = ^H
$ stty erase ^H
- $ rxvt
+ $ urxvt
# use Backspace = ^?
$ stty erase ^?
- $ rxvt
+ $ urxvt
- Toggle with "ESC [ 36 h" / "ESC [ 36 l" as documented in rxvt(7).
+ Toggle with "ESC [ 36 h" / "ESC [ 36 l".
For an existing rxvt-unicode:
option you can use the `keysym' resource to alter the keystrings
associated with keysyms.
- Here's an example for a URxvt session started using "rxvt -name
+ Here's an example for a URxvt session started using "urxvt -name
URxvt"
URxvt.keysym.Home: \033[1~
sgr modes 90..97 and 100..107
--enable-iso14755 (default: on)
- Enable extended ISO 14755 support (see rxvt(1), or doc/rxvt.1.txt).
+ Enable extended ISO 14755 support (see urxvt(1), or doc/rxvt.1.txt).
Basic support (section 5.1) is enabled by "--enable-frills", while
support for 5.2, 5.3 and 5.4 is enabled with this switch.
Add support to have the pointer disappear when typing or inactive.
--enable-perl (default: off)
- Enable an embedded perl interpreter. See the rxvtperl(3) manpage
+ Enable an embedded perl interpreter. See the urxvtperl(3) manpage
(doc/rxvtperl.txt) for more info on this feature, or the files in
src/perl-ext/ for the extensions that are installed by default. The
perl interpreter that is used can be specified via the "PERL"
</p>
<hr />
<h1><a name="synopsis">SYNOPSIS</a></h1>
-<p><strong>rxvt</strong> [options] [-e command [ args ]]</p>
+<p><strong>urxvt</strong> [options] [-e command [ args ]]</p>
<p>
</p>
<hr />
</p>
<hr />
<h1><a name="frequently_asked_questions">FREQUENTLY ASKED QUESTIONS</a></h1>
-<p>See <code>rxvt(7)</code> (try <code>man 7 rxvt</code>) for a list of
+<p>See <code>urxvt(7)</code> (try <code>man 7 urxvt</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>
without most of it's 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>rxvtd(1)</code> (daemon) and
-<code>rxvtc(1)</code> (client).</p>
+drastically reduces memory usage. See <code>urxvtd(1)</code> (daemon) and
+<code>urxvtc(1)</code> (client).</p>
<p>It also makes technical information about escape sequences (which have
-been extended) easier accessible: see <code>rxvt(7)</code> for technical
+been extended) easier accessible: see <code>urxvt(7)</code> for technical
reference documentation (escape sequences etc.).</p>
<p>
</p>
<hr />
<h1><a name="options">OPTIONS</a></h1>
-<p>The <strong>rxvt</strong> options (mostly a subset of <em>xterm</em>'s) are listed
+<p>The <strong>urxvt</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. `rxvt -h' gives a list of major compile-time options on
+your system. `urxvt -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: `rxvt -help' gives a list of all
+<em>XIM</em> on the <em>Options</em> line. Note: `urxvt -help' gives a list of all
command-line options compiled into your version.</p>
-<p>Note that <strong>rxvt</strong> permits the resource name to be used as a
+<p>Note that <strong>urxvt</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: `rxvt --loginShell --color1
+far greater than those listed. For example: `urxvt --loginShell --color1
Orange'.</p>
<p>The following options are available:</p>
<dl>
</dd>
<dd>
<pre>
- rxvt -tr -tint blue -sh 40</pre>
+ urxvt -tr -tint blue -sh 40</pre>
</dd>
<p></p>
<dt><strong><a name="item__2dsh"><strong>-sh</strong></a></strong><br />
</dt>
<dd>
Select the fonts to be used. This is a comma separated list of font names
-that are used in turn when trying to display Unicode characters. The
+that are checked in order when trying to find glyphs for characters. The
first font defines the cell size for characters; other fonts might be
smaller, but not (in general) larger. A (hopefully) reasonable default
font list is always appended to it. See resource <strong>font</strong> for more details.
</dd>
<dd>
<pre>
- rxvt -fn "xft:Bitstream Vera Sans Mono:pixelsize=15"
- rxvt -fn "9x15bold,xft:Bitstream Vera Sans Mono"</pre>
+ urxvt -fn "xft:Bitstream Vera Sans Mono:pixelsize=15"
+ urxvt -fn "9x15bold,xft:Bitstream Vera Sans Mono"</pre>
</dd>
<dd>
<p>See also the question ``How does rxvt-unicode choose fonts?'' in the FAQ
-section of rxvt(7).</p>
+section of urxvt(7).</p>
</dd>
<p></p>
<dt><strong><a name="item__2dfb_fontlist"><strong>-fb</strong> <em>fontlist</em></a></strong><br />
<dt><strong><a name="item__2de_command__5barguments_5d"><strong>-e</strong> <em>command [arguments]</em></a></strong><br />
</dt>
<dd>
-Run the command with its command-line arguments in the <strong>rxvt</strong>
+Run the command with its command-line arguments in the <strong>urxvt</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
</dd>
<dd>
<pre>
- rxvt -e sh -c "shell commands"</pre>
+ urxvt -e sh -c "shell commands"</pre>
</dd>
<p></p>
<dt><strong><a name="item__2dtitle_text"><strong>-title</strong> <em>text</em></a></strong><br />
<dt><strong><a name="item__2dhold_7c_2bhold"><strong>-hold</strong>|<strong>+hold</strong></a></strong><br />
</dt>
<dd>
-Turn on/off hold window after exit support. If enabled, rxvt
+Turn on/off hold window after exit support. If enabled, urxvt
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>.
<dt><strong><a name="item__2dembed_windowid"><strong>-embed</strong> <em>windowid</em></a></strong><br />
</dt>
<dd>
-Tells rxvt to embed it's windows into an already-existing window,
+Tells urxvt to embed it's windows into an already-existing window,
which enables applications to easily embed a terminal.
</dd>
<dd>
-<p>Right now, rxvt will first unmap/map the specified window, so it
-shouldn't be a top-level window. rxvt will also reconfigure it
+<p>Right now, urxvt will first unmap/map the specified window, so it
+shouldn't be a top-level window. urxvt 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 rxvt and leave it alone.</p>
+create an extra subwindow for urxvt and leave it alone.</p>
</dd>
<dd>
-<p>The window will not be destroyed when rxvt exits.</p>
+<p>The window will not be destroyed when urxvt exits.</p>
</dd>
<dd>
-<p>It might be useful to know that rxvt will not close file
+<p>It might be useful to know that urxvt 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
my $rxvt = new Gtk2::Socket;
$rxvt->signal_connect_after (realize => sub {
my $xid = $_[0]->window->get_xid;
- system "rxvt -embed $xid &";
+ system "urxvt -embed $xid &";
});</pre>
</dd>
<p></p>
<dt><strong><a name="item__2dpty_2dfd_file_descriptor"><strong>-pty-fd</strong> <em>file descriptor</em></a></strong><br />
</dt>
<dd>
-Tells rxvt NOT to execute any commands or create a new pty/tty
+Tells urxvt NOT to execute any commands or create a new pty/tty
pair but instead use the given filehandle as the tty master. This is
-useful if you want to drive rxvt as a generic terminal emulator
+useful if you want to drive urxvt as a generic terminal emulator
without having to run a program within it.
</dd>
<dd>
-<p>If this switch is given, rxvt will not create any utmp/wtmp
+<p>If this switch is given, urxvt 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>
<pre>
my $pty = new IO::Pty;
fcntl $pty, F_SETFD, 0; # clear close-on-exec
- system "rxvt -pty-fd " . (fileno $pty) . "&";
+ system "urxvt -pty-fd " . (fileno $pty) . "&";
close $pty;</pre>
</dd>
<dd>
</p>
<hr />
<h1><a name="resources__available_also_as_longoptions_">RESOURCES (available also as long-options)</a></h1>
-<p>Note: `rxvt --help' gives a list of all resources (long
+<p>Note: `urxvt --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. rxvt will consult the following files/resources in order,
+starts. urxvt 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
3. RESOURCE_MANAGER property on root-window OR $HOME/.Xdefaults
4. SCREEN_RESOURCES for the current screen
5. $XENVIRONMENT file OR $HOME/.Xdefaults-<nodename></pre>
-<p>Note that when reading X resources, <strong>rxvt</strong> recognizes two class
+<p>Note that when reading X resources, <strong>urxvt</strong> recognizes two class
names: <strong>Rxvt</strong> and <strong>URxvt</strong>. The class name <strong>Rxvt</strong> allows resources
-common to both <strong>rxvt</strong> and the original <em>rxvt</em> to be easily
+common to both <strong>urxvt</strong> and the original <em>rxvt</em> to be easily
configured, while the class name <strong>URxvt</strong> allows resources unique to
-<strong>rxvt</strong>, to be shared between different <strong>rxvt</strong>
+<strong>urxvt</strong>, to be shared between different <strong>urxvt</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>rxvtperl(3)</code> manpage for additional settings by perl
+check the <code>urxvtperl(3)</code> manpage for additional settings by perl
extensions not documented here):</p>
<dl>
<dt><strong><a name="item_geometry_3a_geom"><strong>geometry:</strong> <em>geom</em></a></strong><br />
</dd>
<dd>
<p>Colours higher than 15 cannot be set using resources (yet), but can be
-changed using an escape command (see rxvt(7)).</p>
+changed using an escape command (see urxvt(7)).</p>
</dd>
<dd>
<p>Colours 16-79 form a standard 4x4x4 colour cube (the same as xterm with
<dt><strong><a name="item_font_3a_fontlist"><strong>font:</strong> <em>fontlist</em></a></strong><br />
</dt>
<dd>
-Select the fonts to be used. This is a comma separated list of font
-names that are used in turn when trying to display Unicode characters.
-The first font defines the cell size for characters; other fonts might
-be smaller, but not larger. A reasonable default font list is always
-appended to it; option <strong>-fn</strong>.
+Select the fonts to be used. This is a comma separated list of font names
+that are checked in order when trying to find glyphs for characters. The
+first font defines the cell size for characters; other fonts might be
+smaller, but not (in general) larger. A (hopefully) reasonable default
+font list is always appended to it; option <strong>-fn</strong>.
</dd>
<dd>
<p>Each font can either be a standard X11 core font (XLFD) name, with
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 rxvt. The default will be set-up to chose *any* suitable found
+in urxvt. 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>.
</dd>
<dt><strong><a name="item_hold_3a_bool"><strong>hold</strong>: <em>bool</em></a></strong><br />
</dt>
<dd>
-Turn on/off hold window after exit support. If enabled, rxvt
+Turn on/off hold window after exit support. If enabled, urxvt
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.
<dd>
<p>Please note that you need to double the <code>\</code> in resource files, as
Xlib itself does it's own de-escaping (you can use <code>\033</code> instead of
-<code>\e</code> (and so on), which will work with both Xt and rxvt's own
+<code>\e</code> (and so on), which will work with both Xt and urxvt's own
processing).</p>
</dd>
<dd>
</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 rxvt's control sequence. For
+is interpreted and executed as urxvt'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>
<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>rxvtperl(3)</code>
+is passed to the <code>on_keyboard_command</code> perl handler. See the <code>urxvtperl(3)</code>
manpage. For example, the <em>selection</em> extension (activated via
-<code>rxvt -pe selection</code>) listens for <code>selection:rot13</code> events:</p>
+<code>urxvt -pe selection</code>) listens for <code>selection:rot13</code> events:</p>
</dd>
<dd>
<pre>
</dd>
<dd>
<p>Unfortunately, this will override built-in key mappings. For example
-if you overwrite the <code>Insert</code> key you will disable rxvt's
+if you overwrite the <code>Insert</code> key you will disable urxvt'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>
URxvt.keysym.M-C-2: command:\033]50;9x15bold\007</pre>
</dd>
<dd>
-<p>Other things are possible, e.g. resizing (see <code>rxvt(7)</code> for more
+<p>Other things are possible, e.g. resizing (see <code>urxvt(7)</code> for more
info):</p>
</dd>
<dd>
</dt>
<dd>
Perl code to be evaluated when all extensions have been registered. See
-the <code>rxvtperl(3)</code> manpage. Due to security reasons, this resource
+the <code>urxvtperl(3)</code> manpage. Due to security reasons, this resource
will be ignored when running setuid/setgid.
</dd>
<p></p>
<dd>
Colon-separated list of additional directories that hold extension
scripts. When looking for extensions specified by the <code>perl</code> resource,
-rxvt will first look in these directories and then in
-<em>/opt/rxvt/lib/urxvt/perl/</em>. Due to security reasons, this resource
+urxvt will first look in these directories and then in
+<em>/usr/local/lib/urxvt/perl/</em>. Due to security reasons, this resource
will be ignored when running setuid/setgid.
</dd>
<dd>
-<p>See the <code>rxvtperl(3)</code> manpage.</p>
+<p>See the <code>urxvtperl(3)</code> manpage.</p>
</dd>
<p></p>
<dt><strong><a name="item_selection_2epattern_2didx_3a_perl_2dregex"><strong>selection.pattern-<em>idx</em> </strong>>: <em>perl-regex</em></a></strong><br />
</dt>
<dd>
-Additional selection patterns, see the <code>rxvtperl(3)</code> manpage for
+Additional selection patterns, see the <code>urxvtperl(3)</code> manpage for
details.
</dd>
<p></p>
<dt><strong><a name="item_selection_2dautotransform_2eidx_3a_perl_2dtransfor"><strong>selection-autotransform.<em>idx</em> </strong>>: <em>perl-transform</em></a></strong><br />
</dt>
<dd>
-Selection auto-transform patterns, see the <code>rxvtperl(3)</code> manpage
+Selection auto-transform patterns, see the <code>urxvtperl(3)</code> manpage
for details.
</dd>
<p></p>
</p>
<hr />
<h1><a name="the_scrollbar">THE SCROLLBAR</a></h1>
-<p>Lines of text that scroll off the top of the <strong>rxvt</strong> window
+<p>Lines of text that scroll off the top of the <strong>urxvt</strong> window
(resource: <strong>saveLines</strong>) and can be scrolled back using the scrollbar
-or by keystrokes. The normal <strong>rxvt</strong> scrollbar has arrows and
+or by keystrokes. The normal <strong>urxvt</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>.
</dt>
<dd>
Pressing and releasing the Middle mouse button (or <strong>Shift-Insert</strong>) in
-an <strong>rxvt</strong> window causes the current text selection to be
+an <strong>urxvt</strong> window causes the current text selection to be
inserted as if it had been typed on the keyboard.
</dd>
<p></p></dl>
</p>
<hr />
<h1><a name="login_stamp">LOGIN STAMP</a></h1>
-<p><strong>rxvt</strong> tries to write an entry into the <em>utmp</em>(5) file so that
+<p><strong>urxvt</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>rxvt</strong> may need to be installed setuid root
+allow this feature, <strong>urxvt</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>rxvt</strong> can display up to 16 colours (8 ANSI colours plus
+<strong>urxvt</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 <strong>rgb.txt</strong> names.</p>
<table>
<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_rxvt__2dfg_black__2dbg_white__2drv"><strong>rxvt -fg Black -bg White -rv</strong></a></strong><br />
+<dt><strong><a name="item_urxvt__2dfg_black__2dbg_white__2drv"><strong>urxvt -fg Black -bg White -rv</strong></a></strong><br />
</dt>
<dd>
would yield White on Black, while on <em>xterm</em>(1) it would yield Black
</p>
<hr />
<h1><a name="environment">ENVIRONMENT</a></h1>
-<p><strong>rxvt</strong> sets and/or uses the following environment variables:</p>
+<p><strong>urxvt</strong> sets and/or uses the following environment variables:</p>
<dl>
<dt><strong><a name="item_term"><strong>TERM</strong></a></strong><br />
</dt>
<dt><strong><a name="item_colorterm"><strong>COLORTERM</strong></a></strong><br />
</dt>
<dd>
-Either <code>rxvt</code>, <code>rxvt-xpm</code>, depending on wether rxvt was
+Either <code>rxvt</code>, <code>rxvt-xpm</code>, depending on wether urxvt was
compiled with XPM support, and optionally with the added extension
<code>-mono</code> to indicate that rxvt-unicode runs on a monochrome screen.
</dd>
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 rxvt
+string <code>default</code>), and <code>xpm</code> is the string <code>default</code> if urxvt
was compiled with XPM support. Libraries like <code>ncurses</code> and <code>slang</code> can
(and do) use this information to optimize screen output.
</dd>
<dt><strong><a name="item_windowid"><strong>WINDOWID</strong></a></strong><br />
</dt>
<dd>
-Set to the (decimal) X Window ID of the rxvt window (the toplevel
+Set to the (decimal) X Window ID of the urxvt window (the toplevel
window, which usually has subwindows for the scrollbar, the terminal
window and so on).
</dd>
<dt><strong><a name="item_terminfo"><strong>TERMINFO</strong></a></strong><br />
</dt>
<dd>
-Set to the terminfo directory iff rxvt was configured with
+Set to the terminfo directory iff urxvt was configured with
<code>--with-terminfo=PATH</code>.
</dd>
<p></p>
<dt><strong><a name="item_display"><strong>DISPLAY</strong></a></strong><br />
</dt>
<dd>
-Used by rxvt to connect to the display and set to the correct
+Used by urxvt to connect to the display and set to the correct
display in it's child processes.
</dd>
<p></p>
<dt><strong><a name="item_rxvtpath"><strong>RXVTPATH</strong></a></strong><br />
</dt>
<dd>
-The path where rxvt looks for support files such as menu and xpm
+The path where urxvt looks for support files such as menu and xpm
files.
</dd>
<p></p>
<dt><strong><a name="item_rxvt_socket"><strong>RXVT_SOCKET</strong></a></strong><br />
</dt>
<dd>
-The unix domain socket path used by <code>rxvtc(1)</code> and
-rxvtd(1).
+The unix domain socket path used by <code>urxvtc(1)</code> and
+urxvtd(1).
</dd>
<dd>
<p>Default <em>$HOME/.rxvt-unicode-<em><nodename </em></em> >>>.</p>
</dt>
<dd>
If set and accessible, gives the name of a X resource file to be loaded by
-rxvt.
+urxvt.
</dd>
<p></p></dl>
<p>
</p>
<hr />
<h1><a name="see_also">SEE ALSO</a></h1>
-<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>urxvt(7), urxvtc(1), urxvtd(1), xterm(1), sh(1), resize(1), X(1), pty(4), tty(4), <code>utmp(5)</code></p>
<p>
</p>
<hr />
.\" ========================================================================
.\"
.IX Title "rxvt 1"
-.TH rxvt 1 "2006-01-12" "7.0" "RXVT-UNICODE"
+.TH rxvt 1 "2006-01-13" "7.0" "RXVT-UNICODE"
.SH "NAME"
rxvt\-unicode (ouR XVT, unicode) \- (a VT102 emulator for the X window system)
.SH "SYNOPSIS"
.IP "\fB\-fn\fR \fIfontlist\fR" 4
.IX Item "-fn fontlist"
Select the fonts to be used. This is a comma separated list of font names
-that are used in turn when trying to display Unicode characters. The
+that are checked in order when trying to find glyphs for characters. The
first font defines the cell size for characters; other fonts might be
smaller, but not (in general) larger. A (hopefully) reasonable default
font list is always appended to it. See resource \fBfont\fR for more details.
\&\fB\s-1PATH\s0\fR environment variables.
.IP "\fBfont:\fR \fIfontlist\fR" 4
.IX Item "font: fontlist"
-Select the fonts to be used. This is a comma separated list of font
-names that are used in turn when trying to display Unicode characters.
-The first font defines the cell size for characters; other fonts might
-be smaller, but not larger. A reasonable default font list is always
-appended to it; option \fB\-fn\fR.
+Select the fonts to be used. This is a comma separated list of font names
+that are checked in order when trying to find glyphs for characters. The
+first font defines the cell size for characters; other fonts might be
+smaller, but not (in general) larger. A (hopefully) reasonable default
+font list is always appended to it; option \fB\-fn\fR.
.Sp
Each font can either be a standard X11 core font (\s-1XLFD\s0) name, with
optional prefix \f(CW\*(C`x:\*(C'\fR or a Xft font (Compile \fIxft\fR), prefixed with \f(CW\*(C`xft:\*(C'\fR.
=item B<-fn> I<fontlist>
Select the fonts to be used. This is a comma separated list of font names
-that are used in turn when trying to display Unicode characters. The
+that are checked in order when trying to find glyphs for characters. The
first font defines the cell size for characters; other fonts might be
smaller, but not (in general) larger. A (hopefully) reasonable default
font list is always appended to it. See resource B<font> for more details.
=item B<font:> I<fontlist>
-Select the fonts to be used. This is a comma separated list of font
-names that are used in turn when trying to display Unicode characters.
-The first font defines the cell size for characters; other fonts might
-be smaller, but not larger. A reasonable default font list is always
-appended to it; option B<-fn>.
+Select the fonts to be used. This is a comma separated list of font names
+that are checked in order when trying to find glyphs for characters. The
+first font defines the cell size for characters; other fonts might be
+smaller, but not (in general) larger. A (hopefully) reasonable default
+font list is always appended to it; option B<-fn>.
Each font can either be a standard X11 core font (XLFD) name, with
optional prefix C<x:> or a Xft font (Compile I<xft>), prefixed with C<xft:>.
system)
SYNOPSIS
- rxvt [options] [-e command [ args ]]
+ urxvt [options] [-e command [ args ]]
DESCRIPTION
rxvt-unicode, version 7.0, is a colour vt102 terminal emulator intended
advantage on a machine serving many X sessions.
FREQUENTLY ASKED QUESTIONS
- See rxvt(7) (try "man 7 rxvt") 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
+ See urxvt(7) (try "man 7 urxvt") 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
<http://cvs.schmorp.de/browse/*checkout*/rxvt-unicode/doc/rxvt.7.html>.
RXVT-UNICODE VS. RXVT
without most of it's 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 rxvtd(1) (daemon) and rxvtc(1)
+ drastically reduces memory usage. See urxvtd(1) (daemon) and urxvtc(1)
(client).
It also makes technical information about escape sequences (which have
- been extended) easier accessible: see rxvt(7) for technical reference
+ been extended) easier accessible: see urxvt(7) for technical reference
documentation (escape sequences etc.).
OPTIONS
- The rxvt options (mostly a subset of *xterm*'s) are listed below. In
+ The urxvt options (mostly a subset of *xterm*'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. `rxvt
+ may not accurately reflect the version installed on your system. `urxvt
-h' gives a list of major compile-time options on the *Options* line.
Option descriptions may be prefixed with which compile option each is
dependent upon. e.g. `Compile *XIM*:' requires *XIM* on the *Options*
- line. Note: `rxvt -help' gives a list of all command-line options
+ line. Note: `urxvt -help' gives a list of all command-line options
compiled into your version.
- Note that rxvt permits the resource name to be used as a long-option
+ Note that urxvt 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: `rxvt --loginShell --color1 Orange'.
+ than those listed. For example: `urxvt --loginShell --color1 Orange'.
The following options are available:
be used to brighten or darken the image in addition to tinting it;
resource *tintColor*. Example:
- rxvt -tr -tint blue -sh 40
+ urxvt -tr -tint blue -sh 40
-sh *number* Darken (0 .. 100) or lighten (-1 .. -100) the transparent
background image in addition to tinting it (i.e. -tint must be
-fn *fontlist*
Select the fonts to be used. This is a comma separated list of font
- names that are used in turn when trying to display Unicode
+ names that are checked in order when trying to find glyphs for
characters. The first font defines the cell size for characters;
other fonts might be smaller, but not (in general) larger. A
(hopefully) reasonable default font list is always appended to it.
prefix it with "x:". To specify an XFT-font, you need to prefix it
with "xft:", e.g.:
- rxvt -fn "xft:Bitstream Vera Sans Mono:pixelsize=15"
- rxvt -fn "9x15bold,xft:Bitstream Vera Sans Mono"
+ urxvt -fn "xft:Bitstream Vera Sans Mono:pixelsize=15"
+ urxvt -fn "9x15bold,xft:Bitstream Vera Sans Mono"
See also the question "How does rxvt-unicode choose fonts?" in the
- FAQ section of rxvt(7).
+ FAQ section of urxvt(7).
-fb *fontlist*
Compile *font-styles*: The bold font list to use when bold
resource termName.
-e *command [arguments]*
- Run the command with its command-line arguments in the rxvt window;
+ Run the command with its command-line arguments in the urxvt window;
also sets the window title and icon name to be the basename of the
program being executed if neither *-title* (*-T*) nor *-n* are given
on the command line. If this option is used, it must be the last on
want to run shell commands, you have to specify the shell, like
this:
- rxvt -e sh -c "shell commands"
+ urxvt -e sh -c "shell commands"
-title *text*
Window title (-T still respected); the default title is the basename
secondaryScroll.
-hold|+hold
- Turn on/off hold window after exit support. If enabled, rxvt will
+ Turn on/off hold window after exit support. If enabled, urxvt 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 hold.
Remap a key symbol. See resource keysym.
-embed *windowid*
- Tells rxvt to embed it's windows into an already-existing window,
+ Tells urxvt to embed it's windows into an already-existing window,
which enables applications to easily embed a terminal.
- Right now, rxvt will first unmap/map the specified window, so 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 rxvt and leave it alone.
+ Right now, urxvt will first unmap/map the specified window, so it
+ shouldn't be a top-level window. urxvt 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.
- The window will not be destroyed when rxvt exits.
+ The window will not be destroyed when urxvt exits.
- 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 "-embed" option was
- used or not.
+ It might be useful to know that urxvt 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 "-embed" option
+ was used or not.
Here is a short Gtk2-perl snippet that illustrates how this option
can be used (a longer example is in doc/embed):
my $rxvt = new Gtk2::Socket;
$rxvt->signal_connect_after (realize => sub {
my $xid = $_[0]->window->get_xid;
- system "rxvt -embed $xid &";
+ system "urxvt -embed $xid &";
});
-pty-fd *file descriptor*
- Tells rxvt NOT to execute any commands or create a new pty/tty pair
+ Tells urxvt NOT to execute any commands or create a new pty/tty pair
but instead use the given filehandle as the tty master. This is
- useful if you want to drive rxvt as a generic terminal emulator
+ useful if you want to drive urxvt as a generic terminal emulator
without having to run a program within it.
- If this switch is given, rxvt will not create any utmp/wtmp entries
+ If this switch is given, urxvt 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.
my $pty = new IO::Pty;
fcntl $pty, F_SETFD, 0; # clear close-on-exec
- system "rxvt -pty-fd " . (fileno $pty) . "&";
+ system "urxvt -pty-fd " . (fileno $pty) . "&";
close $pty;
# now communicate with rxvt
use) in this terminal instance. See resource perl-ext for details.
RESOURCES (available also as long-options)
- Note: `rxvt --help' gives a list of all resources (long options)
+ Note: `urxvt --help' gives a list of all resources (long options)
compiled into your version.
You can set and change the resources using X11 tools like xrdb. Many
distribution do also load settings from the ~/.Xresources file when X
- starts. rxvt will consult the following files/resources in order, with
+ starts. urxvt will consult the following files/resources in order, with
later settings overwriting earlier ones:
1. system-wide app-defaults file, either locale-dependent OR global
4. SCREEN_RESOURCES for the current screen
5. $XENVIRONMENT file OR $HOME/.Xdefaults-<nodename>
- Note that when reading X resources, rxvt recognizes two class names:
- Rxvt and URxvt. The class name Rxvt allows resources common to both rxvt
- and the original *rxvt* to be easily configured, while the class name
- URxvt allows resources unique to rxvt, to be shared between different
- rxvt 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 rxvtperl(3) manpage for additional settings by perl extensions not
- documented here):
+ Note that when reading X resources, urxvt recognizes two class names:
+ Rxvt and URxvt. The class name Rxvt allows resources common to both
+ urxvt and the original *rxvt* to be easily configured, while the class
+ name URxvt allows resources unique to urxvt, to be shared between
+ different urxvt 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 urxvtperl(3) manpage for additional settings by perl
+ extensions not documented here):
geometry: *geom*
Create the window with the specified X window geometry [default
section.
Colours higher than 15 cannot be set using resources (yet), but can
- be changed using an escape command (see rxvt(7)).
+ be changed using an escape command (see urxvt(7)).
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.
font: *fontlist*
Select the fonts to be used. This is a comma separated list of font
- names that are used in turn when trying to display Unicode
+ names that are checked in order when trying to find glyphs for
characters. The first font defines the cell size for characters;
- other fonts might be smaller, but not larger. A reasonable default
- font list is always appended to it; option -fn.
+ other fonts might be smaller, but not (in general) larger. A
+ (hopefully) reasonable default font list is always appended to it;
+ option -fn.
Each font can either be a standard X11 core font (XLFD) name, with
optional prefix "x:" or a Xft font (Compile *xft*), prefixed with
Specify the font-set used for XIM styles "OverTheSpot" or
"OffTheSpot". 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 rxvt. The default will be set-up to chose *any*
+ font lists used in urxvt. 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 -imfont.
instead scroll the screen up.
hold: *bool*
- Turn on/off hold window after exit support. If enabled, rxvt will
+ Turn on/off hold window after exit support. If enabled, urxvt 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.
Please note that you need to double the "\" in resource files, as
Xlib itself does it's own de-escaping (you can use "\033" instead of
- "\e" (and so on), which will work with both Xt and rxvt's own
+ "\e" (and so on), which will work with both Xt and urxvt's own
processing).
You can define a range of keysyms in one shot by providing a
URxvt.keysym.Meta-Control-0x63: \033<M-C-c>
If *string* takes the form of "command:STRING", the specified STRING
- is interpreted and executed as rxvt's control sequence. For example
+ is interpreted and executed as urxvt's control sequence. For example
the following means "change the current locale to "zh_CN.GBK" when
Control-Meta-c is being pressed":
If *string* takes the form "perl:STRING", then the specified STRING
is passed to the "on_keyboard_command" perl handler. See the
- rxvtperl(3) manpage. For example, the selection extension (activated
- via "rxvt -pe selection") listens for "selection:rot13" events:
+ urxvtperl(3) manpage. For example, the selection extension
+ (activated via "urxvt -pe selection") listens for "selection:rot13"
+ events:
URxvt.keysym.M-C-c: perl:selection:rot13
unless some of those are defined mappings themselves.
Unfortunately, this will override built-in key mappings. For example
- if you overwrite the "Insert" key you will disable rxvt's
+ if you overwrite the "Insert" key you will disable urxvt's
"Shift-Insert" mapping. To re-enable that, you can poke "holes" into
the user-defined keymap using the "builtin:" replacement:
URxvt.keysym.M-C-1: command:\033]50;suxuseuro\007
URxvt.keysym.M-C-2: command:\033]50;9x15bold\007
- Other things are possible, e.g. resizing (see rxvt(7) for more
+ Other things are possible, e.g. resizing (see urxvt(7) for more
info):
URxvt.keysym.M-C-3: command:\033[8;25;80t
perl-eval: *string*
Perl code to be evaluated when all extensions have been registered.
- See the rxvtperl(3) manpage. Due to security reasons, this resource
+ See the urxvtperl(3) manpage. Due to security reasons, this resource
will be ignored when running setuid/setgid.
perl-lib: *path*
Colon-separated list of additional directories that hold extension
scripts. When looking for extensions specified by the "perl"
- resource, rxvt will first look in these directories and then in
- /opt/rxvt/lib/urxvt/perl/. Due to security reasons, this resource
+ resource, urxvt will first look in these directories and then in
+ /usr/local/lib/urxvt/perl/. Due to security reasons, this resource
will be ignored when running setuid/setgid.
- See the rxvtperl(3) manpage.
+ See the urxvtperl(3) manpage.
selection.pattern-*idx*: *perl-regex*
- Additional selection patterns, see the rxvtperl(3) manpage for
+ Additional selection patterns, see the urxvtperl(3) manpage for
details.
selection-autotransform.*idx*: *perl-transform*
- Selection auto-transform patterns, see the rxvtperl(3) manpage for
+ Selection auto-transform patterns, see the urxvtperl(3) manpage for
details.
searchable-scrollback: *keysym*
Sets the WM_TRANSIENT_FOR property to the given window iw.
THE SCROLLBAR
- Lines of text that scroll off the top of the rxvt window (resource:
+ Lines of text that scroll off the top of the urxvt window (resource:
saveLines) and can be scrolled back using the scrollbar or by
- keystrokes. The normal rxvt scrollbar has arrows and its behaviour is
+ keystrokes. The normal urxvt scrollbar has arrows and its behaviour is
fairly intuitive. The xterm-scrollbar is without arrows and its
behaviour mimics that of *xterm*
Insertion:
Pressing and releasing the Middle mouse button (or Shift-Insert) in
- an rxvt window causes the current text selection to be inserted as
+ an urxvt window causes the current text selection to be inserted as
if it had been typed on the keyboard.
CHANGING FONTS
both scenario A and B of ISO 14755, including part 5.2.
LOGIN STAMP
- rxvt tries to write an entry into the *utmp*(5) file so that it can be
+ urxvt tries to write an entry into the *utmp*(5) file so that it can be
seen via the *who(1)* command, and can accept messages. To allow this
- feature, rxvt may need to be installed setuid root on some systems or
+ feature, urxvt may need to be installed setuid root on some systems or
setgid to root or to some other group on others.
COLORS AND GRAPHICS
- In addition to the default foreground and background colours, rxvt can
+ In addition to the default foreground and background colours, urxvt 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 rgb.txt
names.
*xterm*(1) where the colours are only swapped if they have not otherwise
been specified. For example,
- rxvt -fg Black -bg White -rv
+ urxvt -fg Black -bg White -rv
would yield White on Black, while on *xterm*(1) it would yield Black
on White.
ENVIRONMENT
- rxvt sets and/or uses the following environment variables:
+ urxvt sets and/or uses the following environment variables:
TERM
Normally set to "rxvt-unicode", unless overwritten at configure
time, via resources or on the commandline.
COLORTERM
- Either "rxvt", "rxvt-xpm", depending on wether rxvt was compiled
+ Either "rxvt", "rxvt-xpm", depending on wether urxvt was compiled
with XPM support, and optionally with the added extension "-mono" to
indicate that rxvt-unicode runs on a monochrome screen.
string "default" to indicate that the default-colour escape sequence
is to be used), "bg" is the colour code used as default background
colour (or the string "default"), and "xpm" is the string "default"
- if rxvt was compiled with XPM support. Libraries like "ncurses" and
+ if urxvt was compiled with XPM support. Libraries like "ncurses" and
"slang" can (and do) use this information to optimize screen output.
WINDOWID
- Set to the (decimal) X Window ID of the rxvt window (the toplevel
+ Set to the (decimal) X Window ID of the urxvt window (the toplevel
window, which usually has subwindows for the scrollbar, the terminal
window and so on).
TERMINFO
- Set to the terminfo directory iff rxvt was configured with
+ Set to the terminfo directory iff urxvt was configured with
"--with-terminfo=PATH".
DISPLAY
- Used by rxvt to connect to the display and set to the correct
+ Used by urxvt to connect to the display and set to the correct
display in it's child processes.
SHELL
The shell to be used for command execution, defaults to "/bin/sh".
RXVTPATH
- The path where rxvt looks for support files such as menu and xpm
+ The path where urxvt looks for support files such as menu and xpm
files.
PATH
Used in the same way as "RXVTPATH".
RXVT_SOCKET
- The unix domain socket path used by rxvtc(1) and rxvtd(1).
+ The unix domain socket path used by urxvtc(1) and urxvtd(1).
Default $HOME/.rxvt-unicode-*<nodename*.
XENVIRONMENT
If set and accessible, gives the name of a X resource file to be
- loaded by rxvt.
+ loaded by urxvt.
FILES
/usr/lib/X11/rgb.txt
Color names.
SEE ALSO
- rxvt(7), rxvtc(1), rxvtd(1), xterm(1), sh(1), resize(1), X(1), pty(4),
- tty(4), utmp(5)
+ urxvt(7), urxvtc(1), urxvtd(1), xterm(1), sh(1), resize(1), X(1),
+ pty(4), tty(4), utmp(5)
CURRENT PROJECT COORDINATOR
Project Coordinator
<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
+<strong>PREPACKAGED EXTENSIONS</strong> in the <code>urxvtperl(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>
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. When
-using the rxvtc client, the version displayed is that of the
+using the urxvtc client, the version displayed is that of the
daemon.
</dd>
<p></p>
<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><strong><a name="item_bash_27s_readline_does_not_work_correctly_under_ur"><code>bash</code>'s readline does not work correctly under urxvt.</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 />
</dt>
</dd>
<dd>
<pre>
- rxvt -fn basefont,font2,font3...</pre>
+ urxvt -fn basefont,font2,font3...</pre>
</dd>
<dd>
<p>When rxvt-unicode sees a character, it will first look at the base
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 />
URxvt.color15: #e1dddd</pre>
</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><strong><a name="item_how_can_i_start_urxvtd_in_a_race_2dfree_way_3f">How can I start urxvtd in a race-free way?</a></strong><br />
</dt>
<dd>
-Try <code>rxvtd -f -o</code>, which tells rxvtd to open the
+Try <code>urxvtd -f -o</code>, which tells urxvtd to open the
display, create the listening socket and then fork.
</dd>
<p></p>
<pre>
# use Backspace = ^H
$ stty erase ^H
- $ rxvt</pre>
+ $ urxvt</pre>
</dd>
<dd>
<pre>
# use Backspace = ^?
$ stty erase ^?
- $ rxvt</pre>
+ $ urxvt</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>
use the `keysym' resource to alter the keystrings associated with keysyms.
</dd>
<dd>
-<p>Here's an example for a URxvt session started using <code>rxvt -name URxvt</code></p>
+<p>Here's an example for a URxvt session started using <code>urxvt -name URxvt</code></p>
</dd>
<dd>
<pre>
<dt><strong><a name="item_iso14755">--enable-iso14755 (default: on)</a></strong><br />
</dt>
<dd>
-Enable extended ISO 14755 support (see rxvt(1), or
+Enable extended ISO 14755 support (see urxvt(1), or
<em>doc/rxvt.1.txt</em>). Basic support (section 5.1) is enabled by
<code>--enable-frills</code>, while support for 5.2, 5.3 and 5.4 is enabled with
this switch.
<dt><strong><a name="item_perl">--enable-perl (default: off)</a></strong><br />
</dt>
<dd>
-Enable an embedded perl interpreter. See the <strong>rxvtperl(3)</strong>
+Enable an embedded perl interpreter. See the <strong>urxvtperl(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
some editors prematurely may leave the mouse in mouse report mode. I've
heard that tcsh may use mouse reporting unless it otherwise specified. A
quick check is to see if cut/paste works when the Alt or Shift keys are
-depressed. See @@RXVT_NAME@@(7)
+depressed.
.IP "What's with this bold/blink stuff?" 4
.IX Item "What's with this bold/blink stuff?"
If no bold colour is set via \f(CW\*(C`colorBD:\*(C'\fR, bold will invert text using the
\& $ @@RXVT_NAME@@
.Ve
.Sp
-Toggle with \f(CW\*(C`ESC [ 36 h\*(C'\fR / \f(CW\*(C`ESC [ 36 l\*(C'\fR as documented in @@RXVT_NAME@@(7).
+Toggle with \f(CW\*(C`ESC [ 36 h\*(C'\fR / \f(CW\*(C`ESC [ 36 l\*(C'\fR.
.Sp
For an existing rxvt\-unicode:
.Sp
some editors prematurely may leave the mouse in mouse report mode. I've
heard that tcsh may use mouse reporting unless it otherwise specified. A
quick check is to see if cut/paste works when the Alt or Shift keys are
-depressed. See @@RXVT_NAME@@(7)
+depressed.
=item What's with this bold/blink stuff?
$ stty erase ^?
$ @@RXVT_NAME@@
-Toggle with C<ESC [ 36 h> / C<ESC [ 36 l> as documented in @@RXVT_NAME@@(7).
+Toggle with C<ESC [ 36 h> / C<ESC [ 36 l>.
For an existing rxvt-unicode:
If you only want to disable specific features, you first have to
identify which perl extension is responsible. For this, read the
- section PREPACKAGED EXTENSIONS in the rxvtperl(3) manpage. For
+ section PREPACKAGED EXTENSIONS in the urxvtperl(3) manpage. For
example, to disable the selection-popup and option-popup, specify
this perl-ext-common resource:
How do I know which rxvt-unicode version I'm using?
The version number is displayed with the usage (-h). Also the escape
sequence "ESC [ 8 n" sets the window title to the version number.
- When using the rxvtc client, the version displayed is that of the
+ When using the urxvtc client, the version displayed is that of the
daemon.
I am using Debian GNU/Linux and have a problem...
Most likely it's the empty definition for "enacs=". Just replace it
by "enacs=\E[0@" and try again.
- "bash"'s readline does not work correctly under rxvt.
+ "bash"'s readline does not work correctly under urxvt.
I need a termcap file entry.
One reason you might want this is that some distributions or
operating systems still compile some programs using the
In that case, select a font of your taste and add it to the font
list, e.g.:
- rxvt -fn basefont,font2,font3...
+ urxvt -fn basefont,font2,font3...
When rxvt-unicode sees a character, it will first look at the base
font. If the base font does not contain the character, it will go to
some editors prematurely may leave the mouse in mouse report mode.
I've heard that tcsh may use mouse reporting unless it otherwise
specified. A quick check is to see if cut/paste works when the Alt
- or Shift keys are depressed. See rxvt(7)
+ or Shift keys are depressed.
What's with this bold/blink stuff?
If no bold colour is set via "colorBD:", bold will invert text using
URxvt.color7: #e1dddd
URxvt.color15: #e1dddd
- How can I start rxvtd in a race-free way?
- Try "rxvtd -f -o", which tells rxvtd to open the display, create the
- listening socket and then fork.
+ How can I start urxvtd in a race-free way?
+ Try "urxvtd -f -o", which tells urxvtd to open the display, create
+ the listening socket and then fork.
What's with the strange Backspace/Delete key behaviour?
Assuming that the physical Backspace key corresponds to the
# use Backspace = ^H
$ stty erase ^H
- $ rxvt
+ $ urxvt
# use Backspace = ^?
$ stty erase ^?
- $ rxvt
+ $ urxvt
- Toggle with "ESC [ 36 h" / "ESC [ 36 l" as documented in rxvt(7).
+ Toggle with "ESC [ 36 h" / "ESC [ 36 l".
For an existing rxvt-unicode:
option you can use the `keysym' resource to alter the keystrings
associated with keysyms.
- Here's an example for a URxvt session started using "rxvt -name
+ Here's an example for a URxvt session started using "urxvt -name
URxvt"
URxvt.keysym.Home: \033[1~
sgr modes 90..97 and 100..107
--enable-iso14755 (default: on)
- Enable extended ISO 14755 support (see rxvt(1), or doc/rxvt.1.txt).
+ Enable extended ISO 14755 support (see urxvt(1), or doc/rxvt.1.txt).
Basic support (section 5.1) is enabled by "--enable-frills", while
support for 5.2, 5.3 and 5.4 is enabled with this switch.
Add support to have the pointer disappear when typing or inactive.
--enable-perl (default: off)
- Enable an embedded perl interpreter. See the rxvtperl(3) manpage
+ Enable an embedded perl interpreter. See the urxvtperl(3) manpage
(doc/rxvtperl.txt) for more info on this feature, or the files in
src/perl-ext/ for the extensions that are installed by default. The
perl interpreter that is used can be specified via the "PERL"
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
-<title>rxvtperl - rxvt-unicode's embedded perl interpreter</title>
+<title>urxvtperl - rxvt-unicode's embedded perl interpreter</title>
<link rev="made" href="mailto:perl-binary@plan9.de" />
</head>
</p>
<hr />
<h1><a name="name">NAME</a></h1>
-<p>rxvtperl - rxvt-unicode's embedded perl interpreter</p>
+<p>urxvtperl - rxvt-unicode's embedded perl interpreter</p>
<p>
</p>
<hr />
()
}</pre>
<pre>
- # start a rxvt using it:</pre>
+ # start a urxvt using it:</pre>
<pre>
- rxvt --perl-lib $HOME -pe grab_test</pre>
+ urxvt --perl-lib $HOME -pe grab_test</pre>
<p>
</p>
<hr />
the <code>perl</code> resource are loaded and associated with it.</p>
<p>Scripts are compiled in a 'use strict' and 'use utf8' environment, and
thus must be encoded as UTF-8.</p>
-<p>Each script will only ever be loaded once, even in rxvtd, where
+<p>Each script will only ever be loaded once, even in urxvtd, where
scripts will be shared (but not enabled) for all terminals.</p>
<p>
</p>
<hr />
<h1><a name="prepackaged_extensions">PREPACKAGED EXTENSIONS</a></h1>
<p>This section describes the extensions delivered with this release. You can
-find them in <em>/opt/rxvt/lib/urxvt/perl/</em>.</p>
+find them in <em>/usr/local/lib/urxvt/perl/</em>.</p>
<p>You can activate them like this:</p>
<pre>
- rxvt -pe <extensionname></pre>
+ urxvt -pe <extensionname></pre>
<dl>
<dt><strong><a name="item_selection">selection (enabled by default)</a></strong><br />
</dt>
</dd>
<dd>
<pre>
- URxvt.selection-autotransform.0: s/^(\\S+):(\\d+):?$/vi +$2 \\Q$1\\E\\x0d/</pre>
+ URxvt.selection-autotransform.0: s/^([^:[:space:]]+):(\\d+):?$/vi +$2 \\Q$1\\E\\x0d/</pre>
</dd>
<dd>
<p>And this example matches the same,but replaces it with vi-commands you can
</dd>
<dd>
<pre>
- URxvt.selection-autotransform.0: s/^(S+):(d+):?$/\\x1b:e \\Q$1\\E\\x0d:$2\\x0d/</pre>
+ URxvt.selection-autotransform.0: s/^([^:[:space:]]+(\\d+):?$/\\x1b:e \\Q$1\\E\\x0d:$2\\x0d/</pre>
</dd>
<dd>
<p>Of course, this can be modified to suit your needs and your editor :)</p>
<dd>
Called whenever the user presses a key combination that has a
<code>perl:string</code> action bound to it (see description of the <strong>keysym</strong>
-resource in the <code>rxvt(1)</code> manpage).
+resource in the <code>urxvt(1)</code> manpage).
+</dd>
+<p></p>
+<dt><strong><a name="item_on_x_event__24term_2c__24event">on_x_event $term, $event</a></strong><br />
+</dt>
+<dd>
+Called on every X event received on the vt window (and possibly other
+windows). Should only be used as a last resort. Most event structure
+members are not passed.
</dd>
<p></p>
<dt><strong><a name="item_on_focus_in__24term">on_focus_in $term</a></strong><br />
Mod3Mask, Mod4Mask, Mod5Mask, Button1Mask, Button2Mask, Button3Mask,
Button4Mask, Button5Mask, AnyModifier</a></strong><br />
</dt>
+<dt><strong><a name="item_urxvt_3a_3anoeventmask_2c_keypressmask_2c_keyrelea">urxvt::NoEventMask, KeyPressMask, KeyReleaseMask,
+ButtonPressMask, ButtonReleaseMask, EnterWindowMask, LeaveWindowMask,
+PointerMotionMask, PointerMotionHintMask, Button1MotionMask, Button2MotionMask,
+Button3MotionMask, Button4MotionMask, Button5MotionMask, ButtonMotionMask,
+KeymapStateMask, ExposureMask, VisibilityChangeMask, StructureNotifyMask,
+ResizeRedirectMask, SubstructureNotifyMask, SubstructureRedirectMask,
+FocusChangeMask, PropertyChangeMask, ColormapChangeMask, OwnerGrabButtonMask</a></strong><br />
+</dt>
+<dt><strong><a name="item_urxvt_3a_3akeypress_2c_keyrelease_2c_buttonpress_2">urxvt::KeyPress, KeyRelease, ButtonPress, ButtonRelease, MotionNotify,
+EnterNotify, LeaveNotify, FocusIn, FocusOut, KeymapNotify, Expose,
+GraphicsExpose, NoExpose, VisibilityNotify, CreateNotify, DestroyNotify,
+UnmapNotify, MapNotify, MapRequest, ReparentNotify, ConfigureNotify,
+ConfigureRequest, GravityNotify, ResizeRequest, CirculateNotify,
+CirculateRequest, PropertyNotify, SelectionClear, SelectionRequest,
+SelectionNotify, ColormapNotify, ClientMessage, MappingNotify</a></strong><br />
+</dt>
<dd>
Various constants for use in X calls and event processing.
</dd>
</dt>
<dd>
Destroy the terminal object (close the window, free resources
-etc.). Please note that rxvt will not exit as long as any event
+etc.). Please note that urxvt will not exit as long as any event
watchers (timers, io watchers) are still active.
</dd>
<p></p>
</dt>
<dd>
Adds a keymap translation exactly as specified via a resource. See the
-<code>keysym</code> resource in the <code>rxvt(1)</code> manpage.
+<code>keysym</code> resource in the <code>urxvt(1)</code> manpage.
</dd>
<p></p>
<dt><strong><a name="item_rstyle">$rend = $term->rstyle ([$new_rstyle])</a></strong><br />
Return the window id of the terminal window.
</dd>
<p></p>
+<dt><strong><a name="item_vt_emask_add">$term->vt_emask_add ($x_event_mask)</a></strong><br />
+</dt>
+<dd>
+Adds the specified events to the vt event mask. Useful e.g. when you want
+to receive pointer events all the times:
+</dd>
+<dd>
+<pre>
+ $term->vt_emask_add (urxvt::PointerMotionMask);</pre>
+</dd>
+<p></p>
<dt><strong><a name="item_width">$window_width = $term->width</a></strong><br />
</dt>
<dt><strong><a name="item_height">$window_height = $term->height</a></strong><br />
$word\*(C'\fR:
.Sp
.Vb 1
-\& URxvt.selection-autotransform.0: s/^(\e\eS+):(\e\ed+):?$/vi +$2 \e\eQ$1\e\eE\e\ex0d/
+\& URxvt.selection-autotransform.0: s/^([^:[:space:]]+):(\e\ed+):?$/vi +$2 \e\eQ$1\e\eE\e\ex0d/
.Ve
.Sp
And this example matches the same,but replaces it with vi-commands you can
paste directly into your (vi :) editor:
.Sp
.Vb 1
-\& URxvt.selection-autotransform.0: s/^(S+):(d+):?$/\e\ex1b:e \e\eQ$1\e\eE\e\ex0d:$2\e\ex0d/
+\& URxvt.selection-autotransform.0: s/^([^:[:space:]]+(\e\ed+):?$/\e\ex1b:e \e\eQ$1\e\eE\e\ex0d:$2\e\ex0d/
.Ve
.Sp
Of course, this can be modified to suit your needs and your editor :)
Called whenever the user presses a key combination that has a
\&\f(CW\*(C`perl:string\*(C'\fR action bound to it (see description of the \fBkeysym\fR
resource in the @@RXVT_NAME@@(1) manpage).
+.ie n .IP "on_x_event $term\fR, \f(CW$event" 4
+.el .IP "on_x_event \f(CW$term\fR, \f(CW$event\fR" 4
+.IX Item "on_x_event $term, $event"
+Called on every X event received on the vt window (and possibly other
+windows). Should only be used as a last resort. Most event structure
+members are not passed.
.ie n .IP "on_focus_in $term" 4
.el .IP "on_focus_in \f(CW$term\fR" 4
.IX Item "on_focus_in $term"
.PD 0
.IP "urxvt::ShiftMask, LockMask, ControlMask, Mod1Mask, Mod2Mask, Mod3Mask, Mod4Mask, Mod5Mask, Button1Mask, Button2Mask, Button3Mask, Button4Mask, Button5Mask, AnyModifier" 4
.IX Item "urxvt::ShiftMask, LockMask, ControlMask, Mod1Mask, Mod2Mask, Mod3Mask, Mod4Mask, Mod5Mask, Button1Mask, Button2Mask, Button3Mask, Button4Mask, Button5Mask, AnyModifier"
+.IP "urxvt::NoEventMask, KeyPressMask, KeyReleaseMask, ButtonPressMask, ButtonReleaseMask, EnterWindowMask, LeaveWindowMask, PointerMotionMask, PointerMotionHintMask, Button1MotionMask, Button2MotionMask, Button3MotionMask, Button4MotionMask, Button5MotionMask, ButtonMotionMask, KeymapStateMask, ExposureMask, VisibilityChangeMask, StructureNotifyMask, ResizeRedirectMask, SubstructureNotifyMask, SubstructureRedirectMask, FocusChangeMask, PropertyChangeMask, ColormapChangeMask, OwnerGrabButtonMask" 4
+.IX Item "urxvt::NoEventMask, KeyPressMask, KeyReleaseMask, ButtonPressMask, ButtonReleaseMask, EnterWindowMask, LeaveWindowMask, PointerMotionMask, PointerMotionHintMask, Button1MotionMask, Button2MotionMask, Button3MotionMask, Button4MotionMask, Button5MotionMask, ButtonMotionMask, KeymapStateMask, ExposureMask, VisibilityChangeMask, StructureNotifyMask, ResizeRedirectMask, SubstructureNotifyMask, SubstructureRedirectMask, FocusChangeMask, PropertyChangeMask, ColormapChangeMask, OwnerGrabButtonMask"
+.IP "urxvt::KeyPress, KeyRelease, ButtonPress, ButtonRelease, MotionNotify, EnterNotify, LeaveNotify, FocusIn, FocusOut, KeymapNotify, Expose, GraphicsExpose, NoExpose, VisibilityNotify, CreateNotify, DestroyNotify, UnmapNotify, MapNotify, MapRequest, ReparentNotify, ConfigureNotify, ConfigureRequest, GravityNotify, ResizeRequest, CirculateNotify, CirculateRequest, PropertyNotify, SelectionClear, SelectionRequest, SelectionNotify, ColormapNotify, ClientMessage, MappingNotify" 4
+.IX Item "urxvt::KeyPress, KeyRelease, ButtonPress, ButtonRelease, MotionNotify, EnterNotify, LeaveNotify, FocusIn, FocusOut, KeymapNotify, Expose, GraphicsExpose, NoExpose, VisibilityNotify, CreateNotify, DestroyNotify, UnmapNotify, MapNotify, MapRequest, ReparentNotify, ConfigureNotify, ConfigureRequest, GravityNotify, ResizeRequest, CirculateNotify, CirculateRequest, PropertyNotify, SelectionClear, SelectionRequest, SelectionNotify, ColormapNotify, ClientMessage, MappingNotify"
.PD
Various constants for use in X calls and event processing.
.Sh "\s-1RENDITION\s0"
.el .IP "$windowid = \f(CW$term\fR\->vt" 4
.IX Item "$windowid = $term->vt"
Return the window id of the terminal window.
+.IP "$term\->vt_emask_add ($x_event_mask)" 4
+.IX Item "$term->vt_emask_add ($x_event_mask)"
+Adds the specified events to the vt event mask. Useful e.g. when you want
+to receive pointer events all the times:
+.Sp
+.Vb 1
+\& $term->vt_emask_add (urxvt::PointerMotionMask);
+.Ve
.ie n .IP "$window_width = $term\->width" 4
.el .IP "$window_width = \f(CW$term\fR\->width" 4
.IX Item "$window_width = $term->width"
NAME
- rxvtperl - rxvt-unicode's embedded perl interpreter
+ urxvtperl - rxvt-unicode's embedded perl interpreter
SYNOPSIS
# create a file grab_test in $HOME:
()
}
- # start a rxvt using it:
+ # start a urxvt using it:
- rxvt --perl-lib $HOME -pe grab_test
+ urxvt --perl-lib $HOME -pe grab_test
DESCRIPTION
Everytime a terminal object gets created, extension scripts specified
Scripts are compiled in a 'use strict' and 'use utf8' environment, and
thus must be encoded as UTF-8.
- Each script will only ever be loaded once, even in rxvtd, where scripts
+ Each script will only ever be loaded once, even in urxvtd, where scripts
will be shared (but not enabled) for all terminals.
PREPACKAGED EXTENSIONS
This section describes the extensions delivered with this release. You
- can find them in /opt/rxvt/lib/urxvt/perl/.
+ can find them in /usr/local/lib/urxvt/perl/.
You can activate them like this:
- rxvt -pe <extensionname>
+ urxvt -pe <extensionname>
selection (enabled by default)
(More) intelligent selection. This extension tries to be more
"filename:number", often seen in compiler messages, into "vi
+$filename $word":
- URxvt.selection-autotransform.0: s/^(\\S+):(\\d+):?$/vi +$2 \\Q$1\\E\\x0d/
+ URxvt.selection-autotransform.0: s/^([^:[:space:]]+):(\\d+):?$/vi +$2 \\Q$1\\E\\x0d/
And this example matches the same,but replaces it with vi-commands
you can paste directly into your (vi :) editor:
- URxvt.selection-autotransform.0: s/^(S+):(d+):?$/\\x1b:e \\Q$1\\E\\x0d:$2\\x0d/
+ URxvt.selection-autotransform.0: s/^([^:[:space:]]+(\\d+):?$/\\x1b:e \\Q$1\\E\\x0d:$2\\x0d/
Of course, this can be modified to suit your needs and your editor
:)
on_keyboard_command $term, $string
Called whenever the user presses a key combination that has a
"perl:string" action bound to it (see description of the keysym
- resource in the rxvt(1) manpage).
+ resource in the urxvt(1) manpage).
+
+ on_x_event $term, $event
+ Called on every X event received on the vt window (and possibly
+ other windows). Should only be used as a last resort. Most event
+ structure members are not passed.
on_focus_in $term
Called whenever the window gets the keyboard focus, before
urxvt::ShiftMask, LockMask, ControlMask, Mod1Mask, Mod2Mask, Mod3Mask,
Mod4Mask, Mod5Mask, Button1Mask, Button2Mask, Button3Mask, Button4Mask,
Button5Mask, AnyModifier
+ urxvt::NoEventMask, KeyPressMask, KeyReleaseMask, ButtonPressMask,
+ ButtonReleaseMask, EnterWindowMask, LeaveWindowMask, PointerMotionMask,
+ PointerMotionHintMask, Button1MotionMask, Button2MotionMask,
+ Button3MotionMask, Button4MotionMask, Button5MotionMask,
+ ButtonMotionMask, KeymapStateMask, ExposureMask, VisibilityChangeMask,
+ StructureNotifyMask, ResizeRedirectMask, SubstructureNotifyMask,
+ SubstructureRedirectMask, FocusChangeMask, PropertyChangeMask,
+ ColormapChangeMask, OwnerGrabButtonMask
+ urxvt::KeyPress, KeyRelease, ButtonPress, ButtonRelease, MotionNotify,
+ EnterNotify, LeaveNotify, FocusIn, FocusOut, KeymapNotify, Expose,
+ GraphicsExpose, NoExpose, VisibilityNotify, CreateNotify, DestroyNotify,
+ UnmapNotify, MapNotify, MapRequest, ReparentNotify, ConfigureNotify,
+ ConfigureRequest, GravityNotify, ResizeRequest, CirculateNotify,
+ CirculateRequest, PropertyNotify, SelectionClear, SelectionRequest,
+ SelectionNotify, ColormapNotify, ClientMessage, MappingNotify
Various constants for use in X calls and event processing.
RENDITION
$term->destroy
Destroy the terminal object (close the window, free resources etc.).
- Please note that rxvt will not exit as long as any event watchers
+ Please note that urxvt will not exit as long as any event watchers
(timers, io watchers) are still active.
$isset = $term->option ($optval[, $set])
$success = $term->parse_keysym ($keysym_spec, $command_string)
Adds a keymap translation exactly as specified via a resource. See
- the "keysym" resource in the rxvt(1) manpage.
+ the "keysym" resource in the urxvt(1) manpage.
$rend = $term->rstyle ([$new_rstyle])
Return and optionally change the current rendition. Text that is
$windowid = $term->vt
Return the window id of the terminal window.
+ $term->vt_emask_add ($x_event_mask)
+ Adds the specified events to the vt event mask. Useful e.g. when you
+ want to receive pointer events all the times:
+
+ $term->vt_emask_add (urxvt::PointerMotionMask);
+
$window_width = $term->width
$window_height = $term->height
$font_width = $term->fwidth
projects / dana / urxvt.git / commitdiff