=> when setting the constraints, the wm might (correctly)
resize the outer window, which might result in a smaller window overall.
or something like that. guys, send me a patch.
+TODO: zero scorllback buffer should free memory
+TODO: debian integration
WISH: skipscroll option
WISH: selection-color-pair instead of reverse video
WISH: load system-wide config file even if we don't have one
WISH: look into XAddConnectionWatch, does anybody need that?
WISH: anyevent mouse notification / manage MotionMask better.
-WISH: http://www120.pair.com/mccarthy/nextstep/intro.htmld/Workspace.html is the correct nextstep look.
+WISH: http://www120.pair.com/mccarthy/nextstep/intro.htmld/Workspace.html is the correct nextstep scrollbar look.
DUMB: support tex fonts
-7.8
-TODO: zero scorllback buffer should free memory
-TODO: debian integration
+7.8 Mon Jul 17 21:00:46 CEST 2006
- INCOMPATIBLE CHANGE: this version will always read ~/.Xdefaults,
earlier versions only read it if display-resources (usually from
.Xresources) are not set. This avoids the #1 FAQ ("why isn't my
verbose X error handling
--enable-iso14755 (default: on)
- Enable extended ISO 14755 support (see rxvt(1), or doc/rxvt.1.txt).
+ Enable extended ISO 14755 support (see urxvt(1), or doc/rxvt.1.txt).
Basic support (section 5.1) is enabled by "--enable-frills", while
support for 5.2, 5.3 and 5.4 is enabled with this switch.
Add support to have the pointer disappear when typing or inactive.
--enable-perl (default: on)
- Enable an embedded perl interpreter. See the rxvtperl(3) manpage
+ Enable an embedded perl interpreter. See the urxvtperl(3) manpage
(doc/rxvtperl.txt) for more info on this feature, or the files in
src/perl-ext/ for the extensions that are installed by default. The
perl interpreter that is used can be specified via the "PERL"
</p>
<hr />
<h1><a name="synopsis">SYNOPSIS</a></h1>
-<p><strong>rxvt</strong> [options] [-e command [ args ]]</p>
+<p><strong>urxvt</strong> [options] [-e command [ args ]]</p>
<p>
</p>
<hr />
<h1><a name="description">DESCRIPTION</a></h1>
-<p><strong>rxvt-unicode</strong>, version <strong>7.7</strong>, is a colour vt102 terminal
+<p><strong>rxvt-unicode</strong>, version <strong>7.8</strong>, is a colour vt102 terminal
emulator intended as an <em>xterm</em>(1) replacement for users who do not
require features such as Tektronix 4014 emulation and toolkit-style
configurability. As a result, <strong>rxvt-unicode</strong> uses much less swap space --
</p>
<hr />
<h1><a name="frequently_asked_questions">FREQUENTLY ASKED QUESTIONS</a></h1>
-<p>See <code>rxvt(7)</code> (try <code>man 7 rxvt</code>) for a list of
+<p>See <code>urxvt(7)</code> (try <code>man 7 urxvt</code>) for a list of
frequently asked questions and answer to them and some common
problems. That document is also accessible on the World-Wide-Web at
<a href="http://cvs.schmorp.de/browse/*checkout*/rxvt-unicode/doc/rxvt.7.html">http://cvs.schmorp.de/browse/*checkout*/rxvt-unicode/doc/rxvt.7.html</a>.</p>
without most of its features to get a lean binary. It also comes with
a client/daemon pair that lets you open any number of terminal windows
from within a single process, which makes startup time very fast and
-drastically reduces memory usage. See <code>rxvtd(1)</code> (daemon) and
-<code>rxvtc(1)</code> (client).</p>
+drastically reduces memory usage. See <code>urxvtd(1)</code> (daemon) and
+<code>urxvtc(1)</code> (client).</p>
<p>It also makes technical information about escape sequences (which have
-been extended) easier accessible: see <code>rxvt(7)</code> for technical
+been extended) easier accessible: see <code>urxvt(7)</code> for technical
reference documentation (escape sequences etc.).</p>
<p>
</p>
<hr />
<h1><a name="options">OPTIONS</a></h1>
-<p>The <strong>rxvt</strong> options (mostly a subset of <em>xterm</em>'s) are listed
+<p>The <strong>urxvt</strong> options (mostly a subset of <em>xterm</em>'s) are listed
below. In keeping with the smaller-is-better philosophy, options may be
eliminated or default values chosen at compile-time, so options and
defaults listed may not accurately reflect the version installed on
-your system. `rxvt -h' gives a list of major compile-time options on
+your system. `urxvt -h' gives a list of major compile-time options on
the <em>Options</em> line. Option descriptions may be prefixed with which
compile option each is dependent upon. e.g. `Compile <em>XIM</em>:' requires
-<em>XIM</em> on the <em>Options</em> line. Note: `rxvt -help' gives a list of all
+<em>XIM</em> on the <em>Options</em> line. Note: `urxvt -help' gives a list of all
command-line options compiled into your version.</p>
-<p>Note that <strong>rxvt</strong> permits the resource name to be used as a
+<p>Note that <strong>urxvt</strong> permits the resource name to be used as a
long-option (--/++ option) so the potential command-line options are
-far greater than those listed. For example: `rxvt --loginShell --color1
+far greater than those listed. For example: `urxvt --loginShell --color1
Orange'.</p>
<p>The following options are available:</p>
<dl>
</dd>
<dd>
<pre>
- rxvt -tr -tint blue -sh 40</pre>
+ urxvt -tr -tint blue -sh 40</pre>
</dd>
</li>
<dt><strong><a name="item__2dsh"><strong>-sh</strong></a></strong>
</dd>
<dd>
<pre>
- rxvt -fn "xft:Bitstream Vera Sans Mono:pixelsize=15"
- rxvt -fn "9x15bold,xft:Bitstream Vera Sans Mono"</pre>
+ urxvt -fn "xft:Bitstream Vera Sans Mono:pixelsize=15"
+ urxvt -fn "9x15bold,xft:Bitstream Vera Sans Mono"</pre>
</dd>
<dd>
<p>See also the question ``How does rxvt-unicode choose fonts?'' in the FAQ
-section of rxvt(7).</p>
+section of urxvt(7).</p>
</dd>
</li>
<dt><strong><a name="item__2dfb_fontlist"><strong>-fb</strong> <em>fontlist</em></a></strong>
<dt><strong><a name="item__2de_command__5barguments_5d"><strong>-e</strong> <em>command [arguments]</em></a></strong>
<dd>
-<p>Run the command with its command-line arguments in the <strong>rxvt</strong>
+<p>Run the command with its command-line arguments in the <strong>urxvt</strong>
window; also sets the window title and icon name to be the basename of
the program being executed if neither <em>-title</em> (<em>-T</em>) nor <em>-n</em> are
given on the command line. If this option is used, it must be the last
</dd>
<dd>
<pre>
- rxvt -e sh -c "shell commands"</pre>
+ urxvt -e sh -c "shell commands"</pre>
</dd>
</li>
<dt><strong><a name="item__2dtitle_text"><strong>-title</strong> <em>text</em></a></strong>
<dt><strong><a name="item__2dhold_7c_2bhold"><strong>-hold</strong>|<strong>+hold</strong></a></strong>
<dd>
-<p>Turn on/off hold window after exit support. If enabled, rxvt
+<p>Turn on/off hold window after exit support. If enabled, urxvt
will not immediately destroy its window when the program executed within
it exits. Instead, it will wait till it is being killed or closed by the
user; resource <strong>hold</strong>.</p>
<dt><strong><a name="item__2dembed_windowid"><strong>-embed</strong> <em>windowid</em></a></strong>
<dd>
-<p>Tells rxvt to embed its windows into an already-existing window,
+<p>Tells urxvt to embed its windows into an already-existing window,
which enables applications to easily embed a terminal.</p>
</dd>
<dd>
-<p>Right now, rxvt will first unmap/map the specified window, so it
-shouldn't be a top-level window. rxvt will also reconfigure it
+<p>Right now, urxvt will first unmap/map the specified window, so it
+shouldn't be a top-level window. urxvt will also reconfigure it
quite a bit, so don't expect it to keep some specific state. It's best to
-create an extra subwindow for rxvt and leave it alone.</p>
+create an extra subwindow for urxvt and leave it alone.</p>
</dd>
<dd>
-<p>The window will not be destroyed when rxvt exits.</p>
+<p>The window will not be destroyed when urxvt exits.</p>
</dd>
<dd>
-<p>It might be useful to know that rxvt will not close file
+<p>It might be useful to know that urxvt will not close file
descriptors passed to it (except for stdin/out/err, of course), so you
can use file descriptors to communicate with the programs within the
terminal. This works regardless of wether the <code>-embed</code> option was used or
my $rxvt = new Gtk2::Socket;
$rxvt->signal_connect_after (realize => sub {
my $xid = $_[0]->window->get_xid;
- system "rxvt -embed $xid &";
+ system "urxvt -embed $xid &";
});</pre>
</dd>
</li>
<dt><strong><a name="item__2dpty_2dfd_file_descriptor"><strong>-pty-fd</strong> <em>file descriptor</em></a></strong>
<dd>
-<p>Tells rxvt NOT to execute any commands or create a new pty/tty
+<p>Tells urxvt NOT to execute any commands or create a new pty/tty
pair but instead use the given filehandle as the tty master. This is
-useful if you want to drive rxvt as a generic terminal emulator
+useful if you want to drive urxvt as a generic terminal emulator
without having to run a program within it.</p>
</dd>
<dd>
-<p>If this switch is given, rxvt will not create any utmp/wtmp
+<p>If this switch is given, urxvt will not create any utmp/wtmp
entries and will not tinker with pty/tty permissions - you have to do that
yourself if you want that.</p>
</dd>
<pre>
my $pty = new IO::Pty;
fcntl $pty, F_SETFD, 0; # clear close-on-exec
- system "rxvt -pty-fd " . (fileno $pty) . "&";
+ system "urxvt -pty-fd " . (fileno $pty) . "&";
close $pty;</pre>
</dd>
<dd>
</p>
<hr />
<h1><a name="resources__available_also_as_longoptions_">RESOURCES (available also as long-options)</a></h1>
-<p>Note: `rxvt --help' gives a list of all resources (long
+<p>Note: `urxvt --help' gives a list of all resources (long
options) compiled into your version.</p>
<p>You can set and change the resources using X11 tools like <strong>xrdb</strong>. Many
distribution do also load settings from the <strong>~/.Xresources</strong> file when X
-starts. rxvt will consult the following files/resources in order,
+starts. urxvt will consult the following files/resources in order,
with later settings overwriting earlier ones:</p>
<pre>
1. system-wide app-defaults file, either locale-dependent OR global
3. RESOURCE_MANAGER property on root-window OR $HOME/.Xdefaults
4. SCREEN_RESOURCES for the current screen
5. $XENVIRONMENT file OR $HOME/.Xdefaults-<nodename></pre>
-<p>Note that when reading X resources, <strong>rxvt</strong> recognizes two class
+<p>Note that when reading X resources, <strong>urxvt</strong> recognizes two class
names: <strong>Rxvt</strong> and <strong>URxvt</strong>. The class name <strong>Rxvt</strong> allows resources
-common to both <strong>rxvt</strong> and the original <em>rxvt</em> to be easily
+common to both <strong>urxvt</strong> and the original <em>rxvt</em> to be easily
configured, while the class name <strong>URxvt</strong> allows resources unique to
-<strong>rxvt</strong>, to be shared between different <strong>rxvt</strong>
+<strong>urxvt</strong>, to be shared between different <strong>urxvt</strong>
configurations. If no resources are specified, suitable defaults will
be used. Command-line arguments can be used to override resource
settings. The following resources are supported (you might want to
-check the <code>rxvtperl(3)</code> manpage for additional settings by perl
+check the <code>urxvtperl(3)</code> manpage for additional settings by perl
extensions not documented here):</p>
<dl>
<dt><strong><a name="item_depth_3a_bitdepth"><strong>depth:</strong> <em>bitdepth</em></a></strong>
</dd>
<dd>
<p>Colours higher than 15 cannot be set using resources (yet), but can be
-changed using an escape command (see rxvt(7)).</p>
+changed using an escape command (see urxvt(7)).</p>
</dd>
<dd>
<p>Colours 16-79 form a standard 4x4x4 colour cube (the same as xterm with
</dd>
<dd>
<p>When the selection extension is in use (the default if compiled in, see
-the <code>rxvtperl(3)</code> manpage), a suitable regex using these characters
+the <code>urxvtperl(3)</code> manpage), a suitable regex using these characters
will be created (if the resource exists, otherwise, no regex will be
created). In this mode, characters outside ISO-8859-1 can be used.</p>
</dd>
<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 rxvt. The default will be set-up to chose *any* suitable found
+in urxvt. The default will be set-up to chose *any* suitable found
found, preferably one or two pixels differing in size to the base font.
option <strong>-imfont</strong>.</p>
</dd>
<dt><strong><a name="item_hold_3a_boolean"><strong>hold</strong>: <em>boolean</em></a></strong>
<dd>
-<p>Turn on/off hold window after exit support. If enabled, rxvt
+<p>Turn on/off hold window after exit support. If enabled, urxvt
will not immediately destroy its window when the program executed within
it exits. Instead, it will wait till it is being killed or closed by the
user.</p>
<dd>
<p>Please note that you need to double the <code>\</code> in resource files, as
Xlib itself does its own de-escaping (you can use <code>\033</code> instead of
-<code>\e</code> (and so on), which will work with both Xt and rxvt's own
+<code>\e</code> (and so on), which will work with both Xt and urxvt's own
processing).</p>
</dd>
<dd>
</dd>
<dd>
<p>If <em>string</em> takes the form of <code>command:STRING</code>, the specified <strong>STRING</strong>
-is interpreted and executed as rxvt's control sequence. For
+is interpreted and executed as urxvt's control sequence. For
example the following means ``change the current locale to <code>zh_CN.GBK</code>
when Control-Meta-c is being pressed'':</p>
</dd>
</dd>
<dd>
<p>If <em>string</em> takes the form <code>perl:STRING</code>, then the specified <strong>STRING</strong>
-is passed to the <code>on_keyboard_command</code> perl handler. See the <code>rxvtperl(3)</code>
+is passed to the <code>on_keyboard_command</code> perl handler. See the <code>urxvtperl(3)</code>
manpage. For example, the <em>selection</em> extension (activated via
-<code>rxvt -pe selection</code>) listens for <code>selection:rot13</code> events:</p>
+<code>urxvt -pe selection</code>) listens for <code>selection:rot13</code> events:</p>
</dd>
<dd>
<pre>
</dd>
<dd>
<p>Unfortunately, this will override built-in key mappings. For example
-if you overwrite the <code>Insert</code> key you will disable rxvt's
+if you overwrite the <code>Insert</code> key you will disable urxvt's
<code>Shift-Insert</code> mapping. To re-enable that, you can poke ``holes'' into the
user-defined keymap using the <code>builtin:</code> replacement:</p>
</dd>
URxvt.keysym.M-C-2: command:\033]50;9x15bold\007</pre>
</dd>
<dd>
-<p>Other things are possible, e.g. resizing (see <code>rxvt(7)</code> for more
+<p>Other things are possible, e.g. resizing (see <code>urxvt(7)</code> for more
info):</p>
</dd>
<dd>
<dd>
<p>Perl code to be evaluated when all extensions have been registered. See
-the <code>rxvtperl(3)</code> manpage. Due to security reasons, this resource
+the <code>urxvtperl(3)</code> manpage. Due to security reasons, this resource
will be ignored when running setuid/setgid.</p>
</dd>
</li>
<dd>
<p>Colon-separated list of additional directories that hold extension
scripts. When looking for extensions specified by the <code>perl</code> resource,
-rxvt will first look in these directories and then in
-<em>/opt/rxvt/lib/urxvt/perl/</em>. Due to security reasons, this resource
+urxvt will first look in these directories and then in
+<em>/usr/local/lib/urxvt/perl/</em>. Due to security reasons, this resource
will be ignored when running setuid/setgid.</p>
</dd>
<dd>
-<p>See the <code>rxvtperl(3)</code> manpage.</p>
+<p>See the <code>urxvtperl(3)</code> manpage.</p>
</dd>
</li>
<dt><strong><a name="item_selection_2epattern_2didx_3a_perl_2dregex"><strong>selection.pattern-<em>idx</em> </strong>>: <em>perl-regex</em></a></strong>
<dd>
-<p>Additional selection patterns, see the <code>rxvtperl(3)</code> manpage for
+<p>Additional selection patterns, see the <code>urxvtperl(3)</code> manpage for
details.</p>
</dd>
</li>
<dt><strong><a name="item_selection_2dautotransform_2eidx_3a_perl_2dtransfor"><strong>selection-autotransform.<em>idx</em> </strong>>: <em>perl-transform</em></a></strong>
<dd>
-<p>Selection auto-transform patterns, see the <code>rxvtperl(3)</code> manpage
+<p>Selection auto-transform patterns, see the <code>urxvtperl(3)</code> manpage
for details.</p>
</dd>
</li>
</p>
<hr />
<h1><a name="the_scrollbar">THE SCROLLBAR</a></h1>
-<p>Lines of text that scroll off the top of the <strong>rxvt</strong> window
+<p>Lines of text that scroll off the top of the <strong>urxvt</strong> window
(resource: <strong>saveLines</strong>) and can be scrolled back using the scrollbar
-or by keystrokes. The normal <strong>rxvt</strong> scrollbar has arrows and
+or by keystrokes. The normal <strong>urxvt</strong> scrollbar has arrows and
its behaviour is fairly intuitive. The <strong>xterm-scrollbar</strong> is without
arrows and its behaviour mimics that of <em>xterm</em></p>
<p>Scroll down with <strong>Button1</strong> (<strong>xterm-scrollbar</strong>) or <strong>Shift-Next</strong>.
<dt><strong><a name="item_insertion_3a"><strong>Insertion</strong>:</a></strong>
<dd>
-<p>Pressing and releasing the Middle mouse button in an <strong>rxvt</strong>
+<p>Pressing and releasing the Middle mouse button in an <strong>urxvt</strong>
window causes the value of the PRIMARY selection (or CLIPBOARD with the
Meta modifier) to be inserted as if it had been typed on the keyboard.</p>
</dd>
</p>
<hr />
<h1><a name="login_stamp">LOGIN STAMP</a></h1>
-<p><strong>rxvt</strong> tries to write an entry into the <em>utmp</em>(5) file so that
+<p><strong>urxvt</strong> tries to write an entry into the <em>utmp</em>(5) file so that
it can be seen via the <em>who(1)</em> command, and can accept messages. To
-allow this feature, <strong>rxvt</strong> may need to be installed setuid root
+allow this feature, <strong>urxvt</strong> may need to be installed setuid root
on some systems or setgid to root or to some other group on others.</p>
<p>
</p>
<hr />
<h1><a name="colors_and_graphics">COLORS AND GRAPHICS</a></h1>
<p>In addition to the default foreground and background colours,
-<strong>rxvt</strong> can display up to 16 colours (8 ANSI colours plus
+<strong>urxvt</strong> can display up to 16 colours (8 ANSI colours plus
high-intensity bold/blink versions of the same). Here is a list of the
colours with their names.</p>
<table>
<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, rxvt offers an
+<p>In addition to the colours defined above, urxvt offers an
additional 72 colours. The first 64 of those (with indices 16 to 79)
consist of a 4*4*4 RGB colour cube (i.e. <em>index = r * 16 + g * 4 + b +
16</em>), followed by 8 additional shades of gray (with indices 80 to 87).</p>
<em>xterm</em>(1) where the colours are only swapped if they have not otherwise
been specified. For example,</p>
<dl>
-<dt><strong><a name="item_rxvt__2dfg_black__2dbg_white__2drv"><strong>rxvt -fg Black -bg White -rv</strong></a></strong>
+<dt><strong><a name="item_urxvt__2dfg_black__2dbg_white__2drv"><strong>urxvt -fg Black -bg White -rv</strong></a></strong>
<dd>
<p>would yield White on Black, while on <em>xterm</em>(1) it would yield Black
<p>For example, the following selects an almost completely transparent red
background, and an almost opaque pink foreground:</p>
<pre>
- rxvt -depth 32 -bg rgba:0000/0000/0000/2222 -fg "[e]pink"</pre>
+ urxvt -depth 32 -bg rgba:0000/0000/0000/2222 -fg "[e]pink"</pre>
<p><em>Please note that transparency of any kind if completely unsupported by
the author. Don't bug him with installation questions!</em></p>
<p>
</p>
<hr />
<h1><a name="environment">ENVIRONMENT</a></h1>
-<p><strong>rxvt</strong> sets and/or uses the following environment variables:</p>
+<p><strong>urxvt</strong> sets and/or uses the following environment variables:</p>
<dl>
<dt><strong><a name="item_term"><strong>TERM</strong></a></strong>
<dt><strong><a name="item_colorterm"><strong>COLORTERM</strong></a></strong>
<dd>
-<p>Either <code>rxvt</code>, <code>rxvt-xpm</code>, depending on wether rxvt was
+<p>Either <code>rxvt</code>, <code>rxvt-xpm</code>, depending on wether urxvt was
compiled with XPM support, and optionally with the added extension
<code>-mono</code> to indicate that rxvt-unicode runs on a monochrome screen.</p>
</dd>
the colour code used as default foreground/text colour (or the string
<code>default</code> to indicate that the default-colour escape sequence is to be
used), <code>bg</code> is the colour code used as default background colour (or the
-string <code>default</code>), and <code>xpm</code> is the string <code>default</code> if rxvt
+string <code>default</code>), and <code>xpm</code> is the string <code>default</code> if urxvt
was compiled with XPM support. Libraries like <code>ncurses</code> and <code>slang</code> can
(and do) use this information to optimize screen output.</p>
</dd>
<dt><strong><a name="item_windowid"><strong>WINDOWID</strong></a></strong>
<dd>
-<p>Set to the (decimal) X Window ID of the rxvt window (the toplevel
+<p>Set to the (decimal) X Window ID of the urxvt window (the toplevel
window, which usually has subwindows for the scrollbar, the terminal
window and so on).</p>
</dd>
<dt><strong><a name="item_terminfo"><strong>TERMINFO</strong></a></strong>
<dd>
-<p>Set to the terminfo directory iff rxvt was configured with
+<p>Set to the terminfo directory iff urxvt was configured with
<code>--with-terminfo=PATH</code>.</p>
</dd>
</li>
<dt><strong><a name="item_display"><strong>DISPLAY</strong></a></strong>
<dd>
-<p>Used by rxvt to connect to the display and set to the correct
+<p>Used by urxvt to connect to the display and set to the correct
display in its child processes.</p>
</dd>
</li>
<dt><strong><a name="item_rxvt_socket"><strong>RXVT_SOCKET</strong></a></strong>
<dd>
-<p>The unix domain socket path used by <code>rxvtc(1)</code> and
-rxvtd(1).</p>
+<p>The unix domain socket path used by <code>urxvtc(1)</code> and
+urxvtd(1).</p>
</dd>
<dd>
<p>Default <em>$HOME/.rxvt-unicode-<em><nodename </em></em> >>>.</p>
<dd>
<p>If set and accessible, gives the name of a X resource file to be loaded by
-rxvt.</p>
+urxvt.</p>
</dd>
</li>
</dl>
</p>
<hr />
<h1><a name="see_also">SEE ALSO</a></h1>
-<p>rxvt(7), rxvtc(1), rxvtd(1), xterm(1), sh(1), resize(1), X(1), pty(4), tty(4), <code>utmp(5)</code></p>
+<p>urxvt(7), urxvtc(1), urxvtd(1), xterm(1), sh(1), resize(1), X(1), pty(4), tty(4), <code>utmp(5)</code></p>
<p>
</p>
<hr />
.\" ========================================================================
.\"
.IX Title "@@RXVT_NAME@@ 1"
-.TH @@RXVT_NAME@@ 1 "2006-07-06" "7.7" "RXVT-UNICODE"
+.TH @@RXVT_NAME@@ 1 "2006-07-17" "7.8" "RXVT-UNICODE"
.SH "NAME"
rxvt\-unicode (ouR XVT, unicode) \- (a VT102 emulator for the X window system)
.SH "SYNOPSIS"
system)
SYNOPSIS
- rxvt [options] [-e command [ args ]]
+ urxvt [options] [-e command [ args ]]
DESCRIPTION
- rxvt-unicode, version 7.7, is a colour vt102 terminal emulator intended
+ rxvt-unicode, version 7.8, is a colour vt102 terminal emulator intended
as an *xterm*(1) replacement for users who do not require features such
as Tektronix 4014 emulation and toolkit-style configurability. As a
result, rxvt-unicode uses much less swap space -- a significant
advantage on a machine serving many X sessions.
FREQUENTLY ASKED QUESTIONS
- See rxvt(7) (try "man 7 rxvt") for a list of frequently asked questions
- and answer to them and some common problems. That document is also
- accessible on the World-Wide-Web at
+ See urxvt(7) (try "man 7 urxvt") for a list of frequently asked
+ questions and answer to them and some common problems. That document is
+ also accessible on the World-Wide-Web at
<http://cvs.schmorp.de/browse/*checkout*/rxvt-unicode/doc/rxvt.7.html>.
RXVT-UNICODE VS. RXVT
without most of 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 rxvtd(1) (daemon) and rxvtc(1)
+ drastically reduces memory usage. See urxvtd(1) (daemon) and urxvtc(1)
(client).
It also makes technical information about escape sequences (which have
- been extended) easier accessible: see rxvt(7) for technical reference
+ been extended) easier accessible: see urxvt(7) for technical reference
documentation (escape sequences etc.).
OPTIONS
- The rxvt options (mostly a subset of *xterm*'s) are listed below. In
+ The urxvt options (mostly a subset of *xterm*'s) are listed below. In
keeping with the smaller-is-better philosophy, options may be eliminated
or default values chosen at compile-time, so options and defaults listed
- may not accurately reflect the version installed on your system. `rxvt
+ may not accurately reflect the version installed on your system. `urxvt
-h' gives a list of major compile-time options on the *Options* line.
Option descriptions may be prefixed with which compile option each is
dependent upon. e.g. `Compile *XIM*:' requires *XIM* on the *Options*
- line. Note: `rxvt -help' gives a list of all command-line options
+ line. Note: `urxvt -help' gives a list of all command-line options
compiled into your version.
- Note that rxvt permits the resource name to be used as a long-option
+ Note that urxvt permits the resource name to be used as a long-option
(--/++ option) so the potential command-line options are far greater
- than those listed. For example: `rxvt --loginShell --color1 Orange'.
+ than those listed. For example: `urxvt --loginShell --color1 Orange'.
The following options are available:
be used to brighten or darken the image in addition to tinting it;
resource *tintColor*. Example:
- rxvt -tr -tint blue -sh 40
+ urxvt -tr -tint blue -sh 40
-sh *number* Darken (0 .. 100) or lighten (-1 .. -100) the transparent
background image in addition to tinting it (i.e. -tint must be
prefix it with "x:". To specify an XFT-font, you need to prefix it
with "xft:", e.g.:
- rxvt -fn "xft:Bitstream Vera Sans Mono:pixelsize=15"
- rxvt -fn "9x15bold,xft:Bitstream Vera Sans Mono"
+ urxvt -fn "xft:Bitstream Vera Sans Mono:pixelsize=15"
+ urxvt -fn "9x15bold,xft:Bitstream Vera Sans Mono"
See also the question "How does rxvt-unicode choose fonts?" in the
- FAQ section of rxvt(7).
+ FAQ section of urxvt(7).
-fb *fontlist*
Compile *font-styles*: The bold font list to use when bold
resource termName.
-e *command [arguments]*
- Run the command with its command-line arguments in the rxvt window;
+ Run the command with its command-line arguments in the urxvt window;
also sets the window title and icon name to be the basename of the
program being executed if neither *-title* (*-T*) nor *-n* are given
on the command line. If this option is used, it must be the last on
want to run shell commands, you have to specify the shell, like
this:
- rxvt -e sh -c "shell commands"
+ urxvt -e sh -c "shell commands"
-title *text*
Window title (-T still respected); the default title is the basename
secondaryScroll.
-hold|+hold
- Turn on/off hold window after exit support. If enabled, rxvt will
+ Turn on/off hold window after exit support. If enabled, urxvt will
not immediately destroy its window when the program executed within
it exits. Instead, it will wait till it is being killed or closed by
the user; resource hold.
Remap a key symbol. See resource keysym.
-embed *windowid*
- Tells rxvt to embed its windows into an already-existing window,
+ Tells urxvt to embed its windows into an already-existing window,
which enables applications to easily embed a terminal.
- Right now, rxvt will first unmap/map the specified window, so it
- shouldn't be a top-level window. rxvt will also reconfigure it quite
- a bit, so don't expect it to keep some specific state. It's best to
- create an extra subwindow for rxvt and leave it alone.
+ Right now, urxvt will first unmap/map the specified window, so it
+ shouldn't be a top-level window. urxvt will also reconfigure it
+ quite a bit, so don't expect it to keep some specific state. It's
+ best to create an extra subwindow for urxvt and leave it alone.
- The window will not be destroyed when rxvt exits.
+ The window will not be destroyed when urxvt exits.
- It might be useful to know that rxvt will not close file descriptors
- passed to it (except for stdin/out/err, of course), so you can use
- file descriptors to communicate with the programs within the
- terminal. This works regardless of wether the "-embed" option was
- used or not.
+ It might be useful to know that urxvt will not close file
+ descriptors passed to it (except for stdin/out/err, of course), so
+ you can use file descriptors to communicate with the programs within
+ the terminal. This works regardless of wether the "-embed" option
+ was used or not.
Here is a short Gtk2-perl snippet that illustrates how this option
can be used (a longer example is in doc/embed):
my $rxvt = new Gtk2::Socket;
$rxvt->signal_connect_after (realize => sub {
my $xid = $_[0]->window->get_xid;
- system "rxvt -embed $xid &";
+ system "urxvt -embed $xid &";
});
-pty-fd *file descriptor*
- Tells rxvt NOT to execute any commands or create a new pty/tty pair
+ Tells urxvt NOT to execute any commands or create a new pty/tty pair
but instead use the given filehandle as the tty master. This is
- useful if you want to drive rxvt as a generic terminal emulator
+ useful if you want to drive urxvt as a generic terminal emulator
without having to run a program within it.
- If this switch is given, rxvt will not create any utmp/wtmp entries
+ If this switch is given, urxvt will not create any utmp/wtmp entries
and will not tinker with pty/tty permissions - you have to do that
yourself if you want that.
my $pty = new IO::Pty;
fcntl $pty, F_SETFD, 0; # clear close-on-exec
- system "rxvt -pty-fd " . (fileno $pty) . "&";
+ system "urxvt -pty-fd " . (fileno $pty) . "&";
close $pty;
# now communicate with rxvt
use) in this terminal instance. See resource perl-ext for details.
RESOURCES (available also as long-options)
- Note: `rxvt --help' gives a list of all resources (long options)
+ Note: `urxvt --help' gives a list of all resources (long options)
compiled into your version.
You can set and change the resources using X11 tools like xrdb. Many
distribution do also load settings from the ~/.Xresources file when X
- starts. rxvt will consult the following files/resources in order, with
+ starts. urxvt will consult the following files/resources in order, with
later settings overwriting earlier ones:
1. system-wide app-defaults file, either locale-dependent OR global
4. SCREEN_RESOURCES for the current screen
5. $XENVIRONMENT file OR $HOME/.Xdefaults-<nodename>
- Note that when reading X resources, rxvt recognizes two class names:
- Rxvt and URxvt. The class name Rxvt allows resources common to both rxvt
- and the original *rxvt* to be easily configured, while the class name
- URxvt allows resources unique to rxvt, to be shared between different
- rxvt configurations. If no resources are specified, suitable defaults
- will be used. Command-line arguments can be used to override resource
- settings. The following resources are supported (you might want to check
- the rxvtperl(3) manpage for additional settings by perl extensions not
- documented here):
+ Note that when reading X resources, urxvt recognizes two class names:
+ Rxvt and URxvt. The class name Rxvt allows resources common to both
+ urxvt and the original *rxvt* to be easily configured, while the class
+ name URxvt allows resources unique to urxvt, to be shared between
+ different urxvt configurations. If no resources are specified, suitable
+ defaults will be used. Command-line arguments can be used to override
+ resource settings. The following resources are supported (you might want
+ to check the urxvtperl(3) manpage for additional settings by perl
+ extensions not documented here):
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 rxvt(7)).
+ be changed using an escape command (see urxvt(7)).
Colours 16-79 form a standard 4x4x4 colour cube (the same as xterm
with 88 colour support). Colours 80-87 are evenly spaces grey steps.
(whitespace delimiting is added automatically if resource is given).
When the selection extension is in use (the default if compiled in,
- see the rxvtperl(3) manpage), a suitable regex using these
+ see the urxvtperl(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.
Specify the font-set used for XIM styles "OverTheSpot" or
"OffTheSpot". It must be a standard X font set (XLFD patterns
separated by commas), i.e. it's not in the same format as the other
- font lists used in rxvt. The default will be set-up to chose *any*
+ font lists used in urxvt. The default will be set-up to chose *any*
suitable found found, preferably one or two pixels differing in size
to the base font. option -imfont.
instead scroll the screen up.
hold: *boolean*
- Turn on/off hold window after exit support. If enabled, rxvt will
+ Turn on/off hold window after exit support. If enabled, urxvt will
not immediately destroy its window when the program executed within
it exits. Instead, it will wait till it is being killed or closed by
the user.
Please note that you need to double the "\" in resource files, as
Xlib itself does its own de-escaping (you can use "\033" instead of
- "\e" (and so on), which will work with both Xt and rxvt's own
+ "\e" (and so on), which will work with both Xt and urxvt's own
processing).
You can define a range of keysyms in one shot by providing a
URxvt.keysym.Meta-Control-0x63: \033<M-C-c>
If *string* takes the form of "command:STRING", the specified STRING
- is interpreted and executed as rxvt's control sequence. For example
+ is interpreted and executed as urxvt's control sequence. For example
the following means "change the current locale to "zh_CN.GBK" when
Control-Meta-c is being pressed":
If *string* takes the form "perl:STRING", then the specified STRING
is passed to the "on_keyboard_command" perl handler. See the
- rxvtperl(3) manpage. For example, the selection extension (activated
- via "rxvt -pe selection") listens for "selection:rot13" events:
+ urxvtperl(3) manpage. For example, the selection extension
+ (activated via "urxvt -pe selection") listens for "selection:rot13"
+ events:
URxvt.keysym.M-C-c: perl:selection:rot13
unless some of those are defined mappings themselves.
Unfortunately, this will override built-in key mappings. For example
- if you overwrite the "Insert" key you will disable rxvt's
+ if you overwrite the "Insert" key you will disable urxvt's
"Shift-Insert" mapping. To re-enable that, you can poke "holes" into
the user-defined keymap using the "builtin:" replacement:
URxvt.keysym.M-C-1: command:\033]50;suxuseuro\007
URxvt.keysym.M-C-2: command:\033]50;9x15bold\007
- Other things are possible, e.g. resizing (see rxvt(7) for more
+ Other things are possible, e.g. resizing (see urxvt(7) for more
info):
URxvt.keysym.M-C-3: command:\033[8;25;80t
perl-eval: *string*
Perl code to be evaluated when all extensions have been registered.
- See the rxvtperl(3) manpage. Due to security reasons, this resource
+ See the urxvtperl(3) manpage. Due to security reasons, this resource
will be ignored when running setuid/setgid.
perl-lib: *path*
Colon-separated list of additional directories that hold extension
scripts. When looking for extensions specified by the "perl"
- resource, rxvt will first look in these directories and then in
- /opt/rxvt/lib/urxvt/perl/. Due to security reasons, this resource
+ resource, urxvt will first look in these directories and then in
+ /usr/local/lib/urxvt/perl/. Due to security reasons, this resource
will be ignored when running setuid/setgid.
- See the rxvtperl(3) manpage.
+ See the urxvtperl(3) manpage.
selection.pattern-*idx*: *perl-regex*
- Additional selection patterns, see the rxvtperl(3) manpage for
+ Additional selection patterns, see the urxvtperl(3) manpage for
details.
selection-autotransform.*idx*: *perl-transform*
- Selection auto-transform patterns, see the rxvtperl(3) manpage for
+ Selection auto-transform patterns, see the urxvtperl(3) manpage for
details.
searchable-scrollback: *keysym*
-override-redirect.
THE SCROLLBAR
- Lines of text that scroll off the top of the rxvt window (resource:
+ Lines of text that scroll off the top of the urxvt window (resource:
saveLines) and can be scrolled back using the scrollbar or by
- keystrokes. The normal rxvt scrollbar has arrows and its behaviour is
+ keystrokes. The normal urxvt scrollbar has arrows and its behaviour is
fairly intuitive. The xterm-scrollbar is without arrows and its
behaviour mimics that of *xterm*
removed from the selection.
Insertion:
- Pressing and releasing the Middle mouse button in an rxvt window
+ Pressing and releasing the Middle mouse button in an urxvt 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
- rxvt tries to write an entry into the *utmp*(5) file so that it can be
+ urxvt tries to write an entry into the *utmp*(5) file so that it can be
seen via the *who(1)* command, and can accept messages. To allow this
- feature, rxvt may need to be installed setuid root on some systems or
+ feature, urxvt may need to be installed setuid root on some systems or
setgid to root or to some other group on others.
COLORS AND GRAPHICS
- In addition to the default foreground and background colours, rxvt can
+ In addition to the default foreground and background colours, urxvt can
display up to 16 colours (8 ANSI colours plus high-intensity bold/blink
versions of the same). Here is a list of the colours with their names.
0-15, as a convenient shorthand to reference the colour name of
color0-color15.
- In addition to the colours defined above, rxvt offers an additional 72
+ In addition to the colours defined above, urxvt 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,
- rxvt -fg Black -bg White -rv
+ urxvt -fg Black -bg White -rv
would yield White on Black, while on *xterm*(1) it would yield Black
on White.
For example, the following selects an almost completely transparent red
background, and an almost opaque pink foreground:
- rxvt -depth 32 -bg rgba:0000/0000/0000/2222 -fg "[e]pink"
+ urxvt -depth 32 -bg rgba:0000/0000/0000/2222 -fg "[e]pink"
*Please note that transparency of any kind if completely unsupported by
the author. Don't bug him with installation questions!*
ENVIRONMENT
- rxvt sets and/or uses the following environment variables:
+ urxvt sets and/or uses the following environment variables:
TERM
Normally set to "rxvt-unicode", unless overwritten at configure
time, via resources or on the commandline.
COLORTERM
- Either "rxvt", "rxvt-xpm", depending on wether rxvt was compiled
+ Either "rxvt", "rxvt-xpm", depending on wether urxvt was compiled
with XPM support, and optionally with the added extension "-mono" to
indicate that rxvt-unicode runs on a monochrome screen.
string "default" to indicate that the default-colour escape sequence
is to be used), "bg" is the colour code used as default background
colour (or the string "default"), and "xpm" is the string "default"
- if rxvt was compiled with XPM support. Libraries like "ncurses" and
+ if urxvt was compiled with XPM support. Libraries like "ncurses" and
"slang" can (and do) use this information to optimize screen output.
WINDOWID
- Set to the (decimal) X Window ID of the rxvt window (the toplevel
+ Set to the (decimal) X Window ID of the urxvt window (the toplevel
window, which usually has subwindows for the scrollbar, the terminal
window and so on).
TERMINFO
- Set to the terminfo directory iff rxvt was configured with
+ Set to the terminfo directory iff urxvt was configured with
"--with-terminfo=PATH".
DISPLAY
- Used by rxvt to connect to the display and set to the correct
+ Used by urxvt to connect to the display and set to the correct
display in 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 rxvtc(1) and rxvtd(1).
+ The unix domain socket path used by urxvtc(1) and urxvtd(1).
Default $HOME/.rxvt-unicode-*<nodename*.
XENVIRONMENT
If set and accessible, gives the name of a X resource file to be
- loaded by rxvt.
+ loaded by urxvt.
FILES
/usr/lib/X11/rgb.txt
Color names.
SEE ALSO
- rxvt(7), rxvtc(1), rxvtd(1), xterm(1), sh(1), resize(1), X(1), pty(4),
- tty(4), utmp(5)
+ urxvt(7), urxvtc(1), urxvtd(1), xterm(1), sh(1), resize(1), X(1),
+ pty(4), tty(4), utmp(5)
CURRENT PROJECT COORDINATOR
Project Coordinator
<dt><strong><a name="item_iso14755">--enable-iso14755 (default: on)</a></strong>
<dd>
-<p>Enable extended ISO 14755 support (see rxvt(1), or
+<p>Enable extended ISO 14755 support (see urxvt(1), or
<em>doc/rxvt.1.txt</em>). Basic support (section 5.1) is enabled by
<code>--enable-frills</code>, while support for 5.2, 5.3 and 5.4 is enabled with
this switch.</p>
<dt><strong><a name="item_perl">--enable-perl (default: on)</a></strong>
<dd>
-<p>Enable an embedded perl interpreter. See the <strong>rxvtperl(3)</strong>
+<p>Enable an embedded perl interpreter. See the <strong>urxvtperl(3)</strong>
manpage (<em>doc/rxvtperl.txt</em>) for more info on this feature, or the files
in <em>src/perl-ext/</em> for the extensions that are installed by default. The
perl interpreter that is used can be specified via the <code>PERL</code> environment
.\" ========================================================================
.\"
.IX Title "@@RXVT_NAME@@ 7"
-.TH @@RXVT_NAME@@ 7 "2006-07-06" "7.7" "RXVT-UNICODE"
+.TH @@RXVT_NAME@@ 7 "2006-07-17" "7.8" "RXVT-UNICODE"
.SH "NAME"
RXVT REFERENCE \- FAQ, command sequences and other background information
.SH "SYNOPSIS"
verbose X error handling
--enable-iso14755 (default: on)
- Enable extended ISO 14755 support (see rxvt(1), or doc/rxvt.1.txt).
+ Enable extended ISO 14755 support (see urxvt(1), or doc/rxvt.1.txt).
Basic support (section 5.1) is enabled by "--enable-frills", while
support for 5.2, 5.3 and 5.4 is enabled with this switch.
Add support to have the pointer disappear when typing or inactive.
--enable-perl (default: on)
- Enable an embedded perl interpreter. See the rxvtperl(3) manpage
+ Enable an embedded perl interpreter. See the urxvtperl(3) manpage
(doc/rxvtperl.txt) for more info on this feature, or the files in
src/perl-ext/ for the extensions that are installed by default. The
perl interpreter that is used can be specified via the "PERL"
+<?xml version="1.0" ?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
-<title>rxvtc - control the rxvtd daemon</title>
+<title>urxvtc - control the urxvtd daemon</title>
+<meta http-equiv="content-type" content="text/html; charset=utf-8" />
<link rev="made" href="mailto:perl-binary@plan9.de" />
</head>
<p>
</p>
<h1><a name="name">NAME</a></h1>
-<p>rxvtc - control the rxvtd daemon</p>
+<p>urxvtc - control the urxvtd daemon</p>
<p>
</p>
<hr />
<h1><a name="synopsis">SYNOPSIS</a></h1>
-<p><strong>rxvtc</strong> [same options as for rxvt]</p>
+<p><strong>urxvtc</strong> [same options as for urxvt]</p>
<p>
</p>
<hr />
<h1><a name="description">DESCRIPTION</a></h1>
-<p>This manpage describes the <strong>rxvtc</strong> client program. It connects
-to the <strong>rxvtd</strong> daemon and requests a new terminal window. It
-takes the same arguments as the <strong>rxvt</strong> program. The environment
+<p>This manpage describes the <strong>urxvtc</strong> client program. It connects
+to the <strong>urxvtd</strong> daemon and requests a new terminal window. It
+takes the same arguments as the <strong>urxvt</strong> program. The environment
will also be respected. Currently, it always returns immediately after
contacting the daemon.</p>
<p>
</p>
<hr />
<h1><a name="options">OPTIONS</a></h1>
-<p>All options that are valid for <strong>rxvt</strong> are valid for
-<strong>rxvtc</strong>, too. Please note that all options are currently
+<p>All options that are valid for <strong>urxvt</strong> are valid for
+<strong>urxvtc</strong>, too. Please note that all options are currently
interpreted in the context of the daemon process, which makes a difference
for options that specify a file descriptor (such as <strong>-pty-fd</strong>).</p>
<p>
</p>
<hr />
<h1><a name="exit_status">EXIT STATUS</a></h1>
-<p>If everything went well, rxvtc returns with an exit status of <code>0</code>.
+<p>If everything went well, urxvtc returns with an exit status of <code>0</code>.
If contacting the daemon fails, it exits with the exit status <code>2</code>. In all other error
cases it returns with status <code>1</code>.</p>
<p>This can be used to implement auto-starting behaviour, by checking for an
-exit status of <code>2</code>, running <code>rxvtd -f -q</code> and retrying the call
-to rxvtc.</p>
+exit status of <code>2</code>, running <code>urxvtd -f -q</code> and retrying the call
+to urxvtc.</p>
<p>
</p>
<hr />
<h1><a name="environment">ENVIRONMENT</a></h1>
<p>All environment variables of the current process will be made available
-to the new instance, and will be interpreted as if <strong>rxvt</strong> were
+to the new instance, and will be interpreted as if <strong>urxvt</strong> were
started directly.</p>
<dl>
-<dt><strong><a name="item_rxvt_socket"><strong>RXVT_SOCKET</strong></a></strong><br />
-</dt>
+<dt><strong><a name="item_rxvt_socket"><strong>RXVT_SOCKET</strong></a></strong>
+
<dd>
-Both rxvtc and rxvtd use the environment variable
+<p>Both urxvtc and urxvtd use the environment variable
<em>RXVT_SOCKET</em> to create a listening socket and to contact the
-rxvtd, respectively. If the variable is missing,
+urxvtd, respectively. If the variable is missing,
<em>$HOME/.rxvt-unicode-<em><nodename</em> </em>> >>> is used. The variable must
-specify the absolute path of the socket to create.
+specify the absolute path of the socket to create.</p>
</dd>
-<p></p></dl>
+</li>
+</dl>
<p>
</p>
<hr />
<h1><a name="see_also">SEE ALSO</a></h1>
-<p>rxvt(7), <code>rxvtd(1)</code></p>
+<p>urxvt(7), <code>urxvtd(1)</code></p>
</body>
-.\" Automatically generated by Pod::Man v1.37, Pod::Parser v1.14
+.\" Automatically generated by Pod::Man 2.09 (Pod::Simple 3.04)
.\"
.\" Standard preamble:
.\" ========================================================================
.rm #[ #] #H #V #F C
.\" ========================================================================
.\"
-.IX Title "rxvt 1"
-.TH rxvt 1 "2006-02-02" "7.5" "RXVT-UNICODE"
+.IX Title "@@RXVT_NAME@@ 1"
+.TH @@RXVT_NAME@@ 1 "2006-07-17" "7.8" "RXVT-UNICODE"
.SH "NAME"
@@RXVT_NAME@@c \- control the @@RXVT_NAME@@d daemon
.SH "SYNOPSIS"
Both @@RXVT_NAME@@c and @@RXVT_NAME@@d use the environment variable
\&\fI\s-1RXVT_SOCKET\s0\fR to create a listening socket and to contact the
@@RXVT_NAME@@d, respectively. If the variable is missing,
-\&\fI$HOME/.rxvt\-unicode\-\fI<nodename>\fI\fR is used. The variable must
+\&\fI\f(CI$HOME\fI/.rxvt\-unicode\-\fI<nodename>\fI\fR is used. The variable must
specify the absolute path of the socket to create.
.SH "SEE ALSO"
.IX Header "SEE ALSO"
NAME
- rxvtc - control the rxvtd daemon
+ urxvtc - control the urxvtd daemon
SYNOPSIS
- rxvtc [same options as for rxvt]
+ urxvtc [same options as for urxvt]
DESCRIPTION
- This manpage describes the rxvtc client program. It connects to the
- rxvtd daemon and requests a new terminal window. It takes the same
- arguments as the rxvt program. The environment will also be respected.
+ This manpage describes the urxvtc client program. It connects to the
+ urxvtd daemon and requests a new terminal window. It takes the same
+ arguments as the urxvt program. The environment will also be respected.
Currently, it always returns immediately after contacting the daemon.
OPTIONS
- All options that are valid for rxvt are valid for rxvtc, too. Please
+ All options that are valid for urxvt are valid for urxvtc, too. Please
note that all options are currently interpreted in the context of the
daemon process, which makes a difference for options that specify a file
descriptor (such as -pty-fd).
EXIT STATUS
- If everything went well, rxvtc returns with an exit status of 0. If
+ If everything went well, urxvtc returns with an exit status of 0. If
contacting the daemon fails, it exits with the exit status 2. In all
other error cases it returns with status 1.
This can be used to implement auto-starting behaviour, by checking for
- an exit status of 2, running "rxvtd -f -q" and retrying the call to
- rxvtc.
+ an exit status of 2, running "urxvtd -f -q" and retrying the call to
+ urxvtc.
ENVIRONMENT
All environment variables of the current process will be made available
- to the new instance, and will be interpreted as if rxvt were started
+ to the new instance, and will be interpreted as if urxvt were started
directly.
RXVT_SOCKET
- Both rxvtc and rxvtd use the environment variable RXVT_SOCKET to
- create a listening socket and to contact the rxvtd, respectively. If
- the variable is missing, $HOME/.rxvt-unicode-*<nodename>* is used.
- The variable must specify the absolute path of the socket to create.
+ Both urxvtc and urxvtd use the environment variable RXVT_SOCKET to
+ create a listening socket and to contact the urxvtd, respectively.
+ If the variable is missing, $HOME/.rxvt-unicode-*<nodename>* is
+ used. The variable must specify the absolute path of the socket to
+ create.
SEE ALSO
- rxvt(7), rxvtd(1)
+ urxvt(7), urxvtd(1)
+<?xml version="1.0" ?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
-<title>rxvtd - rxvt terminal daemon</title>
+<title>urxvtd - urxvt terminal daemon</title>
+<meta http-equiv="content-type" content="text/html; charset=utf-8" />
<link rev="made" href="mailto:perl-binary@plan9.de" />
</head>
<p>
</p>
<h1><a name="name">NAME</a></h1>
-<p>rxvtd - rxvt terminal daemon</p>
+<p>urxvtd - urxvt terminal daemon</p>
<p>
</p>
<hr />
<h1><a name="synopsis">SYNOPSIS</a></h1>
-<p><strong>rxvtd</strong> [-q|--quiet] [-o|--opendisplay] [-f|--fork]</p>
+<p><strong>urxvtd</strong> [-q|--quiet] [-o|--opendisplay] [-f|--fork]</p>
<p>
</p>
<hr />
<h1><a name="description">DESCRIPTION</a></h1>
-<p>This manpage describes the rxvtd daemon, which is the same vt102
-terminal emulator as rxvt, but runs as a daemon that can open
+<p>This manpage describes the urxvtd daemon, which is the same vt102
+terminal emulator as urxvt, but runs as a daemon that can open
multiple terminal windows within the same process.</p>
<p>You can run it from your X startup scripts, for example, although it is
not dependent on a working DISPLAY and, in fact, can open windows on
multiple X displays on the same time.</p>
-<p>Advantages of running a rxvt daemon include faster creation time
+<p>Advantages of running a urxvt daemon include faster creation time
for terminal windows and a lot of saved memory.</p>
<p>The disadvantage is a possible impact on stability - if the
main program crashes, all processes in the terminal windows are
terminated. For example, as there is no way to cleanly react to abnormal
connection closes, <code>xkill</code> and server resets/restarts will kill the
-<strong>rxvtd</strong> instance including all windows it has opened.</p>
+<strong>urxvtd</strong> instance including all windows it has opened.</p>
<p>
</p>
<hr />
<h1><a name="options">OPTIONS</a></h1>
-<p><strong>rxvtd</strong> currently understands a few options only. Bundling of
+<p><strong>urxvtd</strong> currently understands a few options only. Bundling of
options is not yet supported.</p>
<dl>
-<dt><strong><a name="item__2dq_2c__2d_2dquiet"><strong>-q</strong>, <strong>--quiet</strong></a></strong><br />
-</dt>
+<dt><strong><a name="item__2dq_2c__2d_2dquiet"><strong>-q</strong>, <strong>--quiet</strong></a></strong>
+
<dd>
-Normally, <strong>rxvtd</strong> outputs the message <code>rxvt-unicode daemon
+<p>Normally, <strong>urxvtd</strong> outputs the message <code>rxvt-unicode daemon
listening on <path></code> after binding to its control socket. This option
-will suppress this message (errors and warnings will still be logged).
+will suppress this message (errors and warnings will still be logged).</p>
</dd>
-<p></p>
-<dt><strong><a name="item__2do_2c__2d_2dopendisplay"><strong>-o</strong>, <strong>--opendisplay</strong></a></strong><br />
-</dt>
+</li>
+<dt><strong><a name="item__2do_2c__2d_2dopendisplay"><strong>-o</strong>, <strong>--opendisplay</strong></a></strong>
+
<dd>
-This forces <strong>rxvtd</strong> to open a connection to the current
-<code>$DISPLAY</code> and keep it open.
+<p>This forces <strong>urxvtd</strong> to open a connection to the current
+<code>$DISPLAY</code> and keep it open.</p>
</dd>
<dd>
-<p>This is useful if you want to bind an instance of <strong>rxvtd</strong> to
+<p>This is useful if you want to bind an instance of <strong>urxvtd</strong> to
the lifetime of a specific display/server. If the server does a reset,
-<strong>rxvtd</strong> will be killed automatically.</p>
+<strong>urxvtd</strong> will be killed automatically.</p>
</dd>
-<p></p>
-<dt><strong><a name="item__2df_2c__2d_2dfork"><strong>-f</strong>, <strong>--fork</strong></a></strong><br />
-</dt>
+</li>
+<dt><strong><a name="item__2df_2c__2d_2dfork"><strong>-f</strong>, <strong>--fork</strong></a></strong>
+
<dd>
-This makes <strong>rxvtd</strong> fork after it has bound itself to its control
-socket.
+<p>This makes <strong>urxvtd</strong> fork after it has bound itself to its control
+socket.</p>
</dd>
-<p></p></dl>
+</li>
+</dl>
<p>
</p>
<hr />
<h1><a name="examples">EXAMPLES</a></h1>
-<p>This is a useful invocation of <strong>rxvtd</strong> in a <em>.xsession</em>-style
+<p>This is a useful invocation of <strong>urxvtd</strong> in a <em>.xsession</em>-style
script:</p>
<pre>
- B<rxvtd> -q -f -o</pre>
+ B<urxvtd> -q -f -o</pre>
<p>This waits till the control socket is available, opens the current display
and forks into the background. When you log-out, the server is reset and
-<strong>rxvtd</strong> is killed.</p>
+<strong>urxvtd</strong> is killed.</p>
<p>
</p>
<hr />
<h1><a name="environment">ENVIRONMENT</a></h1>
<dl>
-<dt><strong><a name="item_rxvt_socket"><strong>RXVT_SOCKET</strong></a></strong><br />
-</dt>
+<dt><strong><a name="item_rxvt_socket"><strong>RXVT_SOCKET</strong></a></strong>
+
<dd>
-Both <strong>rxvtc</strong> and <strong>rxvtd</strong> use the environment
+<p>Both <strong>urxvtc</strong> and <strong>urxvtd</strong> use the environment
variable <em>RXVT_SOCKET</em> to create a listening socket and to contact
-the rxvtd, respectively. If the variable is missing,
+the urxvtd, respectively. If the variable is missing,
<em>$HOME/.rxvt-unicode-<em><nodename</em> </em>> >>> is used. The variable must
-specify the absolute path of the socket to create.
+specify the absolute path of the socket to create.</p>
</dd>
-<p></p>
-<dt><strong><a name="item_display"><strong>DISPLAY</strong></a></strong><br />
-</dt>
+</li>
+<dt><strong><a name="item_display"><strong>DISPLAY</strong></a></strong>
+
<dd>
-Only used when the <code>--opendisplay</code> option is specified. Must contain a
-valid X display name.
+<p>Only used when the <code>--opendisplay</code> option is specified. Must contain a
+valid X display name.</p>
</dd>
</dl>
<p>
</p>
<hr />
<h1><a name="see_also">SEE ALSO</a></h1>
-<p>rxvt(7), <code>rxvtc(1)</code></p>
+<p>urxvt(7), <code>urxvtc(1)</code></p>
</body>
-.\" Automatically generated by Pod::Man v1.37, Pod::Parser v1.3
+.\" Automatically generated by Pod::Man 2.09 (Pod::Simple 3.04)
.\"
.\" Standard preamble:
.\" ========================================================================
.rm #[ #] #H #V #F C
.\" ========================================================================
.\"
-.IX Title "rxvt 1"
-.TH rxvt 1 "2005-12-17" "5.9" "RXVT-UNICODE"
+.IX Title "@@RXVT_NAME@@ 1"
+.TH @@RXVT_NAME@@ 1 "2006-07-17" "7.8" "RXVT-UNICODE"
.SH "NAME"
@@RXVT_NAME@@d \- @@RXVT_NAME@@ terminal daemon
.SH "SYNOPSIS"
script:
.PP
.Vb 1
-\& B<@@RXVT_NAME@@d> -q -f -o
+\& B<@@RXVT_NAME@@d> \-q \-f \-o
.Ve
.PP
This waits till the control socket is available, opens the current display
Both \fB@@RXVT_NAME@@c\fR and \fB@@RXVT_NAME@@d\fR use the environment
variable \fI\s-1RXVT_SOCKET\s0\fR to create a listening socket and to contact
the @@RXVT_NAME@@d, respectively. If the variable is missing,
-\&\fI$HOME/.rxvt\-unicode\-\fI<nodename>\fI\fR is used. The variable must
+\&\fI\f(CI$HOME\fI/.rxvt\-unicode\-\fI<nodename>\fI\fR is used. The variable must
specify the absolute path of the socket to create.
.IP "\fB\s-1DISPLAY\s0\fR" 4
.IX Item "DISPLAY"
Only used when the \f(CW\*(C`\-\-opendisplay\*(C'\fR option is specified. Must contain a
valid X display name.
.RS 4
+.RE
+.RS 4
+.RE
.SH "SEE ALSO"
.IX Header "SEE ALSO"
-.RS 4
@@RXVT_NAME@@(7), @@RXVT_NAME@@c(1)
+.SH "POD ERRORS"
+.IX Header "POD ERRORS"
+Hey! \fBThe above document had some coding errors, which are explained below:\fR
+.IP "Around line 87:" 4
+.IX Item "Around line 87:"
+You forgot a '=back' before '=head1'
+.Sp
+You forgot a '=back' before '=head1'
NAME
- rxvtd - rxvt terminal daemon
+ urxvtd - urxvt terminal daemon
SYNOPSIS
- rxvtd [-q|--quiet] [-o|--opendisplay] [-f|--fork]
+ urxvtd [-q|--quiet] [-o|--opendisplay] [-f|--fork]
DESCRIPTION
- This manpage describes the rxvtd daemon, which is the same vt102
- terminal emulator as rxvt, but runs as a daemon that can open multiple
+ This manpage describes the urxvtd daemon, which is the same vt102
+ terminal emulator as urxvt, but runs as a daemon that can open multiple
terminal windows within the same process.
You can run it from your X startup scripts, for example, although it is
not dependent on a working DISPLAY and, in fact, can open windows on
multiple X displays on the same time.
- Advantages of running a rxvt daemon include faster creation time for
+ Advantages of running a urxvt daemon include faster creation time for
terminal windows and a lot of saved memory.
The disadvantage is a possible impact on stability - if the main program
crashes, all processes in the terminal windows are terminated. For
example, as there is no way to cleanly react to abnormal connection
- closes, "xkill" and server resets/restarts will kill the rxvtd instance
+ closes, "xkill" and server resets/restarts will kill the urxvtd instance
including all windows it has opened.
OPTIONS
- rxvtd currently understands a few options only. Bundling of options is
+ urxvtd currently understands a few options only. Bundling of options is
not yet supported.
-q, --quiet
- Normally, rxvtd outputs the message "rxvt-unicode daemon listening
+ Normally, urxvtd outputs the message "rxvt-unicode daemon listening
on <path>" after binding to its control socket. This option will
suppress this message (errors and warnings will still be logged).
-o, --opendisplay
- This forces rxvtd to open a connection to the current $DISPLAY and
+ This forces urxvtd to open a connection to the current $DISPLAY and
keep it open.
- This is useful if you want to bind an instance of rxvtd to the
+ This is useful if you want to bind an instance of urxvtd to the
lifetime of a specific display/server. If the server does a reset,
- rxvtd will be killed automatically.
+ urxvtd will be killed automatically.
-f, --fork
- This makes rxvtd fork after it has bound itself to its control
+ This makes urxvtd fork after it has bound itself to its control
socket.
EXAMPLES
- This is a useful invocation of rxvtd in a .xsession-style script:
+ This is a useful invocation of urxvtd in a .xsession-style script:
- B<rxvtd> -q -f -o
+ B<urxvtd> -q -f -o
This waits till the control socket is available, opens the current
display and forks into the background. When you log-out, the server is
- reset and rxvtd is killed.
+ reset and urxvtd is killed.
ENVIRONMENT
RXVT_SOCKET
- Both rxvtc and rxvtd use the environment variable RXVT_SOCKET to
- create a listening socket and to contact the rxvtd, respectively. If
- the variable is missing, $HOME/.rxvt-unicode-*<nodename>* is used.
- The variable must specify the absolute path of the socket to create.
+ Both urxvtc and urxvtd use the environment variable RXVT_SOCKET to
+ create a listening socket and to contact the urxvtd, respectively.
+ If the variable is missing, $HOME/.rxvt-unicode-*<nodename>* is
+ used. The variable must specify the absolute path of the socket to
+ create.
DISPLAY
Only used when the "--opendisplay" option is specified. Must contain
a valid X display name.
SEE ALSO
- rxvt(7), rxvtc(1)
+ urxvt(7), urxvtc(1)
+
+POD ERRORS
+ Hey! The above document had some coding errors, which are explained
+ below:
+
+ Around line 87:
+ You forgot a '=back' before '=head1'
+
+ You forgot a '=back' before '=head1'
rxvt -pt OnTheSpot -pe xim-onthespot</pre>
</dd>
</li>
+<dt><strong><a name="item_kuake_3chotkey_3e">kuake<hotkey></a></strong>
+
+<dd>
+<p>A very primitive quake-console-like extension. It was inspired by a
+description of how the programs <code>kuake</code> and <code>yakuake</code> work: Whenever the
+user presses a global accelerator key (by default <code>F10</code>), the terminal
+will show or hide itself. Another press of the accelerator key will hide
+or show it again.</p>
+</dd>
+<dd>
+<p>Initially, the window will not be shown when using this extension.</p>
+</dd>
+<dd>
+<p>This is useful if you need a single terminal thats not using any desktop
+space most of the time but is quickly available at the press of a key.</p>
+</dd>
+<dd>
+<p>The accelerator key is grabbed regardless of any modifers, so this
+extension will actually grab a physical key just for this function.</p>
+</dd>
+<dd>
+<p>If you want a quake-like animation, tell your window manager to do so
+(fvwm can do it).</p>
+</dd>
+</li>
<dt><strong><a name="item_automove_2dbackground">automove-background</a></strong>
<dd>
members are not passed.</p>
</dd>
</li>
+<dt><strong><a name="item_on_root_event__24term_2c__24event">on_root_event $term, $event</a></strong>
+
+<dd>
+<p>Like <code>on_x_event</code>, but is called for events on the root window.</p>
+</dd>
+</li>
<dt><strong><a name="item_on_focus_in__24term">on_focus_in $term</a></strong>
<dd>
.rm #[ #] #H #V #F C
.\" ========================================================================
.\"
-.IX Title "rxvt 3"
-.TH rxvt 3 "2006-07-06" "7.7" "RXVT-UNICODE"
+.IX Title "@@RXVT_NAME@@ 3"
+.TH @@RXVT_NAME@@ 3 "2006-07-17" "7.8" "RXVT-UNICODE"
.SH "NAME"
@@RXVT_NAME@@perl \- rxvt\-unicode's embedded perl interpreter
.SH "SYNOPSIS"
.Vb 1
\& @@RXVT_NAME@@ \-pt OnTheSpot \-pe xim\-onthespot
.Ve
+.IP "kuake<hotkey>" 4
+.IX Item "kuake<hotkey>"
+A very primitive quake-console-like extension. It was inspired by a
+description of how the programs \f(CW\*(C`kuake\*(C'\fR and \f(CW\*(C`yakuake\*(C'\fR work: Whenever the
+user presses a global accelerator key (by default \f(CW\*(C`F10\*(C'\fR), the terminal
+will show or hide itself. Another press of the accelerator key will hide
+or show it again.
+.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
+space most of the time but is quickly available at the press of a key.
+.Sp
+The accelerator key is grabbed regardless of any modifers, so this
+extension will actually grab a physical key just for this function.
+.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
Called on every X event received on the vt window (and possibly other
windows). Should only be used as a last resort. Most event structure
members are not passed.
+.ie n .IP "on_root_event $term\fR, \f(CW$event" 4
+.el .IP "on_root_event \f(CW$term\fR, \f(CW$event\fR" 4
+.IX Item "on_root_event $term, $event"
+Like \f(CW\*(C`on_x_event\*(C'\fR, but is called for events on the root window.
.ie n .IP "on_focus_in $term" 4
.el .IP "on_focus_in \f(CW$term\fR" 4
.IX Item "on_focus_in $term"
rxvt -pt OnTheSpot -pe xim-onthespot
+ kuake<hotkey>
+ A very primitive quake-console-like extension. It was inspired by a
+ description of how the programs "kuake" and "yakuake" work: Whenever
+ the user presses a global accelerator key (by default "F10"), the
+ terminal will show or hide itself. Another press of the accelerator
+ key will hide or show it again.
+
+ Initially, the window will not be shown when using this extension.
+
+ This is useful if you need a single terminal thats not using any
+ desktop space most of the time but is quickly available at the press
+ of a key.
+
+ The accelerator key is grabbed regardless of any modifers, so this
+ extension will actually grab a physical key just for this function.
+
+ 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
other windows). Should only be used as a last resort. Most event
structure members are not passed.
+ on_root_event $term, $event
+ Like "on_x_event", but is called for events on the root window.
+
on_focus_in $term
Called whenever the window gets the keyboard focus, before
rxvt-unicode does focus in processing.
xpm.lo: ../config.h rxvt.h rxvtlib.h optinc.h feature.h encoding.h rxvtutil.h
xpm.lo: rxvtfont.h rxvttoolkit.h iom.h iom_conf.h callback.h salloc.h
xpm.lo: libptytty.h rxvtperl.h hookinc.h rsinc.h
+
+command.lo: ../config.h rxvt.h rxvtlib.h optinc.h feature.h encoding.h
+command.lo: rxvtutil.h rxvtfont.h rxvttoolkit.h iom.h iom_conf.h callback.h
+command.lo: salloc.h libptytty.h rxvtperl.h hookinc.h rsinc.h version.h
+command.lo: command.h keyboard.h
+encoding.lo: ../config.h encoding.h table/iso8859_1.h table/iso8859_15.h
+encoding.lo: table/iso8859_2.h table/iso8859_3.h table/iso8859_4.h
+encoding.lo: table/iso8859_5.h table/iso8859_6.h table/iso8859_7.h
+encoding.lo: table/iso8859_8.h table/iso8859_9.h table/iso8859_10.h
+encoding.lo: table/iso8859_11.h table/iso8859_13.h table/iso8859_14.h
+encoding.lo: table/iso8859_16.h table/koi8_r.h table/koi8_u.h
+encoding.lo: table/ksc5601_1987_0.h table/big5.h table/gbk_0.h
+encoding.lo: table/gb2312_1980_0.h table/cns11643_1992_1.h
+encoding.lo: table/cns11643_1992_2.h table/cns11643_1992_3.h
+encoding.lo: table/cns11643_1992_4.h table/cns11643_1992_5.h
+encoding.lo: table/cns11643_1992_6.h table/cns11643_1992_7.h
+encoding.lo: table/cns11643_1992_f.h table/big5_ext.h table/big5_plus.h
+encoding.lo: table/viscii.h table/jis0201_1976_0.h table/jis0208_1990_0.h
+encoding.lo: table/jis0212_1990_0.h table/jis0213_1.h table/jis0213_2.h
+encoding.lo: table/compose.h table/category.h
+fdpass.lo: ../config.h libptytty.h
+init.lo: ../config.h rxvt.h rxvtlib.h optinc.h feature.h encoding.h
+init.lo: rxvtutil.h rxvtfont.h rxvttoolkit.h iom.h iom_conf.h callback.h
+init.lo: salloc.h libptytty.h rxvtperl.h hookinc.h rsinc.h init.h
+iom.lo: iom.h iom_conf.h rxvtutil.h callback.h
+keyboard.lo: ../config.h rxvt.h rxvtlib.h optinc.h feature.h encoding.h
+keyboard.lo: rxvtutil.h rxvtfont.h rxvttoolkit.h iom.h iom_conf.h callback.h
+keyboard.lo: salloc.h libptytty.h rxvtperl.h hookinc.h rsinc.h keyboard.h
+keyboard.lo: command.h
+logging.lo: ../config.h ptytty.h libptytty.h ptytty_conf.h rxvt.h rxvtlib.h
+logging.lo: optinc.h feature.h encoding.h rxvtutil.h rxvtfont.h rxvttoolkit.h
+logging.lo: iom.h iom_conf.h callback.h salloc.h rxvtperl.h hookinc.h rsinc.h
+main.lo: ../config.h rxvt.h rxvtlib.h optinc.h feature.h encoding.h
+main.lo: rxvtutil.h rxvtfont.h rxvttoolkit.h iom.h iom_conf.h callback.h
+main.lo: salloc.h libptytty.h rxvtperl.h hookinc.h rsinc.h keyboard.h
+misc.lo: ../config.h rxvt.h rxvtlib.h optinc.h feature.h encoding.h
+misc.lo: rxvtutil.h rxvtfont.h rxvttoolkit.h iom.h iom_conf.h callback.h
+misc.lo: salloc.h libptytty.h rxvtperl.h hookinc.h rsinc.h
+netdisp.lo: ../config.h rxvt.h rxvtlib.h optinc.h feature.h encoding.h
+netdisp.lo: rxvtutil.h rxvtfont.h rxvttoolkit.h iom.h iom_conf.h callback.h
+netdisp.lo: salloc.h libptytty.h rxvtperl.h hookinc.h rsinc.h
+proxy.lo: ../config.h ptytty.h libptytty.h ptytty_conf.h rxvt.h rxvtlib.h
+proxy.lo: optinc.h feature.h encoding.h rxvtutil.h rxvtfont.h rxvttoolkit.h
+proxy.lo: iom.h iom_conf.h callback.h salloc.h rxvtperl.h hookinc.h rsinc.h
+ptytty.lo: ../config.h ptytty.h libptytty.h ptytty_conf.h rxvt.h rxvtlib.h
+ptytty.lo: optinc.h feature.h encoding.h rxvtutil.h rxvtfont.h rxvttoolkit.h
+ptytty.lo: iom.h iom_conf.h callback.h salloc.h rxvtperl.h hookinc.h rsinc.h
+rxvt.lo: ../config.h rxvt.h rxvtlib.h optinc.h feature.h encoding.h
+rxvt.lo: rxvtutil.h rxvtfont.h rxvttoolkit.h iom.h iom_conf.h callback.h
+rxvt.lo: salloc.h libptytty.h rxvtperl.h hookinc.h rsinc.h
+rxvtc.lo: ../config.h rxvtdaemon.h rxvtutil.h libptytty.h rxvt.h rxvtlib.h
+rxvtc.lo: optinc.h feature.h encoding.h rxvtfont.h rxvttoolkit.h iom.h
+rxvtc.lo: iom_conf.h callback.h salloc.h rxvtperl.h hookinc.h rsinc.h
+rxvtd.lo: ../config.h rxvt.h rxvtlib.h optinc.h feature.h encoding.h
+rxvtd.lo: rxvtutil.h rxvtfont.h rxvttoolkit.h iom.h iom_conf.h callback.h
+rxvtd.lo: salloc.h libptytty.h rxvtperl.h hookinc.h rsinc.h rxvtdaemon.h
+rxvtdaemon.lo: rxvtdaemon.h rxvtutil.h
+rxvtfont.lo: ../config.h rxvt.h rxvtlib.h optinc.h feature.h encoding.h
+rxvtfont.lo: rxvtutil.h rxvtfont.h rxvttoolkit.h iom.h iom_conf.h callback.h
+rxvtfont.lo: salloc.h libptytty.h rxvtperl.h hookinc.h rsinc.h
+rxvtfont.lo: table/linedraw.h
+rxvtperl.lo: ../config.h iom.h iom_conf.h rxvtutil.h callback.h rxvt.h
+rxvtperl.lo: rxvtlib.h optinc.h feature.h encoding.h rxvtfont.h rxvttoolkit.h
+rxvtperl.lo: salloc.h libptytty.h rxvtperl.h hookinc.h rsinc.h keyboard.h
+rxvtperl.lo: perlxsi.c
+rxvttoolkit.lo: ../config.h rxvt.h rxvtlib.h optinc.h feature.h encoding.h
+rxvttoolkit.lo: rxvtutil.h rxvtfont.h rxvttoolkit.h iom.h iom_conf.h
+rxvttoolkit.lo: callback.h salloc.h libptytty.h rxvtperl.h hookinc.h rsinc.h
+rxvtutil.lo: rxvtutil.h
+salloc.lo: salloc.h
+screen.lo: ../config.h rxvt.h rxvtlib.h optinc.h feature.h encoding.h
+screen.lo: rxvtutil.h rxvtfont.h rxvttoolkit.h iom.h iom_conf.h callback.h
+screen.lo: salloc.h libptytty.h rxvtperl.h hookinc.h rsinc.h salloc.C
+scrollbar-next.lo: ../config.h rxvt.h rxvtlib.h optinc.h feature.h encoding.h
+scrollbar-next.lo: rxvtutil.h rxvtfont.h rxvttoolkit.h iom.h iom_conf.h
+scrollbar-next.lo: callback.h salloc.h libptytty.h rxvtperl.h hookinc.h
+scrollbar-next.lo: rsinc.h
+scrollbar-plain.lo: ../config.h rxvt.h rxvtlib.h optinc.h feature.h
+scrollbar-plain.lo: encoding.h rxvtutil.h rxvtfont.h rxvttoolkit.h iom.h
+scrollbar-plain.lo: iom_conf.h callback.h salloc.h libptytty.h rxvtperl.h
+scrollbar-plain.lo: hookinc.h rsinc.h
+scrollbar-rxvt.lo: ../config.h rxvt.h rxvtlib.h optinc.h feature.h encoding.h
+scrollbar-rxvt.lo: rxvtutil.h rxvtfont.h rxvttoolkit.h iom.h iom_conf.h
+scrollbar-rxvt.lo: callback.h salloc.h libptytty.h rxvtperl.h hookinc.h
+scrollbar-rxvt.lo: rsinc.h
+scrollbar-xterm.lo: ../config.h rxvt.h rxvtlib.h optinc.h feature.h
+scrollbar-xterm.lo: encoding.h rxvtutil.h rxvtfont.h rxvttoolkit.h iom.h
+scrollbar-xterm.lo: iom_conf.h callback.h salloc.h libptytty.h rxvtperl.h
+scrollbar-xterm.lo: hookinc.h rsinc.h
+scrollbar.lo: ../config.h rxvt.h rxvtlib.h optinc.h feature.h encoding.h
+scrollbar.lo: rxvtutil.h rxvtfont.h rxvttoolkit.h iom.h iom_conf.h callback.h
+scrollbar.lo: salloc.h libptytty.h rxvtperl.h hookinc.h rsinc.h
+xdefaults.lo: ../config.h rxvt.h rxvtlib.h optinc.h feature.h encoding.h
+xdefaults.lo: rxvtutil.h rxvtfont.h rxvttoolkit.h iom.h iom_conf.h callback.h
+xdefaults.lo: salloc.h libptytty.h rxvtperl.h hookinc.h rsinc.h version.h
+xdefaults.lo: keyboard.h
+xpm.lo: ../config.h rxvt.h rxvtlib.h optinc.h feature.h encoding.h rxvtutil.h
+xpm.lo: rxvtfont.h rxvttoolkit.h iom.h iom_conf.h callback.h salloc.h
+xpm.lo: libptytty.h rxvtperl.h hookinc.h rsinc.h
+
+command.lo: ../config.h rxvt.h rxvtlib.h optinc.h feature.h encoding.h
+command.lo: rxvtutil.h rxvtfont.h rxvttoolkit.h iom.h iom_conf.h callback.h
+command.lo: salloc.h libptytty.h rxvtperl.h hookinc.h rsinc.h version.h
+command.lo: command.h keyboard.h
+encoding.lo: ../config.h encoding.h table/iso8859_1.h table/iso8859_15.h
+encoding.lo: table/iso8859_2.h table/iso8859_3.h table/iso8859_4.h
+encoding.lo: table/iso8859_5.h table/iso8859_6.h table/iso8859_7.h
+encoding.lo: table/iso8859_8.h table/iso8859_9.h table/iso8859_10.h
+encoding.lo: table/iso8859_11.h table/iso8859_13.h table/iso8859_14.h
+encoding.lo: table/iso8859_16.h table/koi8_r.h table/koi8_u.h
+encoding.lo: table/ksc5601_1987_0.h table/big5.h table/gbk_0.h
+encoding.lo: table/gb2312_1980_0.h table/cns11643_1992_1.h
+encoding.lo: table/cns11643_1992_2.h table/cns11643_1992_3.h
+encoding.lo: table/cns11643_1992_4.h table/cns11643_1992_5.h
+encoding.lo: table/cns11643_1992_6.h table/cns11643_1992_7.h
+encoding.lo: table/cns11643_1992_f.h table/big5_ext.h table/big5_plus.h
+encoding.lo: table/viscii.h table/jis0201_1976_0.h table/jis0208_1990_0.h
+encoding.lo: table/jis0212_1990_0.h table/jis0213_1.h table/jis0213_2.h
+encoding.lo: table/compose.h table/category.h
+fdpass.lo: ../config.h libptytty.h
+init.lo: ../config.h rxvt.h rxvtlib.h optinc.h feature.h encoding.h
+init.lo: rxvtutil.h rxvtfont.h rxvttoolkit.h iom.h iom_conf.h callback.h
+init.lo: salloc.h libptytty.h rxvtperl.h hookinc.h rsinc.h init.h
+iom.lo: iom.h iom_conf.h rxvtutil.h callback.h
+keyboard.lo: ../config.h rxvt.h rxvtlib.h optinc.h feature.h encoding.h
+keyboard.lo: rxvtutil.h rxvtfont.h rxvttoolkit.h iom.h iom_conf.h callback.h
+keyboard.lo: salloc.h libptytty.h rxvtperl.h hookinc.h rsinc.h keyboard.h
+keyboard.lo: command.h
+logging.lo: ../config.h ptytty.h libptytty.h ptytty_conf.h rxvt.h rxvtlib.h
+logging.lo: optinc.h feature.h encoding.h rxvtutil.h rxvtfont.h rxvttoolkit.h
+logging.lo: iom.h iom_conf.h callback.h salloc.h rxvtperl.h hookinc.h rsinc.h
+main.lo: ../config.h rxvt.h rxvtlib.h optinc.h feature.h encoding.h
+main.lo: rxvtutil.h rxvtfont.h rxvttoolkit.h iom.h iom_conf.h callback.h
+main.lo: salloc.h libptytty.h rxvtperl.h hookinc.h rsinc.h keyboard.h
+misc.lo: ../config.h rxvt.h rxvtlib.h optinc.h feature.h encoding.h
+misc.lo: rxvtutil.h rxvtfont.h rxvttoolkit.h iom.h iom_conf.h callback.h
+misc.lo: salloc.h libptytty.h rxvtperl.h hookinc.h rsinc.h
+netdisp.lo: ../config.h rxvt.h rxvtlib.h optinc.h feature.h encoding.h
+netdisp.lo: rxvtutil.h rxvtfont.h rxvttoolkit.h iom.h iom_conf.h callback.h
+netdisp.lo: salloc.h libptytty.h rxvtperl.h hookinc.h rsinc.h
+proxy.lo: ../config.h ptytty.h libptytty.h ptytty_conf.h rxvt.h rxvtlib.h
+proxy.lo: optinc.h feature.h encoding.h rxvtutil.h rxvtfont.h rxvttoolkit.h
+proxy.lo: iom.h iom_conf.h callback.h salloc.h rxvtperl.h hookinc.h rsinc.h
+ptytty.lo: ../config.h ptytty.h libptytty.h ptytty_conf.h rxvt.h rxvtlib.h
+ptytty.lo: optinc.h feature.h encoding.h rxvtutil.h rxvtfont.h rxvttoolkit.h
+ptytty.lo: iom.h iom_conf.h callback.h salloc.h rxvtperl.h hookinc.h rsinc.h
+rxvt.lo: ../config.h rxvt.h rxvtlib.h optinc.h feature.h encoding.h
+rxvt.lo: rxvtutil.h rxvtfont.h rxvttoolkit.h iom.h iom_conf.h callback.h
+rxvt.lo: salloc.h libptytty.h rxvtperl.h hookinc.h rsinc.h
+rxvtc.lo: ../config.h rxvtdaemon.h rxvtutil.h libptytty.h rxvt.h rxvtlib.h
+rxvtc.lo: optinc.h feature.h encoding.h rxvtfont.h rxvttoolkit.h iom.h
+rxvtc.lo: iom_conf.h callback.h salloc.h rxvtperl.h hookinc.h rsinc.h
+rxvtd.lo: ../config.h rxvt.h rxvtlib.h optinc.h feature.h encoding.h
+rxvtd.lo: rxvtutil.h rxvtfont.h rxvttoolkit.h iom.h iom_conf.h callback.h
+rxvtd.lo: salloc.h libptytty.h rxvtperl.h hookinc.h rsinc.h rxvtdaemon.h
+rxvtdaemon.lo: rxvtdaemon.h rxvtutil.h
+rxvtfont.lo: ../config.h rxvt.h rxvtlib.h optinc.h feature.h encoding.h
+rxvtfont.lo: rxvtutil.h rxvtfont.h rxvttoolkit.h iom.h iom_conf.h callback.h
+rxvtfont.lo: salloc.h libptytty.h rxvtperl.h hookinc.h rsinc.h
+rxvtfont.lo: table/linedraw.h
+rxvtperl.lo: ../config.h iom.h iom_conf.h rxvtutil.h callback.h rxvt.h
+rxvtperl.lo: rxvtlib.h optinc.h feature.h encoding.h rxvtfont.h rxvttoolkit.h
+rxvtperl.lo: salloc.h libptytty.h rxvtperl.h hookinc.h rsinc.h keyboard.h
+rxvtperl.lo: perlxsi.c
+rxvttoolkit.lo: ../config.h rxvt.h rxvtlib.h optinc.h feature.h encoding.h
+rxvttoolkit.lo: rxvtutil.h rxvtfont.h rxvttoolkit.h iom.h iom_conf.h
+rxvttoolkit.lo: callback.h salloc.h libptytty.h rxvtperl.h hookinc.h rsinc.h
+rxvtutil.lo: rxvtutil.h
+salloc.lo: salloc.h
+screen.lo: ../config.h rxvt.h rxvtlib.h optinc.h feature.h encoding.h
+screen.lo: rxvtutil.h rxvtfont.h rxvttoolkit.h iom.h iom_conf.h callback.h
+screen.lo: salloc.h libptytty.h rxvtperl.h hookinc.h rsinc.h salloc.C
+scrollbar-next.lo: ../config.h rxvt.h rxvtlib.h optinc.h feature.h encoding.h
+scrollbar-next.lo: rxvtutil.h rxvtfont.h rxvttoolkit.h iom.h iom_conf.h
+scrollbar-next.lo: callback.h salloc.h libptytty.h rxvtperl.h hookinc.h
+scrollbar-next.lo: rsinc.h
+scrollbar-plain.lo: ../config.h rxvt.h rxvtlib.h optinc.h feature.h
+scrollbar-plain.lo: encoding.h rxvtutil.h rxvtfont.h rxvttoolkit.h iom.h
+scrollbar-plain.lo: iom_conf.h callback.h salloc.h libptytty.h rxvtperl.h
+scrollbar-plain.lo: hookinc.h rsinc.h
+scrollbar-rxvt.lo: ../config.h rxvt.h rxvtlib.h optinc.h feature.h encoding.h
+scrollbar-rxvt.lo: rxvtutil.h rxvtfont.h rxvttoolkit.h iom.h iom_conf.h
+scrollbar-rxvt.lo: callback.h salloc.h libptytty.h rxvtperl.h hookinc.h
+scrollbar-rxvt.lo: rsinc.h
+scrollbar-xterm.lo: ../config.h rxvt.h rxvtlib.h optinc.h feature.h
+scrollbar-xterm.lo: encoding.h rxvtutil.h rxvtfont.h rxvttoolkit.h iom.h
+scrollbar-xterm.lo: iom_conf.h callback.h salloc.h libptytty.h rxvtperl.h
+scrollbar-xterm.lo: hookinc.h rsinc.h
+scrollbar.lo: ../config.h rxvt.h rxvtlib.h optinc.h feature.h encoding.h
+scrollbar.lo: rxvtutil.h rxvtfont.h rxvttoolkit.h iom.h iom_conf.h callback.h
+scrollbar.lo: salloc.h libptytty.h rxvtperl.h hookinc.h rsinc.h
+xdefaults.lo: ../config.h rxvt.h rxvtlib.h optinc.h feature.h encoding.h
+xdefaults.lo: rxvtutil.h rxvtfont.h rxvttoolkit.h iom.h iom_conf.h callback.h
+xdefaults.lo: salloc.h libptytty.h rxvtperl.h hookinc.h rsinc.h version.h
+xdefaults.lo: keyboard.h
+xpm.lo: ../config.h rxvt.h rxvtlib.h optinc.h feature.h encoding.h rxvtutil.h
+xpm.lo: rxvtfont.h rxvttoolkit.h iom.h iom_conf.h callback.h salloc.h
+xpm.lo: libptytty.h rxvtperl.h hookinc.h rsinc.h
// VERSION _must_ be \d.\d+
-#define VERSION "7.7"
-#define DATE "2006-02-21"
+#define VERSION "7.8"
+#define DATE "2006-07-17"
projects / dana / urxvt.git / commitdiff