src/perl/selection-autotransform
src/perl/selection-pastebin
src/perl/searchable-scrollback
-src/perl/automove-background
src/perl/matcher
src/perl/tabbed
src/perl/xim-onthespot
libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000)
libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00002aaaaada2000)
- libc.so.6 => /lib/libc.so.6 (0x00002aaaaaeb0000)
- libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab0ee000)
- /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)
+ libc.so.6 => /lib/libc.so.6 (0x00002aaaaaeb0000)
+ libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab0ee000)
+ /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)
No large bloated libraries (of course, none were linked in statically),
except maybe libX11 :)
Here are four ways to get transparency. Do read the manpage and option
descriptions for the programs mentioned and rxvt-unicode. Really, do it!
- 1. Use inheritPixmap:
+ 1. Use transparent mode:
Esetroot wallpaper.jpg
- urxvt -ip -tint red -sh 40
+ urxvt -tr -tint red -sh 40
That works. If you think it doesn't, you lack transparency and tinting
support, or you are unable to read.
your picture with gimp or any other tool:
convert wallpaper.jpg -blur 20x20 -modulate 30 background.jpg
- urxvt -pixmap background.jpg -pe automove-background
+ urxvt -pixmap "background.jpg;:root"
- That works. If you think it doesn't, you lack AfterImage and Perl
- support, or you are unable to read.
+ That works. If you think it doesn't, you lack AfterImage support, or you
+ are unable to read.
3. Use an ARGB visual:
root background, as well as dynamic scaling and bluring of
background images.
- Note that with this option enabled, urxvt's memory footprint might
+ Note that with this option enabled, rxvt's memory footprint might
increase by a few megabytes even if no extra features are used
(mostly due to third-party libraries used by libAI). Memory
footprint may somewhat be lowered if libAfterImage is configured
without support for SVG.
--enable-transparency (default: on)
- Add support for inheriting parent backgrounds thus giving a fake
- transparency to the term.
+ Add support for backgrounds, creating illusion of transparency in
+ the term.
--enable-fading (default: on)
Add support for fading the text when focus is lost.
verbose X error handling
--enable-iso14755 (default: on)
- Enable extended ISO 14755 support (see urxvt(1), or doc/rxvt.1.txt).
+ Enable extended ISO 14755 support (see rxvt(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: on)
- Enable an embedded perl interpreter. See the urxvtperl(3) manpage
+ Enable an embedded perl interpreter. See the rxvtperl(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"
<meta name="description" content="Pod documentation for rxvt-unicode (ouR XVT, unicode)" />
<meta name="inputfile" content="<standard input>" />
<meta name="outputfile" content="<standard output>" />
- <meta name="created" content="Sat Oct 27 14:07:34 2007" />
+ <meta name="created" content="Mon Nov 19 13:01:50 2007" />
<meta name="generator" content="Pod::Xhtml 1.57" />
<link rel="stylesheet" href="http://res.tst.eu/pod.css"/></head>
<body>
</div>
<h1 id="SYNOPSIS">SYNOPSIS</h1><p><a href="#TOP" class="toplink">Top</a></p>
<div id="SYNOPSIS_CONTENT">
-<p><strong>urxvt</strong> [options] [-e command [ args ]]</p>
+<p><strong>rxvt</strong> [options] [-e command [ args ]]</p>
</div>
<h1 id="DESCRIPTION">DESCRIPTION</h1><p><a href="#TOP" class="toplink">Top</a></p>
</div>
<h1 id="FREQUENTLY_ASKED_QUESTIONS">FREQUENTLY ASKED QUESTIONS</h1><p><a href="#TOP" class="toplink">Top</a></p>
<div id="FREQUENTLY_ASKED_QUESTIONS_CONTENT">
-<p>See urxvt(7) (try <code>man 7 urxvt</code>) for a list of
+<p>See rxvt(7) (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/rxvt-unicode/doc/rxvt.7.html">http://cvs.schmorp.de/browse/rxvt-unicode/doc/rxvt.7.html</a>.</p>
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 urxvtd(1) (daemon) and
-urxvtc(1) (client).</p>
+drastically reduces memory usage. See rxvtd(1) (daemon) and
+rxvtc(1) (client).</p>
<p>It also makes technical information about escape sequences (which have
-been extended) more accessible: see urxvt(7) for technical
+been extended) more accessible: see rxvt(7) for technical
reference documentation (escape sequences etc.).</p>
</div>
<h1 id="OPTIONS">OPTIONS</h1><p><a href="#TOP" class="toplink">Top</a></p>
<div id="OPTIONS_CONTENT">
-<p>The <strong>urxvt</strong> options (mostly a subset of <i>xterm</i>'s) are listed
+<p>The <strong>rxvt</strong> options (mostly a subset of <i>xterm</i>'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 <i>Options</i> line. Option descriptions may be prefixed with which
compile option each is dependent upon. e.g. `Compile <i>XIM</i>:' requires
-<i>XIM</i> on the <i>Options</i> line. Note: `urxvt -help' gives a list of all
+<i>XIM</i> on the <i>Options</i> 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>
<dd>
<p>Turn on/off illusion of a transparent window background. Obsolete form of it is
<strong>-ip</strong> and it should not be used anymore; resource <strong>transparent</strong>.</p>
- <p><i>Please note that old resource name of <strong>inheritPixmap</strong> is obsolete and should be
-changed to <strong>transparent</strong>. Backwards compatibility support for <strong>inheritPixmap</strong> will
+ <p><i>Please note that old resource name of <strong>inheritPixmap</strong> is obsolete and should be
+changed to <strong>transparent</strong>. Backwards compatibility support for <strong>inheritPixmap</strong> will
be phased out in future versions of rxvt!</i></p>
- <p><i>Please address all transparency related issues to Sasha Vasko at
-sasha@aftercode.net. Read the FAQ (man 7 urxvt)!</i></p>
+ <p><i>Please address all transparency related issues to Sasha Vasko at
+sasha@aftercode.net. Read the FAQ (man 7 rxvt)!</i></p>
</dd>
<dt><strong>-fade</strong> <i>number</i></dt>
<dd>
used to brighten or darken the image in addition to tinting it.
Please note that certain tint colours can be applied on the server-side,
thus yielding performance gain of two orders of magnitude. These colours are:
-blue, red, green, cyan, magenta, yellow, and those close to them; resource
+blue, red, green, cyan, magenta, yellow, and those close to them. Also
+pure black and pure white colors essentially mean no tinting; resource
<i>tintColor</i>. Example:</p>
-<pre> urxvt -tr -tint blue -sh 40
+<pre> rxvt -tr -tint blue -sh 40
</pre>
</dd>
<dt><strong>-sh</strong> <i>number</i></dt>
<dd>
- <p>Darken (0 .. 100) or lighten (-1 .. -100) the transparent
+ <p>Darken (0 .. 100) or lighten (100 .. 200) the transparent
background image in addition to (or instead of) tinting it;
resource <i>shading</i>.</p>
</dd>
<dd>
<p>Window foreground colour; resource <strong>foreground</strong>.</p>
</dd>
- <dt><strong>-pixmap</strong> <i>file[;geom]</i></dt>
+ <dt><strong>-pixmap</strong> <i>file[;geom[:op1][:op2][...]]</i></dt>
<dd>
- <p>Compile <i>afterimage</i>: Specify image file for the background and also
+ <p>Compile <i>afterimage</i>: Specify image file for the background and also
optionally specify its scaling with a geometry string. Note you may need to
add quotes to avoid special shell interpretation of the <code>;</code> in the
command-line; for more details see resource <strong>backgroundPixmap</strong>.</p>
<p>In short, to specify an X11 core font, just specify its name or prefix it
with <code>x:</code>. To specify an XFT-font, you need to prefix it with <code>xft:</code>,
e.g.:</p>
-<pre> urxvt -fn "xft:Bitstream Vera Sans Mono:pixelsize=15"
- urxvt -fn "9x15bold,xft:Bitstream Vera Sans Mono"
+<pre> rxvt -fn "xft:Bitstream Vera Sans Mono:pixelsize=15"
+ rxvt -fn "9x15bold,xft:Bitstream Vera Sans Mono"
</pre>
<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>
<dt><strong>-fb</strong> <i>fontlist</i></dt>
<dd>
</dd>
<dt><strong>-e</strong> <i>command [arguments]</i></dt>
<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 <i>-title</i> (<i>-T</i>) nor <i>-n</i> are
given on the command line. If this option is used, it must be the last
failing that, <i>sh(1)</i>.</p>
<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>
-<pre> urxvt -e sh -c "shell commands"
+<pre> rxvt -e sh -c "shell commands"
</pre>
</dd>
</dd>
<dt><strong>-hold</strong>|<strong>+hold</strong></dt>
<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>
<dt><strong>-embed</strong> <i>windowid</i></dt>
<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>
- <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
+ <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
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>
- <p>The window will not be destroyed when urxvt exits.</p>
- <p>It might be useful to know that urxvt will not close file
+create an extra subwindow for rxvt and leave it alone.</p>
+ <p>The window will not be destroyed when rxvt exits.</p>
+ <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 whether the <code>-embed</code> option was used or
<pre> my $rxvt = new Gtk2::Socket;
$rxvt->signal_connect_after (realize => sub {
my $xid = $_[0]->window->get_xid;
- system "urxvt -embed $xid &";
+ system "rxvt -embed $xid &";
});
</pre>
</dd>
<dt><strong>-pty-fd</strong> <i>file descriptor</i></dt>
<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 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>
- <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>
<p>As an extremely special case, specifying <code>-1</code> will completely suppress
my $pty = new IO::Pty;
fcntl $pty, F_SETFD, 0; # clear close-on-exec
- system "urxvt -pty-fd " . (fileno $pty) . "&";
+ system "rxvt -pty-fd " . (fileno $pty) . "&";
close $pty;
# now communicate with rxvt
</div>
<h1 id="RESOURCES_available_also_as_long_opt">RESOURCES (available also as long-options)</h1><p><a href="#TOP" class="toplink">Top</a></p>
<div id="RESOURCES_available_also_as_long_opt-2">
-<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
5. $XENVIRONMENT file OR $HOME/.Xdefaults-<nodename>
</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 <i>rxvt</i> to be easily
+common to both <strong>rxvt</strong> and the original <i>rxvt</i> 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 urxvtperl(3) manpage for additional settings by perl
+check the rxvtperl(3) manpage for additional settings by perl
extensions not documented here):</p>
<dl>
<dt><strong>depth:</strong> <i>bitdepth</i></dt>
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>
<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>
<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>jumpScroll:</strong> <i>boolean</i></dt>
<dd>
<p><strong>True</strong>: specify that jump scrolling should be used. When receiving lots
-of lines, urxvt will only scroll once a whole screen height of lines
+of lines, rxvt will only scroll once a whole screen height of lines
has been read, resulting in fewer updates while still displaying every
received line; option <strong>-j</strong>.</p>
- <p><strong>False</strong>: specify that smooth scrolling should be used. urxvt will
+ <p><strong>False</strong>: specify that smooth scrolling should be used. rxvt will
force a screen refresh on each new line it received; option <strong>+j</strong>.</p>
</dd>
<dt><strong>skipScroll:</strong> <i>boolean</i></dt>
<dd>
<p><strong>True</strong>: (the default) specify that skip scrolling should be used. When
-receiving lots of lines, urxvt will only scroll once in a while
+receiving lots of lines, rxvt will only scroll once in a while
(around 60 times per second), resulting in far fewer updates. This can
-result in urxvt not ever displaying some of the lines it receives;
+result in rxvt not ever displaying some of the lines it receives;
option <strong>-ss</strong>.</p>
<p><strong>False</strong>: specify that everything is to be displayed, even
if the refresh is too fast for the human eye to read anything (or the
</dd>
<dt><strong>blurRadius:</strong> <i>number</i></dt>
<dd>
- <p>Apply Gaussian Blurr with the specified radius to the transparent
+ <p>Apply Gaussian Blurr with the specified radius to the transparent
background image; option <strong>-blr</strong>.</p>
</dd>
<dt><strong>scrollColor:</strong> <i>colour</i></dt>
<p>The colour of the border around the text area and between the scrollbar
and the text.</p>
</dd>
- <dt><strong>backgroundPixmap:</strong> <i>file[;geom]</i></dt>
- <dd>
- <p>Use the specified image file for the background and also optionally
-specify its scaling with a geometry string <strong>WxH+X+Y</strong>,
-in which <strong>"W" / "H"</strong> specify the horizontal/vertical scale (percent),
-and <strong>"X" / "Y"</strong> locate the image centre (percent).
-A scale of 0 displays the image with tiling. A scale of 1 displays the
-image without any scaling. A scale of 2 to 9 specifies an integer
-number of images in that direction. No image will be magnified beyond
-10 times its original size. The maximum permitted scale is 1000.
-Special string of <strong>"auto"</strong> used as a geometry will cause image to be
-automatically scaled to match window size.
-If used in conjunction with <strong>-tr</strong> option - specified pixmap will be
-blended over transparency image using either alpha-blending, or any
-other blending type, specified with <strong>-blt "type"</strong> option.
-[default 0x0+50+50]</p>
+ <dt><strong>backgroundPixmap:</strong> <i>file[;geom[:op1][:op2][...]]</i></dt>
+ <dd>
+ <p>Use the specified image file for the background and also
+optionally specify its scaling with a geometry string <strong>WxH+X+Y</strong>,
+(default <code>0x0+50+50</code>) in which <strong>"W" / "H"</strong> specify the
+horizontal/vertical scale (percent), and <strong>"X" / "Y"</strong> locate the image
+centre (percent). A scale of 0 displays the image with tiling. A scale
+of 1 displays the image without any scaling. A scale of 2 to 9 specifies
+an integer number of images in that direction. No image will be magnified
+beyond 10 times its original size. The maximum permitted scale is 1000.
+Additional operations can be specified after colon <strong>:op1:op2...</strong>.
+Supported operations are:</p>
+<pre> tile force background image to be tiled and not scaled. Equivalent to 0x0,
+ propscale will scale image keeping proportions,
+ auto will scale image to match window size. Equivalent to 100x100;
+ hscale will scale image horizontally to the window size;
+ vscale will scale image vertically to the window size;
+ scale will scale image to match window size;
+ root will tile image as if it was a root window background, auto-adjusting
+ whenever terminal window moves.
+
+</pre>
+ <p>If used in conjunction with <strong>-tr</strong> option, the specified pixmap will be
+blended over transparency image using either alpha-blending, or any
+other blending type, specified with <strong>-blt "type"</strong> option.</p>
</dd>
<dt><strong>path:</strong> <i>path</i></dt>
<dd>
<p>The characters used as delimiters for double-click word selection
(whitespace delimiting is added automatically if resource is given).</p>
<p>When the perl selection extension is in use (the default if compiled
-in, see the urxvtperl(3) manpage), a suitable regex using these
+in, see the rxvtperl(3) 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>
<p>When the selection extension is not used, only ISO-8859-1 characters can
be used. If not specified, the built-in default is used:</p>
- <p><strong>BACKSLASH `"'&()*,;<=>?@[]{|}</strong></p>
+ <p><strong>BACKSLASH `"'&()*,;<=>?@[]^{|}</strong></p>
</dd>
<dt><strong>preeditType:</strong> <i>style</i></dt>
<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>
</dd>
<dt><strong>hold</strong>: <i>boolean</i></dt>
<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>
</pre>
<p>If <i>string</i> 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>
<pre> URxvt.keysym.M-C-c: command:\033]701;zh_CN.GBK\007
</pre>
<p>If <i>string</i> 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 urxvtperl(3)
+is passed to the <code>on_keyboard_command</code> perl handler. See the rxvtperl(3)
manpage. For example, the <cite>selection</cite> 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>
<pre> URxvt.keysym.M-C-c: perl:selection:rot13
</pre>
definitions for <code>Meta-a</code>, <code>Shift-a</code> and so on, unless some of those are defined
mappings themselves.</p>
<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>
<pre> URxvt.keysym.Insert: <my insert key sequence>
URxvt.keysym.M-C-2: command:\033]50;9x15bold\007
</pre>
- <p>Other things are possible, e.g. resizing (see urxvt(7) for more
+ <p>Other things are possible, e.g. resizing (see rxvt(7) for more
info):</p>
<pre> URxvt.keysym.M-C-3: command:\033[8;25;80t
URxvt.keysym.M-C-4: command:\033[8;48;110t
<dt><strong>perl-eval</strong>: <i>string</i></dt>
<dd>
<p>Perl code to be evaluated when all extensions have been registered. See
-the urxvtperl(3) manpage. Due to security reasons, this resource
+the rxvtperl(3) manpage. Due to security reasons, this resource
will be ignored when running setuid/setgid.</p>
</dd>
<dt><strong>perl-lib</strong>: <i>path</i></dt>
<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
-<cite>/usr/local/lib/urxvt/perl/</cite>. Due to security reasons, this resource
+rxvt will first look in these directories and then in
+<cite>/opt/rxvt/lib/urxvt/perl/</cite>. Due to security reasons, this resource
will be ignored when running setuid/setgid.</p>
- <p>See the urxvtperl(3) manpage.</p>
+ <p>See the rxvtperl(3) manpage.</p>
</dd>
<dt><strong>selection.pattern-<i>idx</i></strong>: <i>perl-regex</i></dt>
<dd>
- <p>Additional selection patterns, see the urxvtperl(3) manpage for
+ <p>Additional selection patterns, see the rxvtperl(3) manpage for
details.</p>
</dd>
<dt><strong>selection-autotransform.<i>idx</i></strong>: <i>perl-transform</i></dt>
<dd>
- <p>Selection auto-transform patterns, see the urxvtperl(3) manpage
+ <p>Selection auto-transform patterns, see the rxvtperl(3) manpage
for details.</p>
</dd>
<dt><strong>searchable-scrollback:</strong> <i>keysym</i></dt>
</div>
<h1 id="THE_SCROLLBAR">THE SCROLLBAR</h1><p><a href="#TOP" class="toplink">Top</a></p>
<div id="THE_SCROLLBAR_CONTENT">
-<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 <i>xterm</i></p>
<p>Scroll down with <strong>Button1</strong> (<strong>xterm-scrollbar</strong>) or <strong>Shift-Next</strong>.
</dd>
<dt><strong>Pasting</strong>:</dt>
<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
<strong>Meta</strong> modifier) to be inserted as if it had been typed on the keyboard.</p>
<p>Pressing <strong>Shift-Insert</strong> causes the value of the PRIMARY selection to be
</div>
<h1 id="LOGIN_STAMP">LOGIN STAMP</h1><p><a href="#TOP" class="toplink">Top</a></p>
<div id="LOGIN_STAMP_CONTENT">
-<p><strong>urxvt</strong> tries to write an entry into the <i>utmp</i>(5) file so that
+<p><strong>rxvt</strong> tries to write an entry into the <i>utmp</i>(5) file so that
it can be seen via the <i>who(1)</i> 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>
</div>
<h1 id="COLORS_AND_GRAPHICS">COLORS AND GRAPHICS</h1><p><a href="#TOP" class="toplink">Top</a></p>
<div id="COLORS_AND_GRAPHICS_CONTENT">
<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>color2</td><td>(green)</td><td>= Green3</td></tr><tr><td>color3</td><td>(yellow)</td><td>= Yellow3</td></tr><tr><td>color4</td><td>(blue)</td><td>= Blue3</td></tr><tr><td>color5</td><td>(magenta)</td><td>= Magenta3</td></tr><tr><td>color6</td><td>(cyan)</td><td>= Cyan3</td></tr><tr><td>color7</td><td>(white)</td><td>= AntiqueWhite</td></tr><tr><td>color8</td><td>(bright black)</td><td>= Grey25</td></tr><tr><td>color9</td><td>(bright red)</td><td>= Red</td></tr><tr><td>color10</td><td>(bright green)</td><td>= Green</td></tr><tr><td>color11</td><td>(bright yellow)</td><td>= Yellow</td></tr><tr><td>color12</td><td>(bright blue)</td><td>= Blue</td></tr><tr><td>color13</td><td>(bright magenta)</td><td>= Magenta</td></tr><tr><td>color14</td><td>(bright cyan)</td><td>= Cyan</td></tr><tr><td>color15</td><td>(bright white)</td><td>= White</td></tr><tr><td>foreground</td><td></td><td>= Black</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. <i>index = r * 16 + g * 4 + b +
16</i>), followed by 8 additional shades of gray (with indices 80 to 87).</p>
<i>xterm</i>(1) where the colours are only swapped if they have not otherwise
been specified. For example,</p>
<dl>
- <dt><strong>urxvt -fg Black -bg White -rv</strong></dt>
+ <dt><strong>rxvt -fg Black -bg White -rv</strong></dt>
<dd>
<p>would yield White on Black, while on <i>xterm</i>(1) it would yield Black
on White.</p>
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/aaaa -fg "[80]pink"
+<pre> rxvt -depth 32 -bg rgba:0000/0000/0000/aaaa -fg "[80]pink"
</pre>
<p><i>Please note that transparency of any kind if completely unsupported by
</div>
<h1 id="ENVIRONMENT">ENVIRONMENT</h1><p><a href="#TOP" class="toplink">Top</a></p>
<div id="ENVIRONMENT_CONTENT">
-<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>TERM</strong></dt>
<dd>
</dd>
<dt><strong>COLORTERM</strong></dt>
<dd>
- <p>Either <code>rxvt</code>, <code>rxvt-xpm</code>, depending on whether urxvt was
-compiled with background image support, and optionally with the added
-extension <code>-mono</code> to indicate that rxvt-unicode runs on a monochrome
+ <p>Either <code>rxvt</code>, <code>rxvt-xpm</code>, depending on whether rxvt was
+compiled with background image support, and optionally with the added
+extension <code>-mono</code> to indicate that rxvt-unicode runs on a monochrome
screen.</p>
</dd>
<dt><strong>COLORFGBG</strong></dt>
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
-was compiled with background image support. Libraries like <code>ncurses</code>
+string <code>default</code>), and <code>xpm</code> is the string <code>default</code> if rxvt
+was compiled with background image support. Libraries like <code>ncurses</code>
and <code>slang</code> can (and do) use this information to optimize screen output.</p>
</dd>
<dt><strong>WINDOWID</strong></dt>
<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>
<dt><strong>TERMINFO</strong></dt>
<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>
<dt><strong>DISPLAY</strong></dt>
<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>
<dt><strong>SHELL</strong></dt>
</dd>
<dt><strong>RXVT_SOCKET</strong></dt>
<dd>
- <p>The unix domain socket path used by urxvtc(1) and
-urxvtd(1).</p>
+ <p>The unix domain socket path used by rxvtc(1) and
+rxvtd(1).</p>
<p>Default <cite>$HOME/.rxvt-unicode-<i><nodename</i></cite>.</p>
</dd>
<dt><strong>HOME</strong></dt>
<dt><strong>XENVIRONMENT</strong></dt>
<dd>
<p>If set and accessible, gives the name of a X resource file to be loaded by
-urxvt.</p>
+rxvt.</p>
</dd>
</dl>
</div>
<h1 id="SEE_ALSO">SEE ALSO</h1><p><a href="#TOP" class="toplink">Top</a></p>
<div id="SEE_ALSO_CONTENT">
-<p>urxvt(7), urxvtc(1), urxvtd(1), xterm(1), sh(1), resize(1), X(1), pty(4), tty(4), utmp(5)</p>
+<p>rxvt(7), rxvtc(1), rxvtd(1), xterm(1), sh(1), resize(1), X(1), pty(4), tty(4), utmp(5)</p>
</div>
<h1 id="CURRENT_PROJECT_COORDINATOR">CURRENT PROJECT COORDINATOR</h1><p><a href="#TOP" class="toplink">Top</a></p>
-.\" Automatically generated by Pod::Man v1.37, Pod::Parser v1.3
+.\" Automatically generated by Pod::Man v1.37, Pod::Parser v1.35
.\"
.\" Standard preamble:
.\" ========================================================================
.\" ========================================================================
.\"
.IX Title "@@RXVT_NAME@@ 1"
-.TH @@RXVT_NAME@@ 1 "2007-10-29" "8.3" "RXVT-UNICODE"
+.TH @@RXVT_NAME@@ 1 "2007-11-19" "8.4" "RXVT-UNICODE"
.SH "NAME"
rxvt\-unicode (ouR XVT, unicode) \- (a VT102 emulator for the X window system)
.SH "SYNOPSIS"
Turn on/off illusion of a transparent window background. Obsolete form of it is
\&\fB\-ip\fR and it should not be used anymore; resource \fBtransparent\fR.
.Sp
-\&\fIPlease note that old resource name of \f(BIinheritPixmap\fI is obsolete and should be
-changed to \f(BItransparent\fI. Backwards compatibility support for \f(BIinheritPixmap\fI will
+\&\fIPlease note that old resource name of \f(BIinheritPixmap\fI is obsolete and should be
+changed to \f(BItransparent\fI. Backwards compatibility support for \f(BIinheritPixmap\fI will
be phased out in future versions of rxvt!\fR
.Sp
-\&\fIPlease address all transparency related issues to Sasha Vasko at
+\&\fIPlease address all transparency related issues to Sasha Vasko at
sasha@aftercode.net. Read the \s-1FAQ\s0 (man 7 @@RXVT_NAME@@)!\fR
.IP "\fB\-fade\fR \fInumber\fR" 4
.IX Item "-fade number"
used to brighten or darken the image in addition to tinting it.
Please note that certain tint colours can be applied on the server\-side,
thus yielding performance gain of two orders of magnitude. These colours are:
-blue, red, green, cyan, magenta, yellow, and those close to them. Also
-pure black and pure white colors essentialy mean no tinting; resource
+blue, red, green, cyan, magenta, yellow, and those close to them. Also
+pure black and pure white colors essentially mean no tinting; resource
\&\fItintColor\fR. Example:
.Sp
.Vb 1
-\& @@RXVT_NAME@@ \-tr \-tint blue \-sh 40
+\& @@RXVT_NAME@@ -tr -tint blue -sh 40
.Ve
.IP "\fB\-sh\fR \fInumber\fR" 4
.IX Item "-sh number"
.IP "\fB\-fg\fR \fIcolour\fR" 4
.IX Item "-fg colour"
Window foreground colour; resource \fBforeground\fR.
-.IP "\fB\-pixmap\fR \fIfile[;geom]\fR" 4
-.IX Item "-pixmap file[;geom]"
-Compile \fIafterimage\fR: Specify image file for the background and also
+.IP "\fB\-pixmap\fR \fIfile[;geom[:op1][:op2][...]]\fR" 4
+.IX Item "-pixmap file[;geom[:op1][:op2][...]]"
+Compile \fIafterimage\fR: Specify image file for the background and also
optionally specify its scaling with a geometry string. Note you may need to
add quotes to avoid special shell interpretation of the \f(CW\*(C`;\*(C'\fR in the
command\-line; for more details see resource \fBbackgroundPixmap\fR.
e.g.:
.Sp
.Vb 2
-\& @@RXVT_NAME@@ \-fn "xft:Bitstream Vera Sans Mono:pixelsize=15"
-\& @@RXVT_NAME@@ \-fn "9x15bold,xft:Bitstream Vera Sans Mono"
+\& @@RXVT_NAME@@ -fn "xft:Bitstream Vera Sans Mono:pixelsize=15"
+\& @@RXVT_NAME@@ -fn "9x15bold,xft:Bitstream Vera Sans Mono"
.Ve
.Sp
See also the question \*(L"How does rxvt-unicode choose fonts?\*(R" in the \s-1FAQ\s0
run shell commands, you have to specify the shell, like this:
.Sp
.Vb 1
-\& @@RXVT_NAME@@ \-e sh \-c "shell commands"
+\& @@RXVT_NAME@@ -e sh -c "shell commands"
.Ve
.IP "\fB\-title\fR \fItext\fR" 4
.IX Item "-title text"
.Sp
.Vb 5
\& my $rxvt = new Gtk2::Socket;
-\& $rxvt\->signal_connect_after (realize => sub {
-\& my $xid = $_[0]\->window\->get_xid;
-\& system "@@RXVT_NAME@@ \-embed $xid &";
+\& $rxvt->signal_connect_after (realize => sub {
+\& my $xid = $_[0]->window->get_xid;
+\& system "@@RXVT_NAME@@ -embed $xid &";
\& });
.Ve
.IP "\fB\-pty\-fd\fR \fIfile descriptor\fR" 4
.Sp
.Vb 4
\& my $pty = new IO::Pty;
-\& fcntl $pty, F_SETFD, 0; # clear close\-on\-exec
-\& system "@@RXVT_NAME@@ \-pty\-fd " . (fileno $pty) . "&";
+\& fcntl $pty, F_SETFD, 0; # clear close-on-exec
+\& system "@@RXVT_NAME@@ -pty-fd " . (fileno $pty) . "&";
\& close $pty;
.Ve
.Sp
.Vb 3
\& # now communicate with rxvt
-\& my $slave = $pty\->slave;
+\& my $slave = $pty->slave;
\& while (<$slave>) { print $slave "got <$_>\en" }
.Ve
.IP "\fB\-pe\fR \fIstring\fR" 4
with later settings overwriting earlier ones:
.PP
.Vb 5
-\& 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
+\& 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\-<nodename>
+\& 5. $XENVIRONMENT file OR $HOME/.Xdefaults-<nodename>
.Ve
.PP
Note that when reading X resources, \fB@@RXVT_NAME@@\fR recognizes two class
Specify background blending type; option \fB\-blt\fR.
.IP "\fBblurRadius:\fR \fInumber\fR" 4
.IX Item "blurRadius: number"
-Apply Gaussian Blurr with the specified radius to the transparent
+Apply Gaussian Blurr with the specified radius to the transparent
background image; option \fB\-blr\fR.
.IP "\fBscrollColor:\fR \fIcolour\fR" 4
.IX Item "scrollColor: colour"
.IX Item "borderColor: colour"
The colour of the border around the text area and between the scrollbar
and the text.
-.IP "\fBbackgroundPixmap:\fR \fIfile[;geom]\fR" 4
-.IX Item "backgroundPixmap: file[;geom]"
-Use the specified image file for the background and also optionally
-specify its scaling with a geometry string \fBWxH+X+Y\fR,
-in which \fB\*(L"W\*(R" / \*(L"H\*(R"\fR specify the horizontal/vertical scale (percent),
-and \fB\*(L"X\*(R" / \*(L"Y\*(R"\fR locate the image centre (percent).
-A scale of 0 displays the image with tiling. A scale of 1 displays the
-image without any scaling. A scale of 2 to 9 specifies an integer
-number of images in that direction. No image will be magnified beyond
-10 times its original size. The maximum permitted scale is 1000.
-Special string of \fB\*(L"auto\*(R"\fR used as a geometry will cause image to be
-automatically scaled to match window size.
-If used in conjunction with \fB\-tr\fR option \- specified pixmap will be
-blended over transparency image using either alpha\-blending, or any
+.IP "\fBbackgroundPixmap:\fR \fIfile[;geom[:op1][:op2][...]]\fR" 4
+.IX Item "backgroundPixmap: file[;geom[:op1][:op2][...]]"
+Use the specified image file for the background and also
+optionally specify its scaling with a geometry string \fBWxH+X+Y\fR,
+(default \f(CW\*(C`0x0+50+50\*(C'\fR) in which \fB\*(L"W\*(R" / \*(L"H\*(R"\fR specify the
+horizontal/vertical scale (percent), and \fB\*(L"X\*(R" / \*(L"Y\*(R"\fR locate the image
+centre (percent). A scale of 0 displays the image with tiling. A scale
+of 1 displays the image without any scaling. A scale of 2 to 9 specifies
+an integer number of images in that direction. No image will be magnified
+beyond 10 times its original size. The maximum permitted scale is 1000.
+Additional operations can be specified after colon \fB:op1:op2...\fR.
+Supported operations are:
+.Sp
+.Vb 8
+\& tile force background image to be tiled and not scaled. Equivalent to 0x0,
+\& propscale will scale image keeping proportions,
+\& auto will scale image to match window size. Equivalent to 100x100;
+\& hscale will scale image horizontally to the window size;
+\& vscale will scale image vertically to the window size;
+\& scale will scale image to match window size;
+\& root will tile image as if it was a root window background, auto-adjusting
+\& whenever terminal window moves.
+.Ve
+.Sp
+If used in conjunction with \fB\-tr\fR option, the specified pixmap will be
+blended over transparency image using either alpha\-blending, or any
other blending type, specified with \fB\-blt \*(L"type\*(R"\fR option.
-[default 0x0+50+50]
.IP "\fBpath:\fR \fIpath\fR" 4
.IX Item "path: path"
Specify the colon-delimited search path for finding background image files.
.Sp
.Vb 5
\& URxvt.font: 9x15bold,\e
-\& \-misc\-fixed\-bold\-r\-normal\-\-15\-140\-75\-75\-c\-90\-iso10646\-1,\e
-\& \-misc\-fixed\-medium\-r\-normal\-\-15\-140\-75\-75\-c\-90\-iso10646\-1, \e
+\& -misc-fixed-bold-r-normal--15-140-75-75-c-90-iso10646-1,\e
+\& -misc-fixed-medium-r-normal--15-140-75-75-c-90-iso10646-1, \e
\& [codeset=JISX0208]xft:Kochi Gothic:antialias=false, \e
\& xft:Code2000:antialias=false
.Ve
Example:
.Sp
.Vb 1
-\& URxvt.print\-pipe: cat > $(TMPDIR=$HOME mktemp urxvt.XXXXXX)
+\& URxvt.print-pipe: cat > $(TMPDIR=$HOME mktemp urxvt.XXXXXX)
.Ve
.Sp
This creates a new file in your home directory with the screen contents
When the selection extension is not used, only \s-1ISO\-8859\-1\s0 characters can
be used. If not specified, the built-in default is used:
.Sp
-\&\fB\s-1BACKSLASH\s0 `"'&()*,;<=>?@[]{|}\fR
+\&\fB\s-1BACKSLASH\s0 `"'&()*,;<=>?@[]^{|}\fR
.IP "\fBpreeditType:\fR \fIstyle\fR" 4
.IX Item "preeditType: style"
\&\fBOverTheSpot\fR, \fBOffTheSpot\fR, \fBRoot\fR; option \fB\-pt\fR.
Its usage can be demonstrated by an example:
.Sp
.Vb 1
-\& URxvt.keysym.M\-C\-0x61: list|\e033<M\-C\-|abc|>
+\& URxvt.keysym.M-C-0x61: list|\e033<M-C-|abc|>
.Ve
.Sp
The above line is equivalent to the following three lines:
.Sp
.Vb 3
-\& URxvt.keysym.Meta\-Control\-0x61: \e033<M\-C\-a>
-\& URxvt.keysym.Meta\-Control\-0x62: \e033<M\-C\-b>
-\& URxvt.keysym.Meta\-Control\-0x63: \e033<M\-C\-c>
+\& URxvt.keysym.Meta-Control-0x61: \e033<M-C-a>
+\& URxvt.keysym.Meta-Control-0x62: \e033<M-C-b>
+\& URxvt.keysym.Meta-Control-0x63: \e033<M-C-c>
.Ve
.Sp
If \fIstring\fR takes the form of \f(CW\*(C`command:STRING\*(C'\fR, the specified \fB\s-1STRING\s0\fR
when Control-Meta-c is being pressed":
.Sp
.Vb 1
-\& URxvt.keysym.M\-C\-c: command:\e033]701;zh_CN.GBK\e007
+\& URxvt.keysym.M-C-c: command:\e033]701;zh_CN.GBK\e007
.Ve
.Sp
If \fIstring\fR takes the form \f(CW\*(C`perl:STRING\*(C'\fR, then the specified \fB\s-1STRING\s0\fR
\&\f(CW\*(C`@@RXVT_NAME@@ \-pe selection\*(C'\fR) listens for \f(CW\*(C`selection:rot13\*(C'\fR events:
.Sp
.Vb 1
-\& URxvt.keysym.M\-C\-c: perl:selection:rot13
+\& URxvt.keysym.M-C-c: perl:selection:rot13
.Ve
.Sp
Due the the large number of modifier combinations, a defined key mapping
.Sp
.Vb 2
\& URxvt.keysym.Insert: <my insert key sequence>
-\& URxvt.keysym.S\-Insert: builtin:
+\& URxvt.keysym.S-Insert: builtin:
.Ve
.Sp
The first line defines a mapping for \f(CW\*(C`Insert\*(C'\fR and \fIany\fR combination
font-switching at runtime:
.Sp
.Vb 2
-\& URxvt.keysym.M\-C\-1: command:\e033]50;suxuseuro\e007
-\& URxvt.keysym.M\-C\-2: command:\e033]50;9x15bold\e007
+\& URxvt.keysym.M-C-1: command:\e033]50;suxuseuro\e007
+\& URxvt.keysym.M-C-2: command:\e033]50;9x15bold\e007
.Ve
.Sp
Other things are possible, e.g. resizing (see @@RXVT_NAME@@(7) for more
info):
.Sp
.Vb 2
-\& URxvt.keysym.M\-C\-3: command:\e033[8;25;80t
-\& URxvt.keysym.M\-C\-4: command:\e033[8;48;110t
+\& URxvt.keysym.M-C-3: command:\e033[8;25;80t
+\& URxvt.keysym.M-C-4: command:\e033[8;48;110t
.Ve
.IP "\fBperl-ext-common\fR: \fIstring\fR" 4
.IX Item "perl-ext-common: string"
You can use keyboard shortcuts, too:
.PP
.Vb 2
-\& URxvt.keysym.M\-C\-1: command:\e033]710;suxuseuro\e007\e033]711;suxuseuro\e007
-\& URxvt.keysym.M\-C\-2: command:\e033]710;9x15bold\e007\e033]711;9x15bold\e007
+\& URxvt.keysym.M-C-1: command:\e033]710;suxuseuro\e007\e033]711;suxuseuro\e007
+\& URxvt.keysym.M-C-2: command:\e033]710;9x15bold\e007\e033]711;9x15bold\e007
.Ve
.PP
rxvt-unicode will automatically re-apply these fonts to the output so far.
background, and an almost opaque pink foreground:
.PP
.Vb 1
-\& @@RXVT_NAME@@ \-depth 32 \-bg rgba:0000/0000/0000/aaaa \-fg "[80]pink"
+\& @@RXVT_NAME@@ -depth 32 -bg rgba:0000/0000/0000/aaaa -fg "[80]pink"
.Ve
.PP
\&\fIPlease note that transparency of any kind if completely unsupported by
.IP "\fB\s-1COLORTERM\s0\fR" 4
.IX Item "COLORTERM"
Either \f(CW\*(C`rxvt\*(C'\fR, \f(CW\*(C`rxvt\-xpm\*(C'\fR, depending on whether @@RXVT_NAME@@ was
-compiled with background image support, and optionally with the added
-extension \f(CW\*(C`\-mono\*(C'\fR to indicate that rxvt-unicode runs on a monochrome
+compiled with background image support, and optionally with the added
+extension \f(CW\*(C`\-mono\*(C'\fR to indicate that rxvt-unicode runs on a monochrome
screen.
.IP "\fB\s-1COLORFGBG\s0\fR" 4
.IX Item "COLORFGBG"
\&\f(CW\*(C`default\*(C'\fR to indicate that the default-colour escape sequence is to be
used), \f(CW\*(C`bg\*(C'\fR is the colour code used as default background colour (or the
string \f(CW\*(C`default\*(C'\fR), and \f(CW\*(C`xpm\*(C'\fR is the string \f(CW\*(C`default\*(C'\fR if @@RXVT_NAME@@
-was compiled with background image support. Libraries like \f(CW\*(C`ncurses\*(C'\fR
+was compiled with background image support. Libraries like \f(CW\*(C`ncurses\*(C'\fR
and \f(CW\*(C`slang\*(C'\fR can (and do) use this information to optimize screen output.
.IP "\fB\s-1WINDOWID\s0\fR" 4
.IX Item "WINDOWID"
system)
SYNOPSIS
- urxvt [options] [-e command [ args ]]
+ rxvt [options] [-e command [ args ]]
DESCRIPTION
rxvt-unicode, version 8.4, is a colour vt102 terminal emulator intended
advantage on a machine serving many X sessions.
FREQUENTLY ASKED QUESTIONS
- 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
+ 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
<http://cvs.schmorp.de/browse/rxvt-unicode/doc/rxvt.7.html>.
RXVT-UNICODE VS. RXVT
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 urxvtd(1) (daemon) and urxvtc(1)
+ drastically reduces memory usage. See rxvtd(1) (daemon) and rxvtc(1)
(client).
It also makes technical information about escape sequences (which have
- been extended) more accessible: see urxvt(7) for technical reference
+ been extended) more accessible: see rxvt(7) for technical reference
documentation (escape sequences etc.).
OPTIONS
- The urxvt options (mostly a subset of *xterm*'s) are listed below. In
+ The rxvt 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. `urxvt
+ may not accurately reflect the version installed on your system. `rxvt
-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: `urxvt -help' gives a list of all command-line options
+ line. Note: `rxvt -help' gives a list of all command-line options
compiled into your version.
- Note that urxvt permits the resource name to be used as a long-option
+ Note that rxvt 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 Orange'.
+ than those listed. For example: `rxvt --loginShell --color1 Orange'.
The following options are available:
for inheritPixmap will be phased out in future versions of rxvt!*
*Please address all transparency related issues to Sasha Vasko at
- sasha@aftercode.net. Read the FAQ (man 7 urxvt)!*
+ sasha@aftercode.net. Read the FAQ (man 7 rxvt)!*
-fade *number*
Fade the text by the given percentage when focus is lost. Small
that certain tint colours can be applied on the server-side, thus
yielding performance gain of two orders of magnitude. These colours
are: blue, red, green, cyan, magenta, yellow, and those close to
- them; resource *tintColor*. Example:
+ them. Also pure black and pure white colors essentially mean no
+ tinting; resource *tintColor*. Example:
- urxvt -tr -tint blue -sh 40
+ rxvt -tr -tint blue -sh 40
-sh *number*
- Darken (0 .. 100) or lighten (-1 .. -100) the transparent background
+ Darken (0 .. 100) or lighten (100 .. 200) the transparent background
image in addition to (or instead of) tinting it; resource *shading*.
-blt *string*
-fg *colour*
Window foreground colour; resource foreground.
- -pixmap *file[;geom]*
+ -pixmap *file[;geom[:op1][:op2][...]]*
Compile *afterimage*: Specify image file for the background and also
optionally specify its scaling with a geometry string. Note you may
need to add quotes to avoid special shell interpretation of the ";"
prefix it with "x:". To specify an XFT-font, you need to prefix it
with "xft:", e.g.:
- urxvt -fn "xft:Bitstream Vera Sans Mono:pixelsize=15"
- urxvt -fn "9x15bold,xft:Bitstream Vera Sans Mono"
+ rxvt -fn "xft:Bitstream Vera Sans Mono:pixelsize=15"
+ rxvt -fn "9x15bold,xft:Bitstream Vera Sans Mono"
See also the question "How does rxvt-unicode choose fonts?" in the
- FAQ section of urxvt(7).
+ FAQ section of rxvt(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 urxvt window;
+ Run the command with its command-line arguments in the rxvt 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:
- urxvt -e sh -c "shell commands"
+ rxvt -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, urxvt will
+ 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 hold.
Remap a key symbol. See resource keysym.
-embed *windowid*
- Tells urxvt to embed its windows into an already-existing window,
+ Tells rxvt to embed its windows into an already-existing window,
which enables applications to easily embed a terminal.
- 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.
+ 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.
- The window will not be destroyed when urxvt exits.
+ The window will not be destroyed when rxvt exits.
- 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 whether the "-embed" option
- was used or not.
+ 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 whether 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 "urxvt -embed $xid &";
+ system "rxvt -embed $xid &";
});
-pty-fd *file descriptor*
- Tells urxvt NOT to execute any commands or create a new pty/tty pair
+ Tells rxvt NOT to execute any commands or create a new pty/tty 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.
- If this switch is given, urxvt will not create any utmp/wtmp entries
+ 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.
my $pty = new IO::Pty;
fcntl $pty, F_SETFD, 0; # clear close-on-exec
- system "urxvt -pty-fd " . (fileno $pty) . "&";
+ system "rxvt -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: `urxvt --help' gives a list of all resources (long options)
+ Note: `rxvt --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. urxvt will consult the following files/resources in order, with
+ starts. rxvt 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, 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):
+ 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):
depth: *bitdepth*
Compile *xft*: Attempt to find a visual with the given bit depth;
section.
Colours higher than 15 cannot be set using resources (yet), but can
- be changed using an escape command (see urxvt(7)).
+ be changed using an escape command (see rxvt(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.
jumpScroll: *boolean*
True: specify that jump scrolling should be used. When receiving
- lots of lines, urxvt will only scroll once a whole screen height of
+ lots of lines, rxvt will only scroll once a whole screen height of
lines has been read, resulting in fewer updates while still
displaying every received line; option -j.
- False: specify that smooth scrolling should be used. urxvt will
- force a screen refresh on each new line it received; option +j.
+ False: specify that smooth scrolling should be used. rxvt will force
+ a screen refresh on each new line it received; option +j.
skipScroll: *boolean*
True: (the default) specify that skip scrolling should be used. When
- receiving lots of lines, urxvt will only scroll once in a while
+ receiving lots of lines, rxvt will only scroll once in a while
(around 60 times per second), resulting in far fewer updates. This
- can result in urxvt not ever displaying some of the lines it
+ can result in rxvt not ever displaying some of the lines it
receives; option -ss.
False: specify that everything is to be displayed, even if the
The colour of the border around the text area and between the
scrollbar and the text.
- backgroundPixmap: *file[;geom]*
+ backgroundPixmap: *file[;geom[:op1][:op2][...]]*
Use the specified image file for the background and also optionally
- specify its scaling with a geometry string WxH+X+Y, in which "W" /
- "H" specify the horizontal/vertical scale (percent), and "X" / "Y"
- locate the image centre (percent). A scale of 0 displays the image
- with tiling. A scale of 1 displays the image without any scaling. A
- scale of 2 to 9 specifies an integer number of images in that
- direction. No image will be magnified beyond 10 times its original
- size. The maximum permitted scale is 1000. Special string of "auto"
- used as a geometry will cause image to be automatically scaled to
- match window size. If used in conjunction with -tr option -
- specified pixmap will be blended over transparency image using
- either alpha-blending, or any other blending type, specified with
- -blt "type" option. [default 0x0+50+50]
+ specify its scaling with a geometry string WxH+X+Y, (default
+ "0x0+50+50") in which "W" / "H" specify the horizontal/vertical
+ scale (percent), and "X" / "Y" locate the image centre (percent). A
+ scale of 0 displays the image with tiling. A scale of 1 displays the
+ image without any scaling. A scale of 2 to 9 specifies an integer
+ number of images in that direction. No image will be magnified
+ beyond 10 times its original size. The maximum permitted scale is
+ 1000. Additional operations can be specified after colon
+ :op1:op2.... Supported operations are:
+
+ tile force background image to be tiled and not scaled. Equivalent to 0x0,
+ propscale will scale image keeping proportions,
+ auto will scale image to match window size. Equivalent to 100x100;
+ hscale will scale image horizontally to the window size;
+ vscale will scale image vertically to the window size;
+ scale will scale image to match window size;
+ root will tile image as if it was a root window background, auto-adjusting
+ whenever terminal window moves.
+
+ If used in conjunction with -tr option, the specified pixmap will be
+ blended over transparency image using either alpha-blending, or any
+ other blending type, specified with -blt "type" option.
path: *path*
Specify the colon-delimited search path for finding background image
(whitespace delimiting is added automatically if resource is given).
When the perl selection extension is in use (the default if compiled
- in, see the urxvtperl(3) manpage), a suitable regex using these
+ in, see the rxvtperl(3) 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.
When the selection extension is not used, only ISO-8859-1 characters
can be used. If not specified, the built-in default is used:
- BACKSLASH `"'&()*,;<=>?@[]{|}
+ BACKSLASH `"'&()*,;<=>?@[]^{|}
preeditType: *style*
OverTheSpot, OffTheSpot, Root; option -pt.
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 urxvt. The default will be set-up to chose *any*
+ font lists used 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 -imfont.
instead scroll the screen up.
hold: *boolean*
- Turn on/off hold window after exit support. If enabled, urxvt will
+ 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.
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 urxvt's control sequence. For example
+ is interpreted and executed as rxvt'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
- urxvtperl(3) manpage. For example, the selection extension
- (activated via "urxvt -pe selection") listens for "selection:rot13"
- events:
+ rxvtperl(3) manpage. For example, the selection extension (activated
+ via "rxvt -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 urxvt's
+ if you overwrite the "Insert" key you will disable rxvt'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 urxvt(7) for more
+ Other things are possible, e.g. resizing (see rxvt(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 urxvtperl(3) manpage. Due to security reasons, this resource
+ See the rxvtperl(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, urxvt will first look in these directories and then in
- /usr/local/lib/urxvt/perl/. Due to security reasons, this resource
+ resource, rxvt will first look in these directories and then in
+ /opt/rxvt/lib/urxvt/perl/. Due to security reasons, this resource
will be ignored when running setuid/setgid.
- See the urxvtperl(3) manpage.
+ See the rxvtperl(3) manpage.
selection.pattern-*idx*: *perl-regex*
- Additional selection patterns, see the urxvtperl(3) manpage for
+ Additional selection patterns, see the rxvtperl(3) manpage for
details.
selection-autotransform.*idx*: *perl-transform*
- Selection auto-transform patterns, see the urxvtperl(3) manpage for
+ Selection auto-transform patterns, see the rxvtperl(3) manpage for
details.
searchable-scrollback: *keysym*
Turn on/off ISO 14755 5.2 mode (default enabled).
THE SCROLLBAR
- Lines of text that scroll off the top of the urxvt window (resource:
+ Lines of text that scroll off the top of the rxvt window (resource:
saveLines) and can be scrolled back using the scrollbar or by
- keystrokes. The normal urxvt scrollbar has arrows and its behaviour is
+ keystrokes. The normal rxvt scrollbar has arrows and its behaviour is
fairly intuitive. The xterm-scrollbar is without arrows and its
behaviour mimics that of *xterm*
removed from the selection.
Pasting:
- Pressing and releasing the Middle mouse button in an urxvt window
+ Pressing and releasing the Middle mouse button in an rxvt 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.
both scenario A and B of ISO 14755, including part 5.2.
LOGIN STAMP
- urxvt tries to write an entry into the *utmp*(5) file so that it can be
+ rxvt 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, urxvt may need to be installed setuid root on some systems or
+ feature, rxvt 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, urxvt can
+ In addition to the default foreground and background colours, rxvt 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.
0-15, as a convenient shorthand to reference the colour name of
color0-color15.
- In addition to the colours defined above, urxvt offers an additional 72
+ 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. *index = r * 16 + g * 4 + b + 16*), followed
by 8 additional shades of gray (with indices 80 to 87).
*xterm*(1) where the colours are only swapped if they have not otherwise
been specified. For example,
- urxvt -fg Black -bg White -rv
+ rxvt -fg Black -bg White -rv
would yield White on Black, while on *xterm*(1) it would yield Black
on White.
For example, the following selects an almost completely transparent red
background, and an almost opaque pink foreground:
- urxvt -depth 32 -bg rgba:0000/0000/0000/aaaa -fg "[80]pink"
+ rxvt -depth 32 -bg rgba:0000/0000/0000/aaaa -fg "[80]pink"
*Please note that transparency of any kind if completely unsupported by
the author. Don't bug him with installation questions!*
ENVIRONMENT
- urxvt sets and/or uses the following environment variables:
+ rxvt sets and/or uses the following environment variables:
TERM
Normally set to "rxvt-unicode", unless overwritten at configure
time, via resources or on the command line.
COLORTERM
- Either "rxvt", "rxvt-xpm", depending on whether urxvt was compiled
+ Either "rxvt", "rxvt-xpm", depending on whether rxvt was compiled
with background image 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 urxvt was compiled with background image support. Libraries like
+ if rxvt was compiled with background image 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 urxvt window (the toplevel
+ 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).
TERMINFO
- Set to the terminfo directory iff urxvt was configured with
+ Set to the terminfo directory iff rxvt was configured with
"--with-terminfo=PATH".
DISPLAY
- Used by urxvt to connect to the display and set to the correct
+ Used by rxvt to connect to the display and set to the correct
display in its child processes.
SHELL
The shell to be used for command execution, defaults to "/bin/sh".
RXVT_SOCKET
- The unix domain socket path used by urxvtc(1) and urxvtd(1).
+ The unix domain socket path used by rxvtc(1) and rxvtd(1).
Default $HOME/.rxvt-unicode-*<nodename*.
XENVIRONMENT
If set and accessible, gives the name of a X resource file to be
- loaded by urxvt.
+ loaded by rxvt.
FILES
/usr/lib/X11/rgb.txt
Color names.
SEE ALSO
- urxvt(7), urxvtc(1), urxvtd(1), xterm(1), sh(1), resize(1), X(1),
- pty(4), tty(4), utmp(5)
+ rxvt(7), rxvtc(1), rxvtd(1), xterm(1), sh(1), resize(1), X(1), pty(4),
+ tty(4), utmp(5)
CURRENT PROJECT COORDINATOR
Project Coordinator
<meta name="description" content="Pod documentation for RXVT REFERENCE" />
<meta name="inputfile" content="<standard input>" />
<meta name="outputfile" content="<standard output>" />
- <meta name="created" content="Sat Oct 27 14:07:34 2007" />
+ <meta name="created" content="Mon Nov 19 13:01:50 2007" />
<meta name="generator" content="Pod::Xhtml 1.57" />
<link rel="stylesheet" href="http://res.tst.eu/pod.css"/></head>
<body>
<p>And here is rxvt-unicode:</p>
<pre> libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000)
libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00002aaaaada2000)
- libc.so.6 => /lib/libc.so.6 (0x00002aaaaaeb0000)
- libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab0ee000)
- /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)
+ libc.so.6 => /lib/libc.so.6 (0x00002aaaaaeb0000)
+ libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab0ee000)
+ /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)
</pre>
<p>No large bloated libraries (of course, none were linked in statically),
</div>
<h3 id="I_can_t_get_transparency_working_wha">I can't get transparency working, what am I doing wrong?</h3>
<div id="I_can_t_get_transparency_working_wha-2">
-<p>First of all, please address all transparency related issues to Sasha Vasko at
-sasha@aftercode.net and do not bug the author about it. Also, if you can't
+<p>First of all, please address all transparency related issues to Sasha Vasko at
+sasha@aftercode.net and do not bug the author about it. Also, if you can't
get it working consider it a rite of passage: ... and you failed.</p>
<p>Here are four ways to get transparency. <strong>Do</strong> read the manpage and option
descriptions for the programs mentioned and rxvt-unicode. Really, do it!</p>
-<p>1. Use inheritPixmap:</p>
+<p>1. Use transparent mode:</p>
<pre> Esetroot wallpaper.jpg
- urxvt -ip -tint red -sh 40
+ urxvt -tr -tint red -sh 40
</pre>
<p>That works. If you think it doesn't, you lack transparency and tinting
to use effects other than tinting and shading: Just shade/tint/whatever
your picture with gimp or any other tool:</p>
<pre> convert wallpaper.jpg -blur 20x20 -modulate 30 background.jpg
- urxvt -pixmap background.jpg -pe automove-background
+ urxvt -pixmap "background.jpg;:root"
</pre>
-<p>That works. If you think it doesn't, you lack AfterImage and Perl support, or you
+<p>That works. If you think it doesn't, you lack AfterImage support, or you
are unable to read.</p>
<p>3. Use an ARGB visual:</p>
<pre> urxvt -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc
key has been assigned an escape sequence to match the vt100 for Execute
(<code>ESC [ 3 ~</code>) and is in the supplied termcap/terminfo.</p>
<p>Some other Backspace problems:</p>
-<p>some editors use termcap/terminfo,
+<p>some editors use termcap/terminfo,
some editors (vim I'm told) expect Backspace = ^H,
GNU Emacs (and Emacs-like editors) use ^H for help.</p>
<p>Perhaps someday this will all be resolved in a consistent manner.</p>
(<a href="http://www.afterstep.org/visualdoc.php?show=asimagexml">http://www.afterstep.org/visualdoc.php?show=asimagexml</a>).</p>
<p>This option also adds such eye candy as blending an image over the root
background, as well as dynamic scaling and bluring of background images.</p>
- <p>Note that with this option enabled, urxvt's memory footprint might
+ <p>Note that with this option enabled, rxvt's memory footprint might
increase by a few megabytes even if no extra features are used (mostly due
to third-party libraries used by libAI). Memory footprint may somewhat be
lowered if libAfterImage is configured without support for SVG.</p>
</dd>
<dt>--enable-transparency (default: on)</dt>
<dd>
- <p>Add support for inheriting parent backgrounds thus giving a fake
-transparency to the term.</p>
+ <p>Add support for backgrounds, creating illusion of transparency in the term.</p>
</dd>
<dt>--enable-fading (default: on)</dt>
<dd>
</dd>
<dt>--enable-iso14755 (default: on)</dt>
<dd>
- <p>Enable extended ISO 14755 support (see urxvt(1), or
+ <p>Enable extended ISO 14755 support (see rxvt(1), or
<cite>doc/rxvt.1.txt</cite>). 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.</p>
</dd>
<dt>--enable-perl (default: on)</dt>
<dd>
- <p>Enable an embedded perl interpreter. See the <strong>urxvtperl(3)</strong>
+ <p>Enable an embedded perl interpreter. See the <strong>rxvtperl(3)</strong>
manpage (<cite>doc/rxvtperl.txt</cite>) for more info on this feature, or the
files in <cite>src/perl-ext/</cite> for the extensions that are installed by
default. The perl interpreter that is used can be specified via the
.\" ========================================================================
.\"
.IX Title "@@RXVT_NAME@@ 7"
-.TH @@RXVT_NAME@@ 7 "2007-10-27" "8.4" "RXVT-UNICODE"
+.TH @@RXVT_NAME@@ 7 "2007-11-19" "8.4" "RXVT-UNICODE"
.SH "NAME"
RXVT REFERENCE \- FAQ, command sequences and other background information
.SH "SYNOPSIS"
.Vb 5
\& libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000)
\& libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00002aaaaada2000)
-\& libc.so.6 => /lib/libc.so.6 (0x00002aaaaaeb0000)
-\& libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab0ee000)
+\& libc.so.6 => /lib/libc.so.6 (0x00002aaaaaeb0000)
+\& libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab0ee000)
\& /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)
.Ve
.PP
\fII can't get transparency working, what am I doing wrong?\fR
.IX Subsection "I can't get transparency working, what am I doing wrong?"
.PP
-First of all, please address all transparency related issues to Sasha Vasko at
-sasha@aftercode.net and do not bug the author about it. Also, if you can't
+First of all, please address all transparency related issues to Sasha Vasko at
+sasha@aftercode.net and do not bug the author about it. Also, if you can't
get it working consider it a rite of passage: ... and you failed.
.PP
Here are four ways to get transparency. \fBDo\fR read the manpage and option
descriptions for the programs mentioned and rxvt\-unicode. Really, do it!
.PP
-1. Use inheritPixmap:
+1. Use transparent mode:
.PP
.Vb 2
\& Esetroot wallpaper.jpg
-\& @@URXVT_NAME@@ -ip -tint red -sh 40
+\& @@URXVT_NAME@@ -tr -tint red -sh 40
.Ve
.PP
That works. If you think it doesn't, you lack transparency and tinting
.PP
.Vb 2
\& convert wallpaper.jpg -blur 20x20 -modulate 30 background.jpg
-\& @@URXVT_NAME@@ -pixmap background.jpg -pe automove-background
+\& @@URXVT_NAME@@ -pixmap "background.jpg;:root"
.Ve
.PP
-That works. If you think it doesn't, you lack AfterImage and Perl support, or you
+That works. If you think it doesn't, you lack AfterImage support, or you
are unable to read.
.PP
3. Use an \s-1ARGB\s0 visual:
.PP
Some other Backspace problems:
.PP
-some editors use termcap/terminfo,
+some editors use termcap/terminfo,
some editors (vim I'm told) expect Backspace = ^H,
\&\s-1GNU\s0 Emacs (and Emacs-like editors) use ^H for help.
.PP
lowered if libAfterImage is configured without support for \s-1SVG\s0.
.IP "\-\-enable\-transparency (default: on)" 4
.IX Item "--enable-transparency (default: on)"
-Add support for inheriting parent backgrounds thus giving a fake
-transparency to the term.
+Add support for backgrounds, creating illusion of transparency in the term.
.IP "\-\-enable\-fading (default: on)" 4
.IX Item "--enable-fading (default: on)"
Add support for fading the text when focus is lost.
libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000)
libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00002aaaaada2000)
- libc.so.6 => /lib/libc.so.6 (0x00002aaaaaeb0000)
- libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab0ee000)
- /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)
+ libc.so.6 => /lib/libc.so.6 (0x00002aaaaaeb0000)
+ libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab0ee000)
+ /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)
No large bloated libraries (of course, none were linked in statically),
except maybe libX11 :)
Here are four ways to get transparency. Do read the manpage and option
descriptions for the programs mentioned and rxvt-unicode. Really, do it!
- 1. Use inheritPixmap:
+ 1. Use transparent mode:
Esetroot wallpaper.jpg
- urxvt -ip -tint red -sh 40
+ urxvt -tr -tint red -sh 40
That works. If you think it doesn't, you lack transparency and tinting
support, or you are unable to read.
your picture with gimp or any other tool:
convert wallpaper.jpg -blur 20x20 -modulate 30 background.jpg
- urxvt -pixmap background.jpg -pe automove-background
+ urxvt -pixmap "background.jpg;:root"
- That works. If you think it doesn't, you lack AfterImage and Perl
- support, or you are unable to read.
+ That works. If you think it doesn't, you lack AfterImage support, or you
+ are unable to read.
3. Use an ARGB visual:
root background, as well as dynamic scaling and bluring of
background images.
- Note that with this option enabled, urxvt's memory footprint might
+ Note that with this option enabled, rxvt's memory footprint might
increase by a few megabytes even if no extra features are used
(mostly due to third-party libraries used by libAI). Memory
footprint may somewhat be lowered if libAfterImage is configured
without support for SVG.
--enable-transparency (default: on)
- Add support for inheriting parent backgrounds thus giving a fake
- transparency to the term.
+ Add support for backgrounds, creating illusion of transparency in
+ the term.
--enable-fading (default: on)
Add support for fading the text when focus is lost.
verbose X error handling
--enable-iso14755 (default: on)
- Enable extended ISO 14755 support (see urxvt(1), or doc/rxvt.1.txt).
+ Enable extended ISO 14755 support (see rxvt(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: on)
- Enable an embedded perl interpreter. See the urxvtperl(3) manpage
+ Enable an embedded perl interpreter. See the rxvtperl(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.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
<head>
- <title>urxvtperl</title>
- <meta name="description" content="Pod documentation for urxvtperl" />
+ <title>rxvtperl</title>
+ <meta name="description" content="Pod documentation for rxvtperl" />
<meta name="inputfile" content="<standard input>" />
<meta name="outputfile" content="<standard output>" />
- <meta name="created" content="Sat Oct 27 14:07:34 2007" />
+ <meta name="created" content="Mon Nov 19 13:01:50 2007" />
<meta name="generator" content="Pod::Xhtml 1.57" />
<link rel="stylesheet" href="http://res.tst.eu/pod.css"/></head>
<body>
<h1 id="NAME">NAME</h1><p><a href="#TOP" class="toplink">Top</a></p>
<div id="NAME_CONTENT">
-<p>urxvtperl - rxvt-unicode's embedded perl interpreter</p>
+<p>rxvtperl - rxvt-unicode's embedded perl interpreter</p>
</div>
<h1 id="SYNOPSIS">SYNOPSIS</h1><p><a href="#TOP" class="toplink">Top</a></p>
()
}
- # start a urxvt using it:
+ # start a rxvt using it:
- urxvt --perl-lib $HOME -pe grab_test
+ rxvt --perl-lib $HOME -pe grab_test
</pre>
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 urxvtd, where
+<p>Each script will only ever be loaded once, even in rxvtd, where
scripts will be shared (but not enabled) for all terminals.</p>
<p>You can disable the embedded perl interpreter by setting both "perl-ext"
and "perl-ext-common" resources to the empty string.</p>
<h1 id="PREPACKAGED_EXTENSIONS">PREPACKAGED EXTENSIONS</h1><p><a href="#TOP" class="toplink">Top</a></p>
<div id="PREPACKAGED_EXTENSIONS_CONTENT">
<p>This section describes the extensions delivered with this release. You can
-find them in <cite>/usr/local/lib/urxvt/perl/</cite>.</p>
+find them in <cite>/opt/rxvt/lib/urxvt/perl/</cite>.</p>
<p>You can activate them like this:</p>
-<pre> urxvt -pe <extensionname>
+<pre> rxvt -pe <extensionname>
</pre>
<p>Or by adding them to the resource for extensions loaded by default:</p>
-<pre> URxvt.perl-ext-common: default,automove-background,selection-autotransform
+<pre> URxvt.perl-ext-common: default,selection-autotransform
</pre>
<dl>
<p>Other extensions can extend this popup menu by pushing a code reference
onto <code>@{ $term-</code>{option_popup_hook} }>, which gets called whenever the
popup is being displayed.</p>
- <p>It's sole argument is the popup menu, which can be modified. It should
+ <p>Its sole argument is the popup menu, which can be modified. It should
either return nothing or a string, the initial boolean value and a code
reference. The string will be used as button text and the code reference
will be called when the toggle changes, with the new boolean value as
<p>Other extensions can extend this popup menu by pushing a code reference
onto <code>@{ $term-</code>{selection_popup_hook} }>, which gets called whenever the
popup is being displayed.</p>
- <p>It's sole argument is the popup menu, which can be modified. The selection
+ <p>Its sole argument is the popup menu, which can be modified. The selection
is in <code>$_</code>, which can be used to decide whether to add something or not.
It should either return nothing or a string and a code reference. The
string will be used as button text and the code reference will be called
the selection to <code>b</code>s, but only if the selection currently contains any
<code>a</code>s:</p>
<pre> push @{ $self->{term}{selection_popup_hook} }, sub {
- /a/ ? ("a to be" => sub { s/a/b/g }
+ /a/ ? ("a to b" => sub { s/a/b/g }
: ()
};
URxvt.tabbed.tab-bg: <colour-index, default 1>
</pre>
- <p>See <i>COLOR AND GRAPHICS</i> in the urxvt(1) manpage for valid
+ <p>See <i>COLOR AND GRAPHICS</i> in the rxvt(1) manpage for valid
indices.</p>
</dd>
<dt>matcher</dt>
<dd>
<p>This (experimental) perl extension implements OnTheSpot editing. It does
not work perfectly, and some input methods don't seem to work well with
-OnTheSpot editing in general, but it seems to work at leats for SCIM and
+OnTheSpot editing in general, but it seems to work at least for SCIM and
kinput2.</p>
<p>You enable it by specifying this extension and a preedit style of
<code>OnTheSpot</code>, i.e.:</p>
-<pre> urxvt -pt OnTheSpot -pe xim-onthespot
+<pre> rxvt -pt OnTheSpot -pe xim-onthespot
</pre>
</dd>
will show or hide itself. Another press of the accelerator key will hide
or show it again.</p>
<p>Initially, the window will not be shown when using this extension.</p>
- <p>This is useful if you need a single terminal thats not using any desktop
+ <p>This is useful if you need a single terminal that is not using any desktop
space most of the time but is quickly available at the press of a key.</p>
<p>The accelerator key is grabbed regardless of any modifiers, so this
extension will actually grab a physical key just for this function.</p>
<p>If you want a quake-like animation, tell your window manager to do so
(fvwm can do it).</p>
</dd>
- <dt>automove-background</dt>
- <dd>
- <p>This is basically a very small extension that dynamically changes the
-background pixmap offset to the window position, in effect creating the
-same effect as pseudo transparency with a custom pixmap. No scaling is
-supported in this mode. Example:</p>
-<pre> urxvt -pixmap background.xpm -pe automove-background
-
-</pre>
- <p><a href="http://wiki.archlinux.org/index.php/Perl_Background_Rotation/Extensions">http://wiki.archlinux.org/index.php/Perl_Background_Rotation/Extensions</a>
-shows how this extension can be used to implement an automatically blurred
-transparent background.</p>
- </dd>
<dt>block-graphics-to-ascii</dt>
<dd>
<p>A not very useful example of filtering all text output to the terminal
<dt>remote-clipboard</dt>
<dd>
<p>Somewhat of a misnomer, this extension adds two menu entries to the
-selection popup that allows one ti run external commands to store the
+selection popup that allows one to run external commands to store the
selection somewhere and fetch it again.</p>
<p>We use it to implement a "distributed selection mechanism", which just
means that one command uploads the file to a remote server, and another
<dd>
<p>Called whenever a user-configured event is being activated (e.g. via
a <code>perl:string</code> action bound to a key, see description of the <strong>keysym</strong>
-resource in the urxvt(1) manpage).</p>
+resource in the rxvt(1) manpage).</p>
<p>The event is simply the action string. This interface is assumed to change
slightly in the future.</p>
</dd>
<dt>$term->destroy</dt>
<dd>
<p>Destroy the terminal object (close the window, free resources
-etc.). Please note that urxvt will not exit as long as any event
+etc.). Please note that rxvt will not exit as long as any event
watchers (timers, io watchers) are still active.</p>
</dd>
<dt>$term->exec_async ($cmd[, @args])</dt>
<dt>$success = $term->parse_keysym ($keysym_spec, $command_string)</dt>
<dd>
<p>Adds a keymap translation exactly as specified via a resource. See the
-<code>keysym</code> resource in the urxvt(1) manpage.</p>
+<code>keysym</code> resource in the rxvt(1) manpage.</p>
</dd>
<dt>$rend = $term->rstyle ([$new_rstyle])</dt>
<dd>
->cb (sub {
$term->{overlay}->set (0, 0,
sprintf "%2d:%02d:%02d", (localtime urxvt::NOW)[2,1,0]);
- });
+ });
</pre>
<dl>
$term->{iow} = urxvt::iow
->new
->fd (fileno $term->{socket})
- ->events (urxvt::EVENT_READ)
+ ->events (urxvt::EV_READ)
->start
->cb (sub {
my ($iow, $revents) = @_;
<dt>$iow = $iow->events ($eventmask)</dt>
<dd>
<p>Set the event mask to watch. The only allowed values are
-<code>urxvt::EVENT_READ</code> and <code>urxvt::EVENT_WRITE</code>, which might be ORed
-together, or <code>urxvt::EVENT_NONE</code>.</p>
+<code>urxvt::EV_READ</code> and <code>urxvt::EV_WRITE</code>, which might be ORed
+together, or <code>urxvt::EV_NONE</code>.</p>
</dd>
<dt>$iow = $iow->start</dt>
<dd>
->cb (sub {
my ($pw, $exit_status) = @_;
...
- });
+ });
</pre>
<dl>
.\" ========================================================================
.\"
.IX Title "@@RXVT_NAME@@ 3"
-.TH @@RXVT_NAME@@ 3 "2007-10-27" "8.4" "RXVT-UNICODE"
+.TH @@RXVT_NAME@@ 3 "2007-11-19" "8.4" "RXVT-UNICODE"
.SH "NAME"
@@RXVT_NAME@@perl \- rxvt\-unicode's embedded perl interpreter
.SH "SYNOPSIS"
Or by adding them to the resource for extensions loaded by default:
.PP
.Vb 1
-\& URxvt.perl-ext-common: default,automove-background,selection-autotransform
+\& URxvt.perl-ext-common: default,selection-autotransform
.Ve
.IP "selection (enabled by default)" 4
.IX Item "selection (enabled by default)"
onto \f(CW\*(C`@{ $term\-\*(C'\fR{option_popup_hook} }>, which gets called whenever the
popup is being displayed.
.Sp
-It's sole argument is the popup menu, which can be modified. It should
+Its sole argument is the popup menu, which can be modified. It should
either return nothing or a string, the initial boolean value and a code
reference. The string will be used as button text and the code reference
will be called when the toggle changes, with the new boolean value as
onto \f(CW\*(C`@{ $term\-\*(C'\fR{selection_popup_hook} }>, which gets called whenever the
popup is being displayed.
.Sp
-It's sole argument is the popup menu, which can be modified. The selection
+Its sole argument is the popup menu, which can be modified. The selection
is in \f(CW$_\fR, which can be used to decide whether to add something or not.
It should either return nothing or a string and a code reference. The
string will be used as button text and the code reference will be called
.Sp
.Vb 4
\& push @{ $self->{term}{selection_popup_hook} }, sub {
-\& /a/ ? ("a to be" => sub { s/a/b/g }
+\& /a/ ? ("a to b" => sub { s/a/b/g }
\& : ()
\& };
.Ve
.IX Item "xim-onthespot"
This (experimental) perl extension implements OnTheSpot editing. It does
not work perfectly, and some input methods don't seem to work well with
-OnTheSpot editing in general, but it seems to work at leats for \s-1SCIM\s0 and
+OnTheSpot editing in general, but it seems to work at least for \s-1SCIM\s0 and
kinput2.
.Sp
You enable it by specifying this extension and a preedit style of
.Sp
Initially, the window will not be shown when using this extension.
.Sp
-This is useful if you need a single terminal thats not using any desktop
+This is useful if you need a single terminal that is not using any desktop
space most of the time but is quickly available at the press of a key.
.Sp
The accelerator key is grabbed regardless of any modifiers, so this
.Sp
If you want a quake-like animation, tell your window manager to do so
(fvwm can do it).
-.IP "automove-background" 4
-.IX Item "automove-background"
-This is basically a very small extension that dynamically changes the
-background pixmap offset to the window position, in effect creating the
-same effect as pseudo transparency with a custom pixmap. No scaling is
-supported in this mode. Example:
-.Sp
-.Vb 1
-\& @@RXVT_NAME@@ -pixmap background.xpm -pe automove-background
-.Ve
-.Sp
-<http://wiki.archlinux.org/index.php/Perl_Background_Rotation/Extensions>
-shows how this extension can be used to implement an automatically blurred
-transparent background.
.IP "block-graphics-to-ascii" 4
.IX Item "block-graphics-to-ascii"
A not very useful example of filtering all text output to the terminal
.IP "remote-clipboard" 4
.IX Item "remote-clipboard"
Somewhat of a misnomer, this extension adds two menu entries to the
-selection popup that allows one ti run external commands to store the
+selection popup that allows one to run external commands to store the
selection somewhere and fetch it again.
.Sp
We use it to implement a \*(L"distributed selection mechanism\*(R", which just
\& $term->{iow} = urxvt::iow
\& ->new
\& ->fd (fileno $term->{socket})
-\& ->events (urxvt::EVENT_READ)
+\& ->events (urxvt::EV_READ)
\& ->start
\& ->cb (sub {
\& my ($iow, $revents) = @_;
.el .IP "$iow = \f(CW$iow\fR\->events ($eventmask)" 4
.IX Item "$iow = $iow->events ($eventmask)"
Set the event mask to watch. The only allowed values are
-\&\f(CW\*(C`urxvt::EVENT_READ\*(C'\fR and \f(CW\*(C`urxvt::EVENT_WRITE\*(C'\fR, which might be ORed
-together, or \f(CW\*(C`urxvt::EVENT_NONE\*(C'\fR.
+\&\f(CW\*(C`urxvt::EV_READ\*(C'\fR and \f(CW\*(C`urxvt::EV_WRITE\*(C'\fR, which might be ORed
+together, or \f(CW\*(C`urxvt::EV_NONE\*(C'\fR.
.ie n .IP "$iow = $iow\->start" 4
.el .IP "$iow = \f(CW$iow\fR\->start" 4
.IX Item "$iow = $iow->start"
NAME
- urxvtperl - rxvt-unicode's embedded perl interpreter
+ rxvtperl - rxvt-unicode's embedded perl interpreter
SYNOPSIS
# create a file grab_test in $HOME:
()
}
- # start a urxvt using it:
+ # start a rxvt using it:
- urxvt --perl-lib $HOME -pe grab_test
+ rxvt --perl-lib $HOME -pe grab_test
DESCRIPTION
Every time 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 urxvtd, where scripts
+ Each script will only ever be loaded once, even in rxvtd, where scripts
will be shared (but not enabled) for all terminals.
You can disable the embedded perl interpreter by setting both "perl-ext"
PREPACKAGED EXTENSIONS
This section describes the extensions delivered with this release. You
- can find them in /usr/local/lib/urxvt/perl/.
+ can find them in /opt/rxvt/lib/urxvt/perl/.
You can activate them like this:
- urxvt -pe <extensionname>
+ rxvt -pe <extensionname>
Or by adding them to the resource for extensions loaded by default:
- URxvt.perl-ext-common: default,automove-background,selection-autotransform
+ URxvt.perl-ext-common: default,selection-autotransform
selection (enabled by default)
(More) intelligent selection. This extension tries to be more
reference onto "@{ $term-"{option_popup_hook} }>, which gets called
whenever the popup is being displayed.
- It's sole argument is the popup menu, which can be modified. It
+ Its sole argument is the popup menu, which can be modified. It
should either return nothing or a string, the initial boolean value
and a code reference. The string will be used as button text and the
code reference will be called when the toggle changes, with the new
reference onto "@{ $term-"{selection_popup_hook} }>, which gets
called whenever the popup is being displayed.
- It's sole argument is the popup menu, which can be modified. The
+ Its sole argument is the popup menu, which can be modified. The
selection is in $_, which can be used to decide whether to add
something or not. It should either return nothing or a string and a
code reference. The string will be used as button text and the code
any "a"s:
push @{ $self->{term}{selection_popup_hook} }, sub {
- /a/ ? ("a to be" => sub { s/a/b/g }
+ /a/ ? ("a to b" => sub { s/a/b/g }
: ()
};
URxvt.tabbed.tab-fg: <colour-index, default 0>
URxvt.tabbed.tab-bg: <colour-index, default 1>
- See *COLOR AND GRAPHICS* in the urxvt(1) manpage for valid indices.
+ See *COLOR AND GRAPHICS* in the rxvt(1) manpage for valid indices.
matcher
Uses per-line display filtering ("on_line_update") to underline text
This (experimental) perl extension implements OnTheSpot editing. It
does not work perfectly, and some input methods don't seem to work
well with OnTheSpot editing in general, but it seems to work at
- leats for SCIM and kinput2.
+ least for SCIM and kinput2.
You enable it by specifying this extension and a preedit style of
"OnTheSpot", i.e.:
- urxvt -pt OnTheSpot -pe xim-onthespot
+ rxvt -pt OnTheSpot -pe xim-onthespot
kuake<hotkey>
A very primitive quake-console-like extension. It was inspired by a
Initially, the window will not be shown when using this extension.
- This is useful if you need a single terminal thats not using any
+ This is useful if you need a single terminal that is not using any
desktop space most of the time but is quickly available at the press
of a key.
If you want a quake-like animation, tell your window manager to do
so (fvwm can do it).
- automove-background
- This is basically a very small extension that dynamically changes
- the background pixmap offset to the window position, in effect
- creating the same effect as pseudo transparency with a custom
- pixmap. No scaling is supported in this mode. Example:
-
- urxvt -pixmap background.xpm -pe automove-background
-
- <http://wiki.archlinux.org/index.php/Perl_Background_Rotation/Extens
- ions> shows how this extension can be used to implement an
- automatically blurred transparent background.
-
block-graphics-to-ascii
A not very useful example of filtering all text output to the
terminal by replacing all line-drawing characters (U+2500 .. U+259F)
remote-clipboard
Somewhat of a misnomer, this extension adds two menu entries to the
- selection popup that allows one ti run external commands to store
+ selection popup that allows one to run external commands to store
the selection somewhere and fetch it again.
We use it to implement a "distributed selection mechanism", which
on_user_command $term, $string
Called whenever a user-configured event is being activated (e.g. via
a "perl:string" action bound to a key, see description of the keysym
- resource in the urxvt(1) manpage).
+ resource in the rxvt(1) manpage).
The event is simply the action string. This interface is assumed to
change slightly in the future.
$term->destroy
Destroy the terminal object (close the window, free resources etc.).
- Please note that urxvt will not exit as long as any event watchers
+ Please note that rxvt will not exit as long as any event watchers
(timers, io watchers) are still active.
$term->exec_async ($cmd[, @args])
$success = $term->parse_keysym ($keysym_spec, $command_string)
Adds a keymap translation exactly as specified via a resource. See
- the "keysym" resource in the urxvt(1) manpage.
+ the "keysym" resource in the rxvt(1) manpage.
$rend = $term->rstyle ([$new_rstyle])
Return and optionally change the current rendition. Text that is
->cb (sub {
$term->{overlay}->set (0, 0,
sprintf "%2d:%02d:%02d", (localtime urxvt::NOW)[2,1,0]);
- });
+ });
$timer = new urxvt::timer
Create a new timer object in started state. It is scheduled to fire
$term->{iow} = urxvt::iow
->new
->fd (fileno $term->{socket})
- ->events (urxvt::EVENT_READ)
+ ->events (urxvt::EV_READ)
->start
->cb (sub {
my ($iow, $revents) = @_;
$iow = $iow->events ($eventmask)
Set the event mask to watch. The only allowed values are
- "urxvt::EVENT_READ" and "urxvt::EVENT_WRITE", which might be ORed
- together, or "urxvt::EVENT_NONE".
+ "urxvt::EV_READ" and "urxvt::EV_WRITE", which might be ORed
+ together, or "urxvt::EV_NONE".
$iow = $iow->start
Start watching for requested events on the given handle.
->cb (sub {
my ($pw, $exit_status) = @_;
...
- });
+ });
$pw = new urxvt::pw
Create a new process watcher in stopped state.
rxvtfont.o: rxvtutil.h rxvtfont.h rxvttoolkit.h ev_cpp.h callback.h salloc.h
rxvtfont.o: libptytty.h rxvtperl.h hookinc.h background.h rsinc.h
rxvtfont.o: table/linedraw.h
-rxvtperl.o: ../config.h rxvt.h rxvtlib.h optinc.h feature.h encoding.h
-rxvtperl.o: rxvtutil.h rxvtfont.h rxvttoolkit.h ev_cpp.h callback.h salloc.h
-rxvtperl.o: libptytty.h rxvtperl.h hookinc.h background.h rsinc.h keyboard.h
-rxvtperl.o: perlxsi.c ./iom_perl.h
+rxvtperl.o: ../config.h ev_cpp.h rxvt.h rxvtlib.h optinc.h feature.h
+rxvtperl.o: encoding.h rxvtutil.h rxvtfont.h rxvttoolkit.h callback.h
+rxvtperl.o: salloc.h libptytty.h rxvtperl.h hookinc.h background.h rsinc.h
+rxvtperl.o: keyboard.h perlxsi.c ./iom_perl.h
rxvttoolkit.o: ../config.h rxvt.h rxvtlib.h optinc.h feature.h encoding.h
rxvttoolkit.o: rxvtutil.h rxvtfont.h rxvttoolkit.h ev_cpp.h callback.h
rxvttoolkit.o: salloc.h libptytty.h rxvtperl.h hookinc.h background.h rsinc.h
rxvtfont.lo: rxvtutil.h rxvtfont.h rxvttoolkit.h ev_cpp.h callback.h salloc.h
rxvtfont.lo: libptytty.h rxvtperl.h hookinc.h background.h rsinc.h
rxvtfont.lo: table/linedraw.h
-rxvtperl.lo: ../config.h rxvt.h rxvtlib.h optinc.h feature.h encoding.h
-rxvtperl.lo: rxvtutil.h rxvtfont.h rxvttoolkit.h ev_cpp.h callback.h salloc.h
-rxvtperl.lo: libptytty.h rxvtperl.h hookinc.h background.h rsinc.h keyboard.h
-rxvtperl.lo: perlxsi.c ./iom_perl.h
+rxvtperl.lo: ../config.h ev_cpp.h rxvt.h rxvtlib.h optinc.h feature.h
+rxvtperl.lo: encoding.h rxvtutil.h rxvtfont.h rxvttoolkit.h callback.h
+rxvtperl.lo: salloc.h libptytty.h rxvtperl.h hookinc.h background.h rsinc.h
+rxvtperl.lo: keyboard.h perlxsi.c ./iom_perl.h
rxvttoolkit.lo: ../config.h rxvt.h rxvtlib.h optinc.h feature.h encoding.h
rxvttoolkit.lo: rxvtutil.h rxvtfont.h rxvttoolkit.h ev_cpp.h callback.h
rxvttoolkit.lo: salloc.h libptytty.h rxvtperl.h hookinc.h background.h