WISH: kick out xpm.C, replace by pixbuf
DUMB: support tex fonts
- - hopefully fix the crashing bug people encounter with 7.8
- (triggered by using transparency + perl). Likely fixes debian bug #380348.
+7.9 Mon Aug 7 18:16:07 CEST 2006
+ - fix the crashing bug people encountered with 7.8 + urxvtd + perl
+ + transparency. Oight to fix debian bug #380348.
- fix urxvtc.1.pod: it actually claimed -pty-fd would not work. But
it does! :->
- rxvt_fatal() in case the locale string is too long for our static buffer.
- - fixed many, many, typos in the documentation (patch supplied by ves).
+ - fixed many, many, typos in the manpages (patch supplied by ves).
7.8 Mon Jul 17 21:00:46 CEST 2006
- INCOMPATIBLE CHANGE: this version will always read ~/.Xdefaults,
re-run the command. Subsequent invocations of the script will re-use the
existing daemon.
- How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc.
+ How do I distinguish whether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc.
The original rxvt and rxvt-unicode always export the variable
"COLORTERM", so you can check and see if that is set. Note that several
programs, JED, slrn, Midnight Commander automatically check this
When you "--enable-everything" (which *is* unfair, as this involves xft
and full locale/XIM support which are quite bloaty inside libX11 and my
- libc), the two diverge, but not unreasnobaly so.
+ libc), the two diverge, but not unreasonably so.
text data bss drs rss filename
163431 2152 24 20123 2060 rxvt --enable-everything
This requires XFT support, and the support of your X-server. If that
doesn't work for you, blame Xorg and Keith Packard. ARGB visuals aren't
there yet, no matter what they claim. Rxvt-Unicode contains the
- neccessary bugfixes and workarounds for Xft and Xlib to make it work,
- but that doesn't mean that your WM has the required kludges in place.
+ necessary bugfixes and workarounds for Xft and Xlib to make it work, but
+ that doesn't mean that your WM has the required kludges in place.
4. Use xcompmgr and let it do the job:
way is to ask for the character bounding box, which unfortunately is
wrong in these cases).
- It's not clear (to me at least), wether this is a bug in Xft, freetype,
+ It's not clear (to me at least), whether this is a bug in Xft, freetype,
or the respective font. If you encounter this problem you might try
using the "-lsp" option to give the font more height. If that doesn't
work, you might be forced to use a different font.
but when running a program that doesn't parse cursor movements or in
some cases during rlogin sessions, it fails to detect this properly.
- You can permamently switch this feature off by disabling the "readline"
+ You can permanently switch this feature off by disabling the "readline"
extension:
URxvt.perl-ext-common: default,-readline
My numerical keypad acts weird and generates differing output?
Some Debian GNUL/Linux users seem to have this problem, although no
specific details were reported so far. It is possible that this is
- caused by the wrong "TERM" setting, although the details of wether and
+ caused by the wrong "TERM" setting, although the details of whether and
how this can happen are unknown, as "TERM=rxvt" should offer a
compatible keymap. See the answer to the previous question, and please
report if that helped.
depressed.
What's with the strange Backspace/Delete key behaviour?
- Assuming that the physical Backspace key corresponds to the BackSpace
+ Assuming that the physical Backspace key corresponds to the Backspace
keysym (not likely for Linux ... see the following question) there are
two standard values that can be used for Backspace: "^H" and "^?".
write.
The selection stuff mainly makes the selection perl-error-message aware
- and tells it to convert pelr error mssages into vi-commands to load the
+ and tells it to convert perl error messages into vi-commands to load the
relevant file and go tot he error line number.
URxvt.scrollstyle: plain
URxvt.secondaryScroll: true
As the documentation says: plain is the preferred scrollbar for the
- author. The "secondaryScroll" confgiures urxvt to scroll in full-screen
- apps, like screen, so lines scorlled out of screen end up in urxvt's
+ author. The "secondaryScroll" configures urxvt to scroll in full-screen
+ apps, like screen, so lines scrolled out of screen end up in urxvt's
scrollback buffer.
URxvt.background: #000000
urxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true
I wrote rxvt-unicode to be able to specify fonts exactly. So don't be
- overwhelmed. A special note: the "9x15bold" mentioend above is actually
+ overwhelmed. A special note: the "9x15bold" mentioned above is actually
the version from XFree-3.3, as XFree-4 replaced it by a totally
different font (different glyphs for ";" and many other harmless
characters), while the second font is actually the "9x15bold" from
XFree4/XOrg. The bold version has less chars than the medium version, so
- I use it for rare characters, too. Whene ditign sources with vim, I use
+ I use it for rare characters, too. When editing sources with vim, I use
italic for comments and other stuff, which looks quite good with
Bitstream Vera anti-aliased.
URxvt.resource: value
If you want to use another form (there are lots of different ways of
- specifying resources), make sure you understand wether and why it works.
- If unsure, use the form above.
+ specifying resources), make sure you understand whether and why it
+ works. If unsure, use the form above.
When I log-in to another system it tells me about missing terminfo data?
The terminal description used by rxvt-unicode is not as widely available
library (Fedora Core's bash is one example) and rely on a termcap entry
for "rxvt-unicode".
- You could use rxvt's termcap entry with resonable results in many cases.
- You can also create a termcap entry by using terminfo's infocmp program
- like this:
+ You could use rxvt's termcap entry with reasonable results in many
+ cases. You can also create a termcap entry by using terminfo's infocmp
+ program like this:
infocmp -C rxvt-unicode
Why does "ls" no longer have coloured output?
The "ls" in the GNU coreutils unfortunately doesn't use terminfo to
- decide wether a terminal has colour, but uses its own configuration
+ decide whether a terminal has colour, but uses its own configuration
file. Needless to say, "rxvt-unicode" is not in its default file (among
with most other terminals supporting colour). Either add:
- Make sure the "XMODIFIERS" environment variable is set correctly when
*starting* rxvt-unicode.
When you want to use e.g. kinput2, it must be set to "@im=kinput2".
- For scim, use "@im=SCIM". Youc an see what input method servers are
+ For scim, use "@im=SCIM". You can see what input method servers are
running with this command:
xprop -root XIM_SERVERS
I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation?
You should build one binary with the default options. configure now
enables most useful options, and the trend goes to making them
- runtime-switchable, too, so there is usually no drawback to enbaling
+ runtime-switchable, too, so there is usually no drawback to enabling
them, except higher disk and possibly memory usage. The perl interpreter
should be enabled, as important functionality (menus, selection, likely
more in the future) depends on it.
I am on FreeBSD and rxvt-unicode does not seem to work at all.
Rxvt-unicode requires the symbol "__STDC_ISO_10646__" to be defined in
your compile environment, or an implementation that implements it,
- wether it defines the symbol or not. "__STDC_ISO_10646__" requires that
+ whether it defines the symbol or not. "__STDC_ISO_10646__" requires that
wchar_t is represented as unicode.
- As you might have guessed, FreeBSD does neither define this symobl nor
+ As you might have guessed, FreeBSD does neither define this symbol nor
does it support it. Instead, it uses its own internal representation of
wchar_t. This is, of course, completely fine with respect to standards.
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"
</p>
<hr />
<h1><a name="synopsis">SYNOPSIS</a></h1>
-<p><strong>urxvt</strong> [options] [-e command [ args ]]</p>
+<p><strong>rxvt</strong> [options] [-e command [ args ]]</p>
<p>
</p>
<hr />
<h1><a name="description">DESCRIPTION</a></h1>
-<p><strong>rxvt-unicode</strong>, version <strong>7.8</strong>, is a colour vt102 terminal
+<p><strong>rxvt-unicode</strong>, version <strong>7.9</strong>, is a colour vt102 terminal
emulator intended as an <em>xterm</em>(1) replacement for users who do not
require features such as Tektronix 4014 emulation and toolkit-style
configurability. As a result, <strong>rxvt-unicode</strong> uses much less swap space --
</p>
<hr />
<h1><a name="frequently_asked_questions">FREQUENTLY ASKED QUESTIONS</a></h1>
-<p>See <code>urxvt(7)</code> (try <code>man 7 urxvt</code>) for a list of
+<p>See <code>rxvt(7)</code> (try <code>man 7 rxvt</code>) for a list of
frequently asked questions and answer to them and some common
problems. That document is also accessible on the World-Wide-Web at
<a href="http://cvs.schmorp.de/browse/*checkout*/rxvt-unicode/doc/rxvt.7.html">http://cvs.schmorp.de/browse/*checkout*/rxvt-unicode/doc/rxvt.7.html</a>.</p>
like mongolian or scripts requiring extremely complex combining rules,
like tibetan or devenagari. Don't expect pretty output when using these
scripts. Most other scripts, latin, cyrillic, kanji, thai etc. should work
-fine, though. A somewhat difficult case are left-to-right scripts, such
+fine, though. A somewhat difficult case are right-to-left scripts, such
as hebrew: <strong>rxvt-unicode</strong> adopts the view that bidirectional algorithms
belong into the application, not the terminal emulator (too many things --
such as cursor-movement while editing -- break otherwise), but that might
change.</p>
<p>If you are looking for a terminal that supports more exotic scripts, let
-me recommend <code>mlterm</code>, which is a very userfriendly, lean and clean
+me recommend <code>mlterm</code>, which is a very user friendly, lean and clean
terminal emulator. In fact, the reason rxvt-unicode was born was solely
because the author couldn't get <code>mlterm</code> to use one font for latin1 and
another for japanese.</p>
to choose any font for any script freely.</p>
<p>Apart from that, rxvt-unicode is also much better internationalised than
its predecessor, supports things such as XFT and ISO 14755 that are handy
-in i18n-environments, is faster, and has a lot less bugs than the original
+in i18n-environments, is faster, and has a lot bugs less than the original
rxvt. This all in addition to dozens of other small improvements.</p>
<p>It is still faithfully following the original rxvt idea of being lean
and nice on resources: for example, you can still configure rxvt-unicode
without most of its features to get a lean binary. It also comes with
a client/daemon pair that lets you open any number of terminal windows
from within a single process, which makes startup time very fast and
-drastically reduces memory usage. See <code>urxvtd(1)</code> (daemon) and
-<code>urxvtc(1)</code> (client).</p>
+drastically reduces memory usage. See <code>rxvtd(1)</code> (daemon) and
+<code>rxvtc(1)</code> (client).</p>
<p>It also makes technical information about escape sequences (which have
-been extended) easier accessible: see <code>urxvt(7)</code> for technical
+been extended) more accessible: see <code>rxvt(7)</code> for technical
reference documentation (escape sequences etc.).</p>
<p>
</p>
<hr />
<h1><a name="options">OPTIONS</a></h1>
-<p>The <strong>urxvt</strong> options (mostly a subset of <em>xterm</em>'s) are listed
+<p>The <strong>rxvt</strong> options (mostly a subset of <em>xterm</em>'s) are listed
below. In keeping with the smaller-is-better philosophy, options may be
eliminated or default values chosen at compile-time, so options and
defaults listed may not accurately reflect the version installed on
-your system. `urxvt -h' gives a list of major compile-time options on
+your system. `rxvt -h' gives a list of major compile-time options on
the <em>Options</em> line. Option descriptions may be prefixed with which
compile option each is dependent upon. e.g. `Compile <em>XIM</em>:' requires
-<em>XIM</em> on the <em>Options</em> line. Note: `urxvt -help' gives a list of all
+<em>XIM</em> on the <em>Options</em> line. Note: `rxvt -help' gives a list of all
command-line options compiled into your version.</p>
-<p>Note that <strong>urxvt</strong> permits the resource name to be used as a
+<p>Note that <strong>rxvt</strong> permits the resource name to be used as a
long-option (--/++ option) so the potential command-line options are
-far greater than those listed. For example: `urxvt --loginShell --color1
+far greater than those listed. For example: `rxvt --loginShell --color1
Orange'.</p>
<p>The following options are available:</p>
<dl>
</dd>
<dd>
<p><em>Please note that transparency of any kind if completely unsupported by
-the author. Don't bug him with installation questions!</em></p>
+the author. Don't bug him with installation questions! Read the FAQ (man 7
+rxvt)!</em></p>
</dd>
</li>
<dt><strong><a name="item__2dfade_number"><strong>-fade</strong> <em>number</em></a></strong>
</dd>
<dd>
<pre>
- urxvt -tr -tint blue -sh 40</pre>
+ rxvt -tr -tint blue -sh 40</pre>
</dd>
</li>
<dt><strong><a name="item__2dsh"><strong>-sh</strong></a></strong>
</dd>
<dd>
<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>
</dd>
<dd>
<p>See also the question ``How does rxvt-unicode choose fonts?'' in the FAQ
-section of urxvt(7).</p>
+section of rxvt(7).</p>
</dd>
</li>
<dt><strong><a name="item__2dfb_fontlist"><strong>-fb</strong> <em>fontlist</em></a></strong>
<dt><strong><a name="item__2de_command__5barguments_5d"><strong>-e</strong> <em>command [arguments]</em></a></strong>
<dd>
-<p>Run the command with its command-line arguments in the <strong>urxvt</strong>
+<p>Run the command with its command-line arguments in the <strong>rxvt</strong>
window; also sets the window title and icon name to be the basename of
the program being executed if neither <em>-title</em> (<em>-T</em>) nor <em>-n</em> are
given on the command line. If this option is used, it must be the last
</dd>
<dd>
<pre>
- urxvt -e sh -c "shell commands"</pre>
+ rxvt -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, 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>
<dt><strong><a name="item__2dembed_windowid"><strong>-embed</strong> <em>windowid</em></a></strong>
<dd>
-<p>Tells urxvt to embed its windows into an already-existing window,
+<p>Tells rxvt to embed its windows into an already-existing window,
which enables applications to easily embed a terminal.</p>
</dd>
<dd>
-<p>Right now, urxvt will first unmap/map the specified window, so it
-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>
+create an extra subwindow for rxvt and leave it alone.</p>
</dd>
<dd>
-<p>The window will not be destroyed when urxvt exits.</p>
+<p>The window will not be destroyed when rxvt exits.</p>
</dd>
<dd>
-<p>It might be useful to know that urxvt will not close file
+<p>It might be useful to know that rxvt will not close file
descriptors passed to it (except for stdin/out/err, of course), so you
can use file descriptors to communicate with the programs within the
-terminal. This works regardless of wether the <code>-embed</code> option was used or
+terminal. This works regardless of whether the <code>-embed</code> option was used or
not.</p>
</dd>
<dd>
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>
</li>
<dt><strong><a name="item__2dpty_2dfd_file_descriptor"><strong>-pty-fd</strong> <em>file descriptor</em></a></strong>
<dd>
-<p>Tells urxvt NOT to execute any commands or create a new pty/tty
-pair but instead use the given filehandle as the tty master. This is
-useful if you want to drive urxvt as a generic terminal emulator
+<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 rxvt as a generic terminal emulator
without having to run a program within it.</p>
</dd>
<dd>
-<p>If this switch is given, urxvt will not create any utmp/wtmp
+<p>If this switch is given, rxvt will not create any utmp/wtmp
entries and will not tinker with pty/tty permissions - you have to do that
yourself if you want that.</p>
</dd>
<pre>
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;</pre>
</dd>
<dd>
</p>
<hr />
<h1><a name="resources__available_also_as_longoptions_">RESOURCES (available also as long-options)</a></h1>
-<p>Note: `urxvt --help' gives a list of all resources (long
+<p>Note: `rxvt --help' gives a list of all resources (long
options) compiled into your version.</p>
<p>You can set and change the resources using X11 tools like <strong>xrdb</strong>. Many
distribution do also load settings from the <strong>~/.Xresources</strong> file when X
-starts. urxvt will consult the following files/resources in order,
+starts. rxvt will consult the following files/resources in order,
with later settings overwriting earlier ones:</p>
<pre>
1. system-wide app-defaults file, either locale-dependent OR global
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>urxvt</strong> recognizes two class
+<p>Note that when reading X resources, <strong>rxvt</strong> recognizes two class
names: <strong>Rxvt</strong> and <strong>URxvt</strong>. The class name <strong>Rxvt</strong> allows resources
-common to both <strong>urxvt</strong> and the original <em>rxvt</em> to be easily
+common to both <strong>rxvt</strong> and the original <em>rxvt</em> to be easily
configured, while the class name <strong>URxvt</strong> allows resources unique to
-<strong>urxvt</strong>, to be shared between different <strong>urxvt</strong>
+<strong>rxvt</strong>, to be shared between different <strong>rxvt</strong>
configurations. If no resources are specified, suitable defaults will
be used. Command-line arguments can be used to override resource
settings. The following resources are supported (you might want to
-check the <code>urxvtperl(3)</code> manpage for additional settings by perl
+check the <code>rxvtperl(3)</code> manpage for additional settings by perl
extensions not documented here):</p>
<dl>
<dt><strong><a name="item_depth_3a_bitdepth"><strong>depth:</strong> <em>bitdepth</em></a></strong>
</dd>
<dd>
<p>Colours higher than 15 cannot be set using resources (yet), but can be
-changed using an escape command (see urxvt(7)).</p>
+changed using an escape command (see rxvt(7)).</p>
</dd>
<dd>
<p>Colours 16-79 form a standard 4x4x4 colour cube (the same as xterm with
<dd>
<p>When font styles are not enabled, or this option is enabled (<strong>True</strong>,
option <strong>-is</strong>, the default), bold and italic font styles imply high
-intensity foreground/backround colours. Disabling this option (<strong>False</strong>,
+intensity foreground/background colours. Disabling this option (<strong>False</strong>,
option <strong>+is</strong>) disables this behaviour, the high intensity colours are not
reachable.</p>
</dd>
</dd>
<dd>
<p>This creates a new file in your home directory with the screen contents
-everytime you hit <code>Print</code>.</p>
+every time you hit <code>Print</code>.</p>
</dd>
</li>
<dt><strong><a name="item_scrollbar_3a_boolean"><strong>scrollBar:</strong> <em>boolean</em></a></strong>
<dd>
<p><strong>True</strong>: scroll with scrollback buffer when tty receives new lines (and
<strong>scrollTtyOutput</strong> is False); option <strong>-sw</strong>. <strong>False</strong>: do not scroll
-with scrollback buffer when tty recieves new lines; option <strong>+sw</strong>.</p>
+with scrollback buffer when tty receives new lines; option <strong>+sw</strong>.</p>
</dd>
</li>
<dt><strong><a name="item_scrollttykeypress_3a_boolean"><strong>scrollTtyKeypress:</strong> <em>boolean</em></a></strong>
</dd>
<dd>
<p>When the selection extension is in use (the default if compiled in, see
-the <code>urxvtperl(3)</code> manpage), a suitable regex using these characters
+the <code>rxvtperl(3)</code> manpage), a suitable regex using these characters
will be created (if the resource exists, otherwise, no regex will be
created). In this mode, characters outside ISO-8859-1 can be used.</p>
</dd>
<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>
<dt><strong><a name="item_hold_3a_boolean"><strong>hold</strong>: <em>boolean</em></a></strong>
<dd>
-<p>Turn on/off hold window after exit support. If enabled, urxvt
+<p>Turn on/off hold window after exit support. If enabled, rxvt
will not immediately destroy its window when the program executed within
it exits. Instead, it will wait till it is being killed or closed by the
user.</p>
<dd>
<p>Please note that you need to double the <code>\</code> in resource files, as
Xlib itself does its own de-escaping (you can use <code>\033</code> instead of
-<code>\e</code> (and so on), which will work with both Xt and urxvt's own
+<code>\e</code> (and so on), which will work with both Xt and rxvt's own
processing).</p>
</dd>
<dd>
<p>You can define a range of keysyms in one shot by providing a <em>string</em>
-with pattern <strong>list/PREFIX/MIDDLE/SUFFIX</strong>, where the delimeter `/'
+with pattern <strong>list/PREFIX/MIDDLE/SUFFIX</strong>, where the delimiter `/'
should be a character not used by the strings.</p>
</dd>
<dd>
</dd>
<dd>
<p>If <em>string</em> takes the form of <code>command:STRING</code>, the specified <strong>STRING</strong>
-is interpreted and executed as urxvt's control sequence. For
+is interpreted and executed as rxvt's control sequence. For
example the following means ``change the current locale to <code>zh_CN.GBK</code>
when Control-Meta-c is being pressed'':</p>
</dd>
</dd>
<dd>
<p>If <em>string</em> takes the form <code>perl:STRING</code>, then the specified <strong>STRING</strong>
-is passed to the <code>on_keyboard_command</code> perl handler. See the <code>urxvtperl(3)</code>
+is passed to the <code>on_keyboard_command</code> perl handler. See the <code>rxvtperl(3)</code>
manpage. For example, the <em>selection</em> extension (activated via
-<code>urxvt -pe selection</code>) listens for <code>selection:rot13</code> events:</p>
+<code>rxvt -pe selection</code>) listens for <code>selection:rot13</code> events:</p>
</dd>
<dd>
<pre>
</dd>
<dd>
<p>Unfortunately, this will override built-in key mappings. For example
-if you overwrite the <code>Insert</code> key you will disable urxvt's
+if you overwrite the <code>Insert</code> key you will disable rxvt's
<code>Shift-Insert</code> mapping. To re-enable that, you can poke ``holes'' into the
user-defined keymap using the <code>builtin:</code> replacement:</p>
</dd>
URxvt.keysym.M-C-2: command:\033]50;9x15bold\007</pre>
</dd>
<dd>
-<p>Other things are possible, e.g. resizing (see <code>urxvt(7)</code> for more
+<p>Other things are possible, e.g. resizing (see <code>rxvt(7)</code> for more
info):</p>
</dd>
<dd>
<dd>
<p>Extension names can also be followed by an argument in angle brackets
(e.g. <code>searchable-scrollback<M-s></code>, which binds the hotkey for
-searchable scorllback to Alt/Meta-s). Mentioning the same extension
+searchable scrollback to Alt/Meta-s). Mentioning the same extension
multiple times with different arguments will pass multiple arguments to
the extension.</p>
</dd>
<dd>
<p>Perl code to be evaluated when all extensions have been registered. See
-the <code>urxvtperl(3)</code> manpage. Due to security reasons, this resource
+the <code>rxvtperl(3)</code> manpage. Due to security reasons, this resource
will be ignored when running setuid/setgid.</p>
</dd>
</li>
<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
-<em>/usr/local/lib/urxvt/perl/</em>. Due to security reasons, this resource
+rxvt will first look in these directories and then in
+<em>/opt/rxvt/lib/urxvt/perl/</em>. Due to security reasons, this resource
will be ignored when running setuid/setgid.</p>
</dd>
<dd>
-<p>See the <code>urxvtperl(3)</code> manpage.</p>
+<p>See the <code>rxvtperl(3)</code> manpage.</p>
</dd>
</li>
<dt><strong><a name="item_selection_2epattern_2didx_3a_perl_2dregex"><strong>selection.pattern-<em>idx</em> </strong>>: <em>perl-regex</em></a></strong>
<dd>
-<p>Additional selection patterns, see the <code>urxvtperl(3)</code> manpage for
+<p>Additional selection patterns, see the <code>rxvtperl(3)</code> manpage for
details.</p>
</dd>
</li>
<dt><strong><a name="item_selection_2dautotransform_2eidx_3a_perl_2dtransfor"><strong>selection-autotransform.<em>idx</em> </strong>>: <em>perl-transform</em></a></strong>
<dd>
-<p>Selection auto-transform patterns, see the <code>urxvtperl(3)</code> manpage
+<p>Selection auto-transform patterns, see the <code>rxvtperl(3)</code> manpage
for details.</p>
</dd>
</li>
</p>
<hr />
<h1><a name="the_scrollbar">THE SCROLLBAR</a></h1>
-<p>Lines of text that scroll off the top of the <strong>urxvt</strong> window
+<p>Lines of text that scroll off the top of the <strong>rxvt</strong> window
(resource: <strong>saveLines</strong>) and can be scrolled back using the scrollbar
-or by keystrokes. The normal <strong>urxvt</strong> scrollbar has arrows and
+or by keystrokes. The normal <strong>rxvt</strong> scrollbar has arrows and
its behaviour is fairly intuitive. The <strong>xterm-scrollbar</strong> is without
arrows and its behaviour mimics that of <em>xterm</em></p>
<p>Scroll down with <strong>Button1</strong> (<strong>xterm-scrollbar</strong>) or <strong>Shift-Next</strong>.
<dt><strong><a name="item_insertion_3a"><strong>Insertion</strong>:</a></strong>
<dd>
-<p>Pressing and releasing the Middle mouse button in an <strong>urxvt</strong>
+<p>Pressing and releasing the Middle mouse button in an <strong>rxvt</strong>
window causes the value of the PRIMARY selection (or CLIPBOARD with the
Meta modifier) to be inserted as if it had been typed on the keyboard.</p>
</dd>
</p>
<hr />
<h1><a name="login_stamp">LOGIN STAMP</a></h1>
-<p><strong>urxvt</strong> tries to write an entry into the <em>utmp</em>(5) file so that
+<p><strong>rxvt</strong> tries to write an entry into the <em>utmp</em>(5) file so that
it can be seen via the <em>who(1)</em> command, and can accept messages. To
-allow this feature, <strong>urxvt</strong> may need to be installed setuid root
+allow this feature, <strong>rxvt</strong> may need to be installed setuid root
on some systems or setgid to root or to some other group on others.</p>
<p>
</p>
<hr />
<h1><a name="colors_and_graphics">COLORS AND GRAPHICS</a></h1>
<p>In addition to the default foreground and background colours,
-<strong>urxvt</strong> can display up to 16 colours (8 ANSI colours plus
+<strong>rxvt</strong> can display up to 16 colours (8 ANSI colours plus
high-intensity bold/blink versions of the same). Here is a list of the
colours with their names.</p>
<table>
<strong>background</strong>, <strong>cursorColor</strong>, <strong>cursorColor2</strong>, <strong>colorBD</strong>, <strong>colorUL</strong> as
a number 0-15, as a convenient shorthand to reference the colour name of
color0-color15.</p>
-<p>In addition to the colours defined above, urxvt offers an
+<p>In addition to the colours defined above, rxvt offers an
additional 72 colours. The first 64 of those (with indices 16 to 79)
consist of a 4*4*4 RGB colour cube (i.e. <em>index = r * 16 + g * 4 + b +
16</em>), followed by 8 additional shades of gray (with indices 80 to 87).</p>
<em>xterm</em>(1) where the colours are only swapped if they have not otherwise
been specified. For example,</p>
<dl>
-<dt><strong><a name="item_urxvt__2dfg_black__2dbg_white__2drv"><strong>urxvt -fg Black -bg White -rv</strong></a></strong>
+<dt><strong><a name="item_rxvt__2dfg_black__2dbg_white__2drv"><strong>rxvt -fg Black -bg White -rv</strong></a></strong>
<dd>
<p>would yield White on Black, while on <em>xterm</em>(1) it would yield Black
<p>For example, the following selects an almost completely transparent red
background, and an almost opaque pink foreground:</p>
<pre>
- urxvt -depth 32 -bg rgba:0000/0000/0000/2222 -fg "[e]pink"</pre>
+ rxvt -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>urxvt</strong> sets and/or uses the following environment variables:</p>
+<p><strong>rxvt</strong> sets and/or uses the following environment variables:</p>
<dl>
<dt><strong><a name="item_term"><strong>TERM</strong></a></strong>
<dd>
<p>Normally set to <code>rxvt-unicode</code>, unless overwritten at configure time, via
-resources or on the commandline.</p>
+resources or on the command line.</p>
</dd>
</li>
<dt><strong><a name="item_colorterm"><strong>COLORTERM</strong></a></strong>
<dd>
-<p>Either <code>rxvt</code>, <code>rxvt-xpm</code>, depending on wether urxvt was
+<p>Either <code>rxvt</code>, <code>rxvt-xpm</code>, depending on whether rxvt was
compiled with XPM support, and optionally with the added extension
<code>-mono</code> to indicate that rxvt-unicode runs on a monochrome screen.</p>
</dd>
the colour code used as default foreground/text colour (or the string
<code>default</code> to indicate that the default-colour escape sequence is to be
used), <code>bg</code> is the colour code used as default background colour (or the
-string <code>default</code>), and <code>xpm</code> is the string <code>default</code> if urxvt
+string <code>default</code>), and <code>xpm</code> is the string <code>default</code> if rxvt
was compiled with XPM support. Libraries like <code>ncurses</code> and <code>slang</code> can
(and do) use this information to optimize screen output.</p>
</dd>
<dt><strong><a name="item_windowid"><strong>WINDOWID</strong></a></strong>
<dd>
-<p>Set to the (decimal) X Window ID of the urxvt window (the toplevel
+<p>Set to the (decimal) X Window ID of the rxvt window (the toplevel
window, which usually has subwindows for the scrollbar, the terminal
window and so on).</p>
</dd>
<dt><strong><a name="item_terminfo"><strong>TERMINFO</strong></a></strong>
<dd>
-<p>Set to the terminfo directory iff urxvt was configured with
+<p>Set to the terminfo directory iff rxvt was configured with
<code>--with-terminfo=PATH</code>.</p>
</dd>
</li>
<dt><strong><a name="item_display"><strong>DISPLAY</strong></a></strong>
<dd>
-<p>Used by urxvt to connect to the display and set to the correct
+<p>Used by rxvt to connect to the display and set to the correct
display in its child processes.</p>
</dd>
</li>
<dt><strong><a name="item_rxvt_socket"><strong>RXVT_SOCKET</strong></a></strong>
<dd>
-<p>The unix domain socket path used by <code>urxvtc(1)</code> and
-urxvtd(1).</p>
+<p>The unix domain socket path used by <code>rxvtc(1)</code> and
+rxvtd(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
-urxvt.</p>
+rxvt.</p>
</dd>
</li>
</dl>
</p>
<hr />
<h1><a name="see_also">SEE ALSO</a></h1>
-<p>urxvt(7), urxvtc(1), urxvtd(1), xterm(1), sh(1), resize(1), X(1), pty(4), tty(4), <code>utmp(5)</code></p>
+<p>rxvt(7), rxvtc(1), rxvtd(1), xterm(1), sh(1), resize(1), X(1), pty(4), tty(4), <code>utmp(5)</code></p>
<p>
</p>
<hr />
.\" ========================================================================
.\"
.IX Title "@@RXVT_NAME@@ 1"
-.TH @@RXVT_NAME@@ 1 "2006-07-17" "7.8" "RXVT-UNICODE"
+.TH @@RXVT_NAME@@ 1 "2006-08-07" "7.9" "RXVT-UNICODE"
.SH "NAME"
rxvt\-unicode (ouR XVT, unicode) \- (a VT102 emulator for the X window system)
.SH "SYNOPSIS"
like mongolian or scripts requiring extremely complex combining rules,
like tibetan or devenagari. Don't expect pretty output when using these
scripts. Most other scripts, latin, cyrillic, kanji, thai etc. should work
-fine, though. A somewhat difficult case are left-to-right scripts, such
+fine, though. A somewhat difficult case are right-to-left scripts, such
as hebrew: \fBrxvt-unicode\fR adopts the view that bidirectional algorithms
belong into the application, not the terminal emulator (too many things \*(--
such as cursor-movement while editing \*(-- break otherwise), but that might
change.
.PP
If you are looking for a terminal that supports more exotic scripts, let
-me recommend \f(CW\*(C`mlterm\*(C'\fR, which is a very userfriendly, lean and clean
+me recommend \f(CW\*(C`mlterm\*(C'\fR, which is a very user friendly, lean and clean
terminal emulator. In fact, the reason rxvt-unicode was born was solely
because the author couldn't get \f(CW\*(C`mlterm\*(C'\fR to use one font for latin1 and
another for japanese.
.PP
Apart from that, rxvt-unicode is also much better internationalised than
its predecessor, supports things such as \s-1XFT\s0 and \s-1ISO\s0 14755 that are handy
-in i18n\-environments, is faster, and has a lot less bugs than the original
+in i18n\-environments, is faster, and has a lot bugs less than the original
rxvt. This all in addition to dozens of other small improvements.
.PP
It is still faithfully following the original rxvt idea of being lean
@@RXVT_NAME@@c(1) (client).
.PP
It also makes technical information about escape sequences (which have
-been extended) easier accessible: see @@RXVT_NAME@@(7) for technical
+been extended) more accessible: see @@RXVT_NAME@@(7) for technical
reference documentation (escape sequences etc.).
.SH "OPTIONS"
.IX Header "OPTIONS"
\&\fB\-tr\fR; resource \fBinheritPixmap\fR.
.Sp
\&\fIPlease note that transparency of any kind if completely unsupported by
-the author. Don't bug him with installation questions!\fR
+the author. Don't bug him with installation questions! Read the \s-1FAQ\s0 (man 7
+@@RXVT_NAME@@)!\fR
.IP "\fB\-fade\fR \fInumber\fR" 4
.IX Item "-fade number"
Fade the text by the given percentage when focus is lost. Small values
It might be useful to know that @@RXVT_NAME@@ 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 \f(CW\*(C`\-embed\*(C'\fR option was used or
+terminal. This works regardless of whether the \f(CW\*(C`\-embed\*(C'\fR option was used or
not.
.Sp
Here is a short Gtk2\-perl snippet that illustrates how this option can be
.IP "\fB\-pty\-fd\fR \fIfile descriptor\fR" 4
.IX Item "-pty-fd file descriptor"
Tells @@RXVT_NAME@@ \s-1NOT\s0 to execute any commands or create a new pty/tty
-pair but instead use the given filehandle as the tty master. This is
+pair but instead use the given file descriptor as the tty master. This is
useful if you want to drive @@RXVT_NAME@@ as a generic terminal emulator
without having to run a program within it.
.Sp
.IX Item "intensityStyles: boolean"
When font styles are not enabled, or this option is enabled (\fBTrue\fR,
option \fB\-is\fR, the default), bold and italic font styles imply high
-intensity foreground/backround colours. Disabling this option (\fBFalse\fR,
+intensity foreground/background colours. Disabling this option (\fBFalse\fR,
option \fB+is\fR) disables this behaviour, the high intensity colours are not
reachable.
.IP "\fBselectstyle:\fR \fImode\fR" 4
.Ve
.Sp
This creates a new file in your home directory with the screen contents
-everytime you hit \f(CW\*(C`Print\*(C'\fR.
+every time you hit \f(CW\*(C`Print\*(C'\fR.
.IP "\fBscrollBar:\fR \fIboolean\fR" 4
.IX Item "scrollBar: boolean"
\&\fBTrue\fR: enable the scrollbar [default]; option \fB\-sb\fR. \fBFalse\fR:
.IX Item "scrollWithBuffer: boolean"
\&\fBTrue\fR: scroll with scrollback buffer when tty receives new lines (and
\&\fBscrollTtyOutput\fR is False); option \fB\-sw\fR. \fBFalse\fR: do not scroll
-with scrollback buffer when tty recieves new lines; option \fB+sw\fR.
+with scrollback buffer when tty receives new lines; option \fB+sw\fR.
.IP "\fBscrollTtyKeypress:\fR \fIboolean\fR" 4
.IX Item "scrollTtyKeypress: boolean"
\&\fBTrue\fR: scroll to bottom when a non-special key is pressed. Special keys
processing).
.Sp
You can define a range of keysyms in one shot by providing a \fIstring\fR
-with pattern \fBlist/PREFIX/MIDDLE/SUFFIX\fR, where the delimeter `/'
+with pattern \fBlist/PREFIX/MIDDLE/SUFFIX\fR, where the delimiter `/'
should be a character not used by the strings.
.Sp
Its usage can be demonstrated by an example:
.Sp
Extension names can also be followed by an argument in angle brackets
(e.g. \f(CW\*(C`searchable\-scrollback<M\-s>\*(C'\fR, which binds the hotkey for
-searchable scorllback to Alt/Meta\-s). Mentioning the same extension
+searchable scrollback to Alt/Meta\-s). Mentioning the same extension
multiple times with different arguments will pass multiple arguments to
the extension.
.Sp
.IP "\fB\s-1TERM\s0\fR" 4
.IX Item "TERM"
Normally set to \f(CW\*(C`rxvt\-unicode\*(C'\fR, unless overwritten at configure time, via
-resources or on the commandline.
+resources or on the command line.
.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 wether @@RXVT_NAME@@ was
+Either \f(CW\*(C`rxvt\*(C'\fR, \f(CW\*(C`rxvt\-xpm\*(C'\fR, depending on whether @@RXVT_NAME@@ was
compiled with \s-1XPM\s0 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
system)
SYNOPSIS
- urxvt [options] [-e command [ args ]]
+ rxvt [options] [-e command [ args ]]
DESCRIPTION
- rxvt-unicode, version 7.8, is a colour vt102 terminal emulator intended
+ rxvt-unicode, version 7.9, 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 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/*checkout*/rxvt-unicode/doc/rxvt.7.html>.
RXVT-UNICODE VS. RXVT
scripts like mongolian or scripts requiring extremely complex combining
rules, like tibetan or devenagari. Don't expect pretty output when using
these scripts. Most other scripts, latin, cyrillic, kanji, thai etc.
- should work fine, though. A somewhat difficult case are left-to-right
+ should work fine, though. A somewhat difficult case are right-to-left
scripts, such as hebrew: rxvt-unicode adopts the view that bidirectional
algorithms belong into the application, not the terminal emulator (too
many things -- such as cursor-movement while editing -- break
otherwise), but that might change.
If you are looking for a terminal that supports more exotic scripts, let
- me recommend "mlterm", which is a very userfriendly, lean and clean
+ me recommend "mlterm", which is a very user friendly, lean and clean
terminal emulator. In fact, the reason rxvt-unicode was born was solely
because the author couldn't get "mlterm" to use one font for latin1 and
another for japanese.
Apart from that, rxvt-unicode is also much better internationalised than
its predecessor, supports things such as XFT and ISO 14755 that are
- handy in i18n-environments, is faster, and has a lot less bugs than the
+ handy in i18n-environments, is faster, and has a lot bugs less than the
original rxvt. This all in addition to dozens of other small
improvements.
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) easier 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:
-tr; resource inheritPixmap.
*Please note that transparency of any kind if completely unsupported
- by the author. Don't bug him with installation questions!*
+ by the author. Don't bug him with installation questions! Read the
+ FAQ (man 7 rxvt)!*
-fade *number*
Fade the text by the given percentage when focus is lost. Small
be used to brighten or darken the image in addition to tinting it;
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 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.:
- 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 wether 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
- but instead use the given filehandle as the tty master. This is
- useful if you want to drive urxvt as a generic terminal emulator
+ 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 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.
intensityStyles: *boolean*
When font styles are not enabled, or this option is enabled (True,
option -is, the default), bold and italic font styles imply high
- intensity foreground/backround colours. Disabling this option
+ intensity foreground/background colours. Disabling this option
(False, option +is) disables this behaviour, the high intensity
colours are not reachable.
URxvt.print-pipe: cat > $(TMPDIR=$HOME mktemp urxvt.XXXXXX)
This creates a new file in your home directory with the screen
- contents everytime you hit "Print".
+ contents every time you hit "Print".
scrollBar: *boolean*
True: enable the scrollbar [default]; option -sb. False: disable the
scrollWithBuffer: *boolean*
True: scroll with scrollback buffer when tty receives new lines (and
scrollTtyOutput is False); option -sw. False: do not scroll with
- scrollback buffer when tty recieves new lines; option +sw.
+ scrollback buffer when tty receives new lines; option +sw.
scrollTtyKeypress: *boolean*
True: scroll to bottom when a non-special key is pressed. Special
(whitespace delimiting is added automatically if resource is given).
When the selection extension is in use (the default if compiled in,
- see the urxvtperl(3) manpage), a suitable regex using these
+ 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.
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.
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 urxvt's own
+ "\e" (and so on), which will work with both Xt and rxvt's own
processing).
You can define a range of keysyms in one shot by providing a
- *string* with pattern list/PREFIX/MIDDLE/SUFFIX, where the delimeter
+ *string* with pattern list/PREFIX/MIDDLE/SUFFIX, where the delimiter
`/' should be a character not used by the strings.
Its usage can be demonstrated by an example:
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
Extension names can also be followed by an argument in angle
brackets (e.g. "searchable-scrollback<M-s>", which binds the hotkey
- for searchable scorllback to Alt/Meta-s). Mentioning the same
+ for searchable scrollback to Alt/Meta-s). Mentioning the same
extension multiple times with different arguments will pass multiple
arguments to the extension.
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*
-override-redirect.
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.
Insertion:
- 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/2222 -fg "[e]pink"
+ rxvt -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
- 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 commandline.
+ time, via resources or on the command line.
COLORTERM
- Either "rxvt", "rxvt-xpm", depending on wether urxvt was compiled
+ Either "rxvt", "rxvt-xpm", depending on whether rxvt 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 urxvt was compiled with XPM support. Libraries like "ncurses" and
+ if rxvt 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 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
<li><a href="#rxvtunicode_uses_gobs_of_memory__how_can_i_reduce_that">Rxvt-unicode uses gobs of memory, how can I reduce that?</a></li>
<li><a href="#how_can_i_start_urxvtd_in_a_racefree_way">How can I start urxvtd in a race-free way?</a></li>
<li><a href="#how_can_i_start_urxvtd_automatically_when_i_run_urxvt_name__c">How can I start urxvtd automatically when I run URXVT_NAME@@c?</a></li>
- <li><a href="#how_do_i_distinguish_wether_i_m_running_rxvtunicode_or_a_regular_xterm_i_need_this_to_decide_about_setting_colors_etc_">How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc.</a></li>
+ <li><a href="#how_do_i_distinguish_whether_i_m_running_rxvtunicode_or_a_regular_xterm_i_need_this_to_decide_about_setting_colors_etc_">How do I distinguish whether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc.</a></li>
<li><a href="#how_do_i_set_the_correct__full_ip_address_for_the_display_variable">How do I set the correct, full IP address for the DISPLAY variable?</a></li>
<li><a href="#how_do_i_compile_the_manual_pages_on_my_own">How do I compile the manual pages on my own?</a></li>
<li><a href="#isn_t_rxvtunicode_supposed_to_be_small_don_t_all_those_features_bloat">Isn't rxvt-unicode supposed to be small? Don't all those features bloat?</a></li>
existing daemon.</p>
<p>
</p>
-<h3><a name="how_do_i_distinguish_wether_i_m_running_rxvtunicode_or_a_regular_xterm_i_need_this_to_decide_about_setting_colors_etc_">How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc.</a></h3>
+<h3><a name="how_do_i_distinguish_whether_i_m_running_rxvtunicode_or_a_regular_xterm_i_need_this_to_decide_about_setting_colors_etc_">How do I distinguish whether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc.</a></h3>
<p>The original rxvt and rxvt-unicode always export the variable ``COLORTERM'',
so you can check and see if that is set. Note that several programs, JED,
slrn, Midnight Commander automatically check this variable to decide
188985 9048 66616 18222 1788 urxvt --disable-everything</pre>
<p>When you <a href="#item__2d_2denable_2deverything"><code>--enable-everything</code></a> (which <em>is</em> unfair, as this involves xft
and full locale/XIM support which are quite bloaty inside libX11 and my
-libc), the two diverge, but not unreasnobaly so.</p>
+libc), the two diverge, but not unreasonably so.</p>
<pre>
text data bss drs rss filename
163431 2152 24 20123 2060 rxvt --enable-everything
urxvt -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc</pre>
<p>This requires XFT support, and the support of your X-server. If that
doesn't work for you, blame Xorg and Keith Packard. ARGB visuals aren't
-there yet, no matter what they claim. Rxvt-Unicode contains the neccessary
+there yet, no matter what they claim. Rxvt-Unicode contains the necessary
bugfixes and workarounds for Xft and Xlib to make it work, but that
doesn't mean that your WM has the required kludges in place.</p>
<p>4. Use xcompmgr and let it do the job:</p>
box, and rxvt-unicode has no way of detecting this (the correct way is to
ask for the character bounding box, which unfortunately is wrong in these
cases).</p>
-<p>It's not clear (to me at least), wether this is a bug in Xft, freetype,
+<p>It's not clear (to me at least), whether this is a bug in Xft, freetype,
or the respective font. If you encounter this problem you might try using
the <code>-lsp</code> option to give the font more height. If that doesn't work, you
might be forced to use a different font.</p>
line that contains it. It tries hard not to do this at the wrong moment,
but when running a program that doesn't parse cursor movements or in some
cases during rlogin sessions, it fails to detect this properly.</p>
-<p>You can permamently switch this feature off by disabling the <code>readline</code>
+<p>You can permanently switch this feature off by disabling the <code>readline</code>
extension:</p>
<pre>
URxvt.perl-ext-common: default,-readline</pre>
<h3><a name="my_numerical_keypad_acts_weird_and_generates_differing_output">My numerical keypad acts weird and generates differing output?</a></h3>
<p>Some Debian GNUL/Linux users seem to have this problem, although no
specific details were reported so far. It is possible that this is caused
-by the wrong <code>TERM</code> setting, although the details of wether and how
+by the wrong <code>TERM</code> setting, although the details of whether and how
this can happen are unknown, as <code>TERM=rxvt</code> should offer a compatible
keymap. See the answer to the previous question, and please report if that
helped.</p>
</p>
<h3><a name="what_s_with_the_strange_backspace_delete_key_behaviour">What's with the strange Backspace/Delete key behaviour?</a></h3>
<p>Assuming that the physical Backspace key corresponds to the
-BackSpace keysym (not likely for Linux ... see the following
+Backspace keysym (not likely for Linux ... see the following
question) there are two standard values that can be used for
Backspace: <code>^H</code> and <code>^?</code>.</p>
<p>Historically, either value is correct, but rxvt-unicode adopts the debian
develop for myself mostly, so I actually use most of the extensions I
write.</p>
<p>The selection stuff mainly makes the selection perl-error-message aware
-and tells it to convert pelr error mssages into vi-commands to load the
+and tells it to convert perl error messages into vi-commands to load the
relevant file and go tot he error line number.</p>
<pre>
URxvt.scrollstyle: plain
URxvt.secondaryScroll: true</pre>
<p>As the documentation says: plain is the preferred scrollbar for the
-author. The <code>secondaryScroll</code> confgiures urxvt to scroll in full-screen
-apps, like screen, so lines scorlled out of screen end up in urxvt's
+author. The <code>secondaryScroll</code> configures urxvt to scroll in full-screen
+apps, like screen, so lines scrolled out of screen end up in urxvt's
scrollback buffer.</p>
<pre>
URxvt.background: #000000
urxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
urxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true</pre>
<p>I wrote rxvt-unicode to be able to specify fonts exactly. So don't be
-overwhelmed. A special note: the <code>9x15bold</code> mentioend above is actually
+overwhelmed. A special note: the <code>9x15bold</code> mentioned above is actually
the version from XFree-3.3, as XFree-4 replaced it by a totally different
font (different glyphs for <code>;</code> and many other harmless characters),
while the second font is actually the <code>9x15bold</code> from XFree4/XOrg. The
bold version has less chars than the medium version, so I use it for rare
-characters, too. Whene ditign sources with vim, I use italic for comments
+characters, too. When editing sources with vim, I use italic for comments
and other stuff, which looks quite good with Bitstream Vera anti-aliased.</p>
<p>Terminus is a quite bad font (many very wrong glyphs), but for most of my
purposes, it works, and gives a different look, as my normal (Non-bold)
<pre>
URxvt.resource: value</pre>
<p>If you want to use another form (there are lots of different ways of
-specifying resources), make sure you understand wether and why it
+specifying resources), make sure you understand whether and why it
works. If unsure, use the form above.</p>
<p>
</p>
systems still compile some programs using the long-obsoleted termcap
library (Fedora Core's bash is one example) and rely on a termcap entry
for <code>rxvt-unicode</code>.</p>
-<p>You could use rxvt's termcap entry with resonable results in many cases.
+<p>You could use rxvt's termcap entry with reasonable results in many cases.
You can also create a termcap entry by using terminfo's infocmp program
like this:</p>
<pre>
</p>
<h3><a name="why_does_ls_no_longer_have_coloured_output">Why does <code>ls</code> no longer have coloured output?</a></h3>
<p>The <code>ls</code> in the GNU coreutils unfortunately doesn't use terminfo to
-decide wether a terminal has colour, but uses its own configuration
+decide whether a terminal has colour, but uses its own configuration
file. Needless to say, <code>rxvt-unicode</code> is not in its default file (among
with most other terminals supporting colour). Either add:</p>
<pre>
<dd>
<p>When you want to use e.g. <strong>kinput2</strong>, it must be set to
-<code>@im=kinput2</code>. For <strong>scim</strong>, use <code>@im=SCIM</code>. Youc an see what input
+<code>@im=kinput2</code>. For <strong>scim</strong>, use <code>@im=SCIM</code>. You can see what input
method servers are running with this command:</p>
</dd>
<dd>
<h3><a name="i_am_maintaining_rxvtunicode_for_distribution_os_xxx__any_recommendation">I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation?</a></h3>
<p>You should build one binary with the default options. <em>configure</em>
now enables most useful options, and the trend goes to making them
-runtime-switchable, too, so there is usually no drawback to enbaling them,
+runtime-switchable, too, so there is usually no drawback to enabling them,
except higher disk and possibly memory usage. The perl interpreter should
be enabled, as important functionality (menus, selection, likely more in
the future) depends on it.</p>
<h3><a name="i_am_on_freebsd_and_rxvtunicode_does_not_seem_to_work_at_all_">I am on FreeBSD and rxvt-unicode does not seem to work at all.</a></h3>
<p>Rxvt-unicode requires the symbol <code>__STDC_ISO_10646__</code> to be defined
in your compile environment, or an implementation that implements it,
-wether it defines the symbol or not. <code>__STDC_ISO_10646__</code> requires that
+whether it defines the symbol or not. <code>__STDC_ISO_10646__</code> requires that
<strong>wchar_t</strong> is represented as unicode.</p>
-<p>As you might have guessed, FreeBSD does neither define this symobl nor
+<p>As you might have guessed, FreeBSD does neither define this symbol nor
does it support it. Instead, it uses its own internal representation of
<strong>wchar_t</strong>. This is, of course, completely fine with respect to standards.</p>
<p>However, that means rxvt-unicode only works in <code>POSIX</code>, <code>ISO-8859-1</code> and
<dt><strong><a name="item_iso14755">--enable-iso14755 (default: on)</a></strong>
<dd>
-<p>Enable extended ISO 14755 support (see urxvt(1), or
+<p>Enable extended ISO 14755 support (see rxvt(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>urxvtperl(3)</strong>
+<p>Enable an embedded perl interpreter. See the <strong>rxvtperl(3)</strong>
manpage (<em>doc/rxvtperl.txt</em>) for more info on this feature, or the files
in <em>src/perl-ext/</em> for the extensions that are installed by default. The
perl interpreter that is used can be specified via the <code>PERL</code> environment
.\" ========================================================================
.\"
.IX Title "@@RXVT_NAME@@ 7"
-.TH @@RXVT_NAME@@ 7 "2006-07-17" "7.8" "RXVT-UNICODE"
+.TH @@RXVT_NAME@@ 7 "2006-08-07" "7.9" "RXVT-UNICODE"
.SH "NAME"
RXVT REFERENCE \- FAQ, command sequences and other background information
.SH "SYNOPSIS"
re-run the command. Subsequent invocations of the script will re-use the
existing daemon.
.PP
-\fIHow do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc.\fR
-.IX Subsection "How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc."
+\fIHow do I distinguish whether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc.\fR
+.IX Subsection "How do I distinguish whether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc."
.PP
The original rxvt and rxvt-unicode always export the variable \*(L"\s-1COLORTERM\s0\*(R",
so you can check and see if that is set. Note that several programs, \s-1JED\s0,
.PP
When you \f(CW\*(C`\-\-enable\-everything\*(C'\fR (which \fIis\fR unfair, as this involves xft
and full locale/XIM support which are quite bloaty inside libX11 and my
-libc), the two diverge, but not unreasnobaly so.
+libc), the two diverge, but not unreasonably so.
.PP
.Vb 3
\& text data bss drs rss filename
.PP
This requires \s-1XFT\s0 support, and the support of your X\-server. If that
doesn't work for you, blame Xorg and Keith Packard. \s-1ARGB\s0 visuals aren't
-there yet, no matter what they claim. Rxvt-Unicode contains the neccessary
+there yet, no matter what they claim. Rxvt-Unicode contains the necessary
bugfixes and workarounds for Xft and Xlib to make it work, but that
doesn't mean that your \s-1WM\s0 has the required kludges in place.
.PP
ask for the character bounding box, which unfortunately is wrong in these
cases).
.PP
-It's not clear (to me at least), wether this is a bug in Xft, freetype,
+It's not clear (to me at least), whether this is a bug in Xft, freetype,
or the respective font. If you encounter this problem you might try using
the \f(CW\*(C`\-lsp\*(C'\fR option to give the font more height. If that doesn't work, you
might be forced to use a different font.
but when running a program that doesn't parse cursor movements or in some
cases during rlogin sessions, it fails to detect this properly.
.PP
-You can permamently switch this feature off by disabling the \f(CW\*(C`readline\*(C'\fR
+You can permanently switch this feature off by disabling the \f(CW\*(C`readline\*(C'\fR
extension:
.PP
.Vb 1
.PP
Some Debian GNUL/Linux users seem to have this problem, although no
specific details were reported so far. It is possible that this is caused
-by the wrong \f(CW\*(C`TERM\*(C'\fR setting, although the details of wether and how
+by the wrong \f(CW\*(C`TERM\*(C'\fR setting, although the details of whether and how
this can happen are unknown, as \f(CW\*(C`TERM=rxvt\*(C'\fR should offer a compatible
keymap. See the answer to the previous question, and please report if that
helped.
.IX Subsection "What's with the strange Backspace/Delete key behaviour?"
.PP
Assuming that the physical Backspace key corresponds to the
-BackSpace keysym (not likely for Linux ... see the following
+Backspace keysym (not likely for Linux ... see the following
question) there are two standard values that can be used for
Backspace: \f(CW\*(C`^H\*(C'\fR and \f(CW\*(C`^?\*(C'\fR.
.PP
write.
.PP
The selection stuff mainly makes the selection perl-error-message aware
-and tells it to convert pelr error mssages into vi-commands to load the
+and tells it to convert perl error messages into vi-commands to load the
relevant file and go tot he error line number.
.PP
.Vb 2
.Ve
.PP
As the documentation says: plain is the preferred scrollbar for the
-author. The \f(CW\*(C`secondaryScroll\*(C'\fR confgiures urxvt to scroll in full-screen
-apps, like screen, so lines scorlled out of screen end up in urxvt's
+author. The \f(CW\*(C`secondaryScroll\*(C'\fR configures urxvt to scroll in full-screen
+apps, like screen, so lines scrolled out of screen end up in urxvt's
scrollback buffer.
.PP
.Vb 7
.Ve
.PP
I wrote rxvt-unicode to be able to specify fonts exactly. So don't be
-overwhelmed. A special note: the \f(CW\*(C`9x15bold\*(C'\fR mentioend above is actually
+overwhelmed. A special note: the \f(CW\*(C`9x15bold\*(C'\fR mentioned above is actually
the version from XFree\-3.3, as XFree\-4 replaced it by a totally different
font (different glyphs for \f(CW\*(C`;\*(C'\fR and many other harmless characters),
while the second font is actually the \f(CW\*(C`9x15bold\*(C'\fR from XFree4/XOrg. The
bold version has less chars than the medium version, so I use it for rare
-characters, too. Whene ditign sources with vim, I use italic for comments
+characters, too. When editing sources with vim, I use italic for comments
and other stuff, which looks quite good with Bitstream Vera anti\-aliased.
.PP
Terminus is a quite bad font (many very wrong glyphs), but for most of my
.Ve
.PP
If you want to use another form (there are lots of different ways of
-specifying resources), make sure you understand wether and why it
+specifying resources), make sure you understand whether and why it
works. If unsure, use the form above.
.PP
\fIWhen I log-in to another system it tells me about missing terminfo data?\fR
library (Fedora Core's bash is one example) and rely on a termcap entry
for \f(CW\*(C`rxvt\-unicode\*(C'\fR.
.PP
-You could use rxvt's termcap entry with resonable results in many cases.
+You could use rxvt's termcap entry with reasonable results in many cases.
You can also create a termcap entry by using terminfo's infocmp program
like this:
.PP
.IX Subsection "Why does ls no longer have coloured output?"
.PP
The \f(CW\*(C`ls\*(C'\fR in the \s-1GNU\s0 coreutils unfortunately doesn't use terminfo to
-decide wether a terminal has colour, but uses its own configuration
+decide whether a terminal has colour, but uses its own configuration
file. Needless to say, \f(CW\*(C`rxvt\-unicode\*(C'\fR is not in its default file (among
with most other terminals supporting colour). Either add:
.PP
.IX Item "- Make sure the XMODIFIERS environment variable is set correctly when starting rxvt-unicode."
.PD
When you want to use e.g. \fBkinput2\fR, it must be set to
-\&\f(CW\*(C`@im=kinput2\*(C'\fR. For \fBscim\fR, use \f(CW\*(C`@im=SCIM\*(C'\fR. Youc an see what input
+\&\f(CW\*(C`@im=kinput2\*(C'\fR. For \fBscim\fR, use \f(CW\*(C`@im=SCIM\*(C'\fR. You can see what input
method servers are running with this command:
.Sp
.Vb 1
.PP
You should build one binary with the default options. \fIconfigure\fR
now enables most useful options, and the trend goes to making them
-runtime\-switchable, too, so there is usually no drawback to enbaling them,
+runtime\-switchable, too, so there is usually no drawback to enabling them,
except higher disk and possibly memory usage. The perl interpreter should
be enabled, as important functionality (menus, selection, likely more in
the future) depends on it.
.PP
Rxvt-unicode requires the symbol \f(CW\*(C`_\|_STDC_ISO_10646_\|_\*(C'\fR to be defined
in your compile environment, or an implementation that implements it,
-wether it defines the symbol or not. \f(CW\*(C`_\|_STDC_ISO_10646_\|_\*(C'\fR requires that
+whether it defines the symbol or not. \f(CW\*(C`_\|_STDC_ISO_10646_\|_\*(C'\fR requires that
\&\fBwchar_t\fR is represented as unicode.
.PP
-As you might have guessed, FreeBSD does neither define this symobl nor
+As you might have guessed, FreeBSD does neither define this symbol nor
does it support it. Instead, it uses its own internal representation of
\&\fBwchar_t\fR. This is, of course, completely fine with respect to standards.
.PP
re-run the command. Subsequent invocations of the script will re-use the
existing daemon.
- How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc.
+ How do I distinguish whether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc.
The original rxvt and rxvt-unicode always export the variable
"COLORTERM", so you can check and see if that is set. Note that several
programs, JED, slrn, Midnight Commander automatically check this
When you "--enable-everything" (which *is* unfair, as this involves xft
and full locale/XIM support which are quite bloaty inside libX11 and my
- libc), the two diverge, but not unreasnobaly so.
+ libc), the two diverge, but not unreasonably so.
text data bss drs rss filename
163431 2152 24 20123 2060 rxvt --enable-everything
This requires XFT support, and the support of your X-server. If that
doesn't work for you, blame Xorg and Keith Packard. ARGB visuals aren't
there yet, no matter what they claim. Rxvt-Unicode contains the
- neccessary bugfixes and workarounds for Xft and Xlib to make it work,
- but that doesn't mean that your WM has the required kludges in place.
+ necessary bugfixes and workarounds for Xft and Xlib to make it work, but
+ that doesn't mean that your WM has the required kludges in place.
4. Use xcompmgr and let it do the job:
way is to ask for the character bounding box, which unfortunately is
wrong in these cases).
- It's not clear (to me at least), wether this is a bug in Xft, freetype,
+ It's not clear (to me at least), whether this is a bug in Xft, freetype,
or the respective font. If you encounter this problem you might try
using the "-lsp" option to give the font more height. If that doesn't
work, you might be forced to use a different font.
but when running a program that doesn't parse cursor movements or in
some cases during rlogin sessions, it fails to detect this properly.
- You can permamently switch this feature off by disabling the "readline"
+ You can permanently switch this feature off by disabling the "readline"
extension:
URxvt.perl-ext-common: default,-readline
My numerical keypad acts weird and generates differing output?
Some Debian GNUL/Linux users seem to have this problem, although no
specific details were reported so far. It is possible that this is
- caused by the wrong "TERM" setting, although the details of wether and
+ caused by the wrong "TERM" setting, although the details of whether and
how this can happen are unknown, as "TERM=rxvt" should offer a
compatible keymap. See the answer to the previous question, and please
report if that helped.
depressed.
What's with the strange Backspace/Delete key behaviour?
- Assuming that the physical Backspace key corresponds to the BackSpace
+ Assuming that the physical Backspace key corresponds to the Backspace
keysym (not likely for Linux ... see the following question) there are
two standard values that can be used for Backspace: "^H" and "^?".
write.
The selection stuff mainly makes the selection perl-error-message aware
- and tells it to convert pelr error mssages into vi-commands to load the
+ and tells it to convert perl error messages into vi-commands to load the
relevant file and go tot he error line number.
URxvt.scrollstyle: plain
URxvt.secondaryScroll: true
As the documentation says: plain is the preferred scrollbar for the
- author. The "secondaryScroll" confgiures urxvt to scroll in full-screen
- apps, like screen, so lines scorlled out of screen end up in urxvt's
+ author. The "secondaryScroll" configures urxvt to scroll in full-screen
+ apps, like screen, so lines scrolled out of screen end up in urxvt's
scrollback buffer.
URxvt.background: #000000
urxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true
I wrote rxvt-unicode to be able to specify fonts exactly. So don't be
- overwhelmed. A special note: the "9x15bold" mentioend above is actually
+ overwhelmed. A special note: the "9x15bold" mentioned above is actually
the version from XFree-3.3, as XFree-4 replaced it by a totally
different font (different glyphs for ";" and many other harmless
characters), while the second font is actually the "9x15bold" from
XFree4/XOrg. The bold version has less chars than the medium version, so
- I use it for rare characters, too. Whene ditign sources with vim, I use
+ I use it for rare characters, too. When editing sources with vim, I use
italic for comments and other stuff, which looks quite good with
Bitstream Vera anti-aliased.
URxvt.resource: value
If you want to use another form (there are lots of different ways of
- specifying resources), make sure you understand wether and why it works.
- If unsure, use the form above.
+ specifying resources), make sure you understand whether and why it
+ works. If unsure, use the form above.
When I log-in to another system it tells me about missing terminfo data?
The terminal description used by rxvt-unicode is not as widely available
library (Fedora Core's bash is one example) and rely on a termcap entry
for "rxvt-unicode".
- You could use rxvt's termcap entry with resonable results in many cases.
- You can also create a termcap entry by using terminfo's infocmp program
- like this:
+ You could use rxvt's termcap entry with reasonable results in many
+ cases. You can also create a termcap entry by using terminfo's infocmp
+ program like this:
infocmp -C rxvt-unicode
Why does "ls" no longer have coloured output?
The "ls" in the GNU coreutils unfortunately doesn't use terminfo to
- decide wether a terminal has colour, but uses its own configuration
+ decide whether a terminal has colour, but uses its own configuration
file. Needless to say, "rxvt-unicode" is not in its default file (among
with most other terminals supporting colour). Either add:
- Make sure the "XMODIFIERS" environment variable is set correctly when
*starting* rxvt-unicode.
When you want to use e.g. kinput2, it must be set to "@im=kinput2".
- For scim, use "@im=SCIM". Youc an see what input method servers are
+ For scim, use "@im=SCIM". You can see what input method servers are
running with this command:
xprop -root XIM_SERVERS
I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation?
You should build one binary with the default options. configure now
enables most useful options, and the trend goes to making them
- runtime-switchable, too, so there is usually no drawback to enbaling
+ runtime-switchable, too, so there is usually no drawback to enabling
them, except higher disk and possibly memory usage. The perl interpreter
should be enabled, as important functionality (menus, selection, likely
more in the future) depends on it.
I am on FreeBSD and rxvt-unicode does not seem to work at all.
Rxvt-unicode requires the symbol "__STDC_ISO_10646__" to be defined in
your compile environment, or an implementation that implements it,
- wether it defines the symbol or not. "__STDC_ISO_10646__" requires that
+ whether it defines the symbol or not. "__STDC_ISO_10646__" requires that
wchar_t is represented as unicode.
- As you might have guessed, FreeBSD does neither define this symobl nor
+ As you might have guessed, FreeBSD does neither define this symbol nor
does it support it. Instead, it uses its own internal representation of
wchar_t. This is, of course, completely fine with respect to standards.
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"
<p>All options that are valid for <strong>rxvt</strong> are valid for
<strong>rxvtc</strong>, too. Please note that options are interpreted in the
context of the daemon process. However, as current working directory,
-process environment and any file handles (e.g. for <code>-pty-fd</code>) are
+process environment and any file descriptor (e.g. for <code>-pty-fd</code>) are
preserved, this rarely makes a difference.</p>
<p>
</p>
.\" ========================================================================
.\"
.IX Title "@@RXVT_NAME@@ 1"
-.TH @@RXVT_NAME@@ 1 "2006-07-22" "7.8" "RXVT-UNICODE"
+.TH @@RXVT_NAME@@ 1 "2006-08-07" "7.9" "RXVT-UNICODE"
.SH "NAME"
@@RXVT_NAME@@c \- control the @@RXVT_NAME@@d daemon
.SH "SYNOPSIS"
All options that are valid for \fB@@RXVT_NAME@@\fR are valid for
\&\fB@@RXVT_NAME@@c\fR, too. Please note that options are interpreted in the
context of the daemon process. However, as current working directory,
-process environment and any file handles (e.g. for \f(CW\*(C`\-pty\-fd\*(C'\fR) are
+process environment and any file descriptor (e.g. for \f(CW\*(C`\-pty\-fd\*(C'\fR) are
preserved, this rarely makes a difference.
.SH "EXIT STATUS"
.IX Header "EXIT STATUS"
All options that are valid for rxvt are valid for rxvtc, too. Please
note that options are interpreted in the context of the daemon process.
However, as current working directory, process environment and any file
- handles (e.g. for "-pty-fd") are preserved, this rarely makes a
+ descriptor (e.g. for "-pty-fd") are preserved, this rarely makes a
difference.
EXIT STATUS
</p>
<hr />
<h1><a name="description">DESCRIPTION</a></h1>
-<p>Everytime a terminal object gets created, extension scripts specified via
+<p>Every time a terminal object gets created, extension scripts specified via
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>
<dd>
<p>The index number (0, 1...) must not have any holes, and each regex must
contain at least one pair of capturing parentheses, which will be used for
-the match. For example, the followign adds a regex that matches everything
+the match. For example, the following adds a regex that matches everything
between two vertical bars:</p>
</dd>
<dd>
</dd>
<dd>
<p>It's sole argument is the popup menu, which can be modified. The selection
-is in <code>$_</code>, which can be used to decide wether to add something or not.
+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
when the button gets activated and should transform <code>$_</code>.</p>
<dd>
<p>This transforms the terminal into a tabbar with additional terminals, that
-is, it implements what is commonly refered to as ``tabbed terminal''. The topmost line
+is, it implements what is commonly referred to as ``tabbed terminal''. The topmost line
displays a ``[NEW]'' button, which, when clicked, will add a new tab, followed by one
button per tab.</p>
</dd>
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
+<p>The accelerator key is grabbed regardless of any modifiers, so this
extension will actually grab a physical key just for this function.</p>
</dd>
<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. Exmaple:</p>
+supported in this mode. Example:</p>
</dd>
<dd>
<pre>
<h2><a name="hooks">Hooks</a></h2>
<p>The following subroutines can be declared in extension files, and will be
called whenever the relevant event happens.</p>
-<p>The first argument passed to them is an extension oject as described in
+<p>The first argument passed to them is an extension object as described in
the in the <code>Extension Objects</code> section.</p>
<p><strong>All</strong> of these hooks must return a boolean value. If any of the called
hooks returns true, then the event counts as being <em>consumed</em>, and the
<dd>
<p>Called at the very end of initialisation of a new terminal, just before
-trying to map (display) the toplevel and returning to the mainloop.</p>
+trying to map (display) the toplevel and returning to the main loop.</p>
</dd>
</li>
<dt><strong><a name="item_on_destroy__24term">on_destroy $term</a></strong>
by calling <a href="#item_selection"><code>$term->selection</code></a>.</p>
</dd>
<dd>
-<p>Returning a true value aborts selection grabbing. It will still be hilighted.</p>
+<p>Returning a true value aborts selection grabbing. It will still be highlighted.</p>
</dd>
</li>
<dt><strong><a name="item_on_sel_extend__24term">on_sel_extend $term</a></strong>
<dd>
<p>Called whenever the user tries to extend the selection (e.g. with a double
click) and is either supposed to return false (normal operation), or
-should extend the selection itelf and return true to suppress the built-in
+should extend the selection itself and return true to suppress the built-in
processing. This can happen multiple times, as long as the callback
returns true, it will be called on every further click by the user and is
supposed to enlarge the selection more and more, if possible.</p>
<dt><strong><a name="item_on_view_change__24term_2c__24offset">on_view_change $term, $offset</a></strong>
<dd>
-<p>Called whenever the view offset changes, i..e the user or program
+<p>Called whenever the view offset changes, i.e. the user or program
scrolls. Offset <code>0</code> means display the normal terminal, positive values
show this many lines of scrollback.</p>
</dd>
</dd>
<dd>
<p>Be careful not ever to trust (in a security sense) the data you receive,
-as its source can not easily be controleld (e-mail content, messages from
+as its source can not easily be controlled (e-mail content, messages from
other users on the same system etc.).</p>
</dd>
</li>
<dt><strong><a name="item_on_user_command__24term_2c__24string">on_user_command $term, $string</a></strong>
<dd>
-<p>Called whenever the a user-configured event is being activated (e.g. via
+<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 <code>rxvt(1)</code> manpage).</p>
</dd>
<dt><strong><a name="item_on_resize_all_windows__24tern_2c__24new_width_2c__">on_resize_all_windows $tern, $new_width, $new_height</a></strong>
<dd>
-<p>Called just after the new window size has been calculcated, but before
+<p>Called just after the new window size has been calculated, but before
windows are actually being resized or hints are being set. If this hook
returns TRUE, setting of the window hints is being skipped.</p>
</dd>
<dt><strong><a name="item_on_focus_out__24term">on_focus_out $term</a></strong>
<dd>
-<p>Called wheneever the window loses keyboard focus, before rxvt-unicode does
+<p>Called whenever the window loses keyboard focus, before rxvt-unicode does
focus out processing.</p>
</dd>
</li>
<dt><strong><a name="item__urxvt__term_init">@urxvt::TERM_INIT</a></strong>
<dd>
-<p>All coderefs in this array will be called as methods of the next newly
+<p>All code references in this array will be called as methods of the next newly
created <code>urxvt::term</code> object (during the <code>on_init</code> phase). The array
-gets cleared before the codereferences that were in it are being executed,
-so coderefs can push themselves onto it again if they so desire.</p>
+gets cleared before the code references that were in it are being executed,
+so references can push themselves onto it again if they so desire.</p>
</dd>
<dd>
-<p>This complements to the perl-eval commandline option, but gets executed
+<p>This complements to the perl-eval command line option, but gets executed
first.</p>
</dd>
</li>
<dd>
<p>Returns all urxvt::term objects that exist in this process, regardless of
-wether they are started, being destroyed etc., so be careful. Only term
+whether they are started, being destroyed etc., so be careful. Only term
objects that have perl extensions attached will be returned (because there
is no urxvt::term objet associated with others).</p>
</dd>
<code>%urxvt::OPTION</code>. Options not enabled in this binary are not in the hash.</p>
</dd>
<dd>
-<p>Here is a a likely non-exhaustive list of option names, please see the
+<p>Here is a likely non-exhaustive list of option names, please see the
source file <em>/src/optinc.h</em> to see the actual list:</p>
</dd>
<dd>
terminal is destroyed, so changing options frequently will eat memory.</p>
</dd>
<dd>
-<p>Here is a a likely non-exhaustive list of resource names, not all of which
+<p>Here is a likely non-exhaustive list of resource names, not all of which
are supported in every build, please see the source file <em>/src/rsinc.h</em>
to see the actual list:</p>
</dd>
<dt><strong><a name="item_hidden_cursor">$cursor_is_hidden = $term->hidden_cursor</a></strong>
<dd>
-<p>Returns wether the cursor is currently hidden or not.</p>
+<p>Returns whether the cursor is currently hidden or not.</p>
</dd>
</li>
<dt><strong><a name="item_view_start">$view_start = $term->view_start ([$newvalue])</a></strong>
<dt><strong><a name="item_special_decode">$string = $term->special_decode $text</a></strong>
<dd>
-<p>Converts rxvt-unicodes text reprsentation into a perl string. See
+<p>Converts rxvt-unicodes text representation into a perl string. See
<a href="#item_row_t"><code>$term->ROW_t</code></a> for details.</p>
</dd>
</li>
<dd>
<p>Calls XGrabPointer and XGrabKeyboard in asynchronous (default) or
-synchronous (<code>$sync</code> is true). Also remembers the grab timestampe.</p>
+synchronous (<code>$sync</code> is true). Also remembers the grab timestamp.</p>
</dd>
</li>
<dt><strong><a name="item_allow_events_async">$term->allow_events_async</a></strong>
<dt><strong><a name="item_fd">$iow = $iow->fd ($fd)</a></strong>
<dd>
-<p>Set the filedescriptor (not handle) to watch.</p>
+<p>Set the file descriptor (not handle) to watch.</p>
</dd>
</li>
<dt><strong><a name="item_events">$iow = $iow->events ($eventmask)</a></strong>
<dt><strong>$iow = $iow->stop</strong>
<dd>
-<p>Stop watching for events on the given filehandle.</p>
+<p>Stop watching for events on the given file handle.</p>
</dd>
</li>
</dl>
<dt><strong>$pw = $timer->start ($pid)</strong>
<dd>
-<p>Tells the wqtcher to start watching for process <code>$pid</code>.</p>
+<p>Tells the watcher to start watching for process <code>$pid</code>.</p>
</dd>
</li>
<dt><strong>$pw = $pw->stop</strong>
<dt><strong><a name="item__3e_3d10__2d_all_called_hooks">>=10 - all called hooks</a></strong>
-<dt><strong><a name="item__3e_3d11__2d_hook_reutrn_values">>=11 - hook reutrn values</a></strong>
+<dt><strong><a name="item__3e_3d11__2d_hook_return_values">>=11 - hook return values</a></strong>
</dl>
<p>
.\" ========================================================================
.\"
.IX Title "@@RXVT_NAME@@ 3"
-.TH @@RXVT_NAME@@ 3 "2006-07-17" "7.8" "RXVT-UNICODE"
+.TH @@RXVT_NAME@@ 3 "2006-08-07" "7.9" "RXVT-UNICODE"
.SH "NAME"
@@RXVT_NAME@@perl \- rxvt\-unicode's embedded perl interpreter
.SH "SYNOPSIS"
.Ve
.SH "DESCRIPTION"
.IX Header "DESCRIPTION"
-Everytime a terminal object gets created, extension scripts specified via
+Every time a terminal object gets created, extension scripts specified via
the \f(CW\*(C`perl\*(C'\fR resource are loaded and associated with it.
.PP
Scripts are compiled in a 'use strict' and 'use utf8' environment, and
.Sp
The index number (0, 1...) must not have any holes, and each regex must
contain at least one pair of capturing parentheses, which will be used for
-the match. For example, the followign adds a regex that matches everything
+the match. For example, the following adds a regex that matches everything
between two vertical bars:
.Sp
.Vb 1
popup is being displayed.
.Sp
It's sole argument is the popup menu, which can be modified. The selection
-is in \f(CW$_\fR, which can be used to decide wether to add something or not.
+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
when the button gets activated and should transform \f(CW$_\fR.
.IP "tabbed" 4
.IX Item "tabbed"
This transforms the terminal into a tabbar with additional terminals, that
-is, it implements what is commonly refered to as \*(L"tabbed terminal\*(R". The topmost line
+is, it implements what is commonly referred to as \*(L"tabbed terminal\*(R". The topmost line
displays a \*(L"[\s-1NEW\s0]\*(R" button, which, when clicked, will add a new tab, followed by one
button per tab.
.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
+The accelerator key is grabbed regardless of any modifiers, 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
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. Exmaple:
+supported in this mode. Example:
.Sp
.Vb 1
\& @@RXVT_NAME@@ \-pixmap background.xpm \-pe automove\-background
The following subroutines can be declared in extension files, and will be
called whenever the relevant event happens.
.PP
-The first argument passed to them is an extension oject as described in
+The first argument passed to them is an extension object as described in
the in the \f(CW\*(C`Extension Objects\*(C'\fR section.
.PP
\&\fBAll\fR of these hooks must return a boolean value. If any of the called
.el .IP "on_start \f(CW$term\fR" 4
.IX Item "on_start $term"
Called at the very end of initialisation of a new terminal, just before
-trying to map (display) the toplevel and returning to the mainloop.
+trying to map (display) the toplevel and returning to the main loop.
.ie n .IP "on_destroy $term" 4
.el .IP "on_destroy \f(CW$term\fR" 4
.IX Item "on_destroy $term"
requested from the server. The selection text can be queried and changed
by calling \f(CW\*(C`$term\->selection\*(C'\fR.
.Sp
-Returning a true value aborts selection grabbing. It will still be hilighted.
+Returning a true value aborts selection grabbing. It will still be highlighted.
.ie n .IP "on_sel_extend $term" 4
.el .IP "on_sel_extend \f(CW$term\fR" 4
.IX Item "on_sel_extend $term"
Called whenever the user tries to extend the selection (e.g. with a double
click) and is either supposed to return false (normal operation), or
-should extend the selection itelf and return true to suppress the built-in
+should extend the selection itself and return true to suppress the built-in
processing. This can happen multiple times, as long as the callback
returns true, it will be called on every further click by the user and is
supposed to enlarge the selection more and more, if possible.
.ie n .IP "on_view_change $term\fR, \f(CW$offset" 4
.el .IP "on_view_change \f(CW$term\fR, \f(CW$offset\fR" 4
.IX Item "on_view_change $term, $offset"
-Called whenever the view offset changes, i..e the user or program
+Called whenever the view offset changes, i.e. the user or program
scrolls. Offset \f(CW0\fR means display the normal terminal, positive values
show this many lines of scrollback.
.ie n .IP "on_scroll_back $term\fR, \f(CW$lines\fR, \f(CW$saved" 4
future.
.Sp
Be careful not ever to trust (in a security sense) the data you receive,
-as its source can not easily be controleld (e\-mail content, messages from
+as its source can not easily be controlled (e\-mail content, messages from
other users on the same system etc.).
.ie n .IP "on_add_lines $term\fR, \f(CW$string" 4
.el .IP "on_add_lines \f(CW$term\fR, \f(CW$string\fR" 4
.ie n .IP "on_user_command $term\fR, \f(CW$string" 4
.el .IP "on_user_command \f(CW$term\fR, \f(CW$string\fR" 4
.IX Item "on_user_command $term, $string"
-Called whenever the a user-configured event is being activated (e.g. via
+Called whenever a user-configured event is being activated (e.g. via
a \f(CW\*(C`perl:string\*(C'\fR action bound to a key, see description of the \fBkeysym\fR
resource in the @@RXVT_NAME@@(1) manpage).
.Sp
.ie n .IP "on_resize_all_windows $tern\fR, \f(CW$new_width\fR, \f(CW$new_height" 4
.el .IP "on_resize_all_windows \f(CW$tern\fR, \f(CW$new_width\fR, \f(CW$new_height\fR" 4
.IX Item "on_resize_all_windows $tern, $new_width, $new_height"
-Called just after the new window size has been calculcated, but before
+Called just after the new window size has been calculated, but before
windows are actually being resized or hints are being set. If this hook
returns \s-1TRUE\s0, setting of the window hints is being skipped.
.ie n .IP "on_x_event $term\fR, \f(CW$event" 4
.ie n .IP "on_focus_out $term" 4
.el .IP "on_focus_out \f(CW$term\fR" 4
.IX Item "on_focus_out $term"
-Called wheneever the window loses keyboard focus, before rxvt-unicode does
+Called whenever the window loses keyboard focus, before rxvt-unicode does
focus out processing.
.ie n .IP "on_configure_notify $term\fR, \f(CW$event" 4
.el .IP "on_configure_notify \f(CW$term\fR, \f(CW$event\fR" 4
.ie n .IP "@urxvt::TERM_INIT" 4
.el .IP "\f(CW@urxvt::TERM_INIT\fR" 4
.IX Item "@urxvt::TERM_INIT"
-All coderefs in this array will be called as methods of the next newly
+All code references in this array will be called as methods of the next newly
created \f(CW\*(C`urxvt::term\*(C'\fR object (during the \f(CW\*(C`on_init\*(C'\fR phase). The array
-gets cleared before the codereferences that were in it are being executed,
-so coderefs can push themselves onto it again if they so desire.
+gets cleared before the code references that were in it are being executed,
+so references can push themselves onto it again if they so desire.
.Sp
-This complements to the perl-eval commandline option, but gets executed
+This complements to the perl-eval command line option, but gets executed
first.
.ie n .IP "@urxvt::TERM_EXT" 4
.el .IP "\f(CW@urxvt::TERM_EXT\fR" 4
.el .IP "\f(CW@terms\fR = urxvt::termlist" 4
.IX Item "@terms = urxvt::termlist"
Returns all urxvt::term objects that exist in this process, regardless of
-wether they are started, being destroyed etc., so be careful. Only term
+whether they are started, being destroyed etc., so be careful. Only term
objects that have perl extensions attached will be returned (because there
is no urxvt::term objet associated with others).
.ie n .IP "$time = urxvt::NOW" 4
optionally change it. All option values are stored by name in the hash
\&\f(CW%urxvt::OPTION\fR. Options not enabled in this binary are not in the hash.
.Sp
-Here is a a likely non-exhaustive list of option names, please see the
+Here is a likely non-exhaustive list of option names, please see the
source file \fI/src/optinc.h\fR to see the actual list:
.Sp
.Vb 6
Please note that resource strings will currently only be freed when the
terminal is destroyed, so changing options frequently will eat memory.
.Sp
-Here is a a likely non-exhaustive list of resource names, not all of which
+Here is a likely non-exhaustive list of resource names, not all of which
are supported in every build, please see the source file \fI/src/rsinc.h\fR
to see the actual list:
.Sp
.ie n .IP "$cursor_is_hidden\fR = \f(CW$term\->hidden_cursor" 4
.el .IP "\f(CW$cursor_is_hidden\fR = \f(CW$term\fR\->hidden_cursor" 4
.IX Item "$cursor_is_hidden = $term->hidden_cursor"
-Returns wether the cursor is currently hidden or not.
+Returns whether the cursor is currently hidden or not.
.ie n .IP "$view_start\fR = \f(CW$term\->view_start ([$newvalue])" 4
.el .IP "\f(CW$view_start\fR = \f(CW$term\fR\->view_start ([$newvalue])" 4
.IX Item "$view_start = $term->view_start ([$newvalue])"
.ie n .IP "$string\fR = \f(CW$term\fR\->special_decode \f(CW$text" 4
.el .IP "\f(CW$string\fR = \f(CW$term\fR\->special_decode \f(CW$text\fR" 4
.IX Item "$string = $term->special_decode $text"
-Converts rxvt-unicodes text reprsentation into a perl string. See
+Converts rxvt-unicodes text representation into a perl string. See
\&\f(CW\*(C`$term\->ROW_t\*(C'\fR for details.
.ie n .IP "$success\fR = \f(CW$term\fR\->grab_button ($button, \f(CW$modifiermask\fR[, \f(CW$window\fR = \f(CW$term\->vt])" 4
.el .IP "\f(CW$success\fR = \f(CW$term\fR\->grab_button ($button, \f(CW$modifiermask\fR[, \f(CW$window\fR = \f(CW$term\fR\->vt])" 4
.el .IP "\f(CW$success\fR = \f(CW$term\fR\->grab ($eventtime[, \f(CW$sync\fR])" 4
.IX Item "$success = $term->grab ($eventtime[, $sync])"
Calls XGrabPointer and XGrabKeyboard in asynchronous (default) or
-synchronous (\f(CW$sync\fR is true). Also remembers the grab timestampe.
+synchronous (\f(CW$sync\fR is true). Also remembers the grab timestamp.
.ie n .IP "$term\->allow_events_async" 4
.el .IP "\f(CW$term\fR\->allow_events_async" 4
.IX Item "$term->allow_events_async"
.ie n .IP "$iow\fR = \f(CW$iow\->fd ($fd)" 4
.el .IP "\f(CW$iow\fR = \f(CW$iow\fR\->fd ($fd)" 4
.IX Item "$iow = $iow->fd ($fd)"
-Set the filedescriptor (not handle) to watch.
+Set the file descriptor (not handle) to watch.
.ie n .IP "$iow\fR = \f(CW$iow\->events ($eventmask)" 4
.el .IP "\f(CW$iow\fR = \f(CW$iow\fR\->events ($eventmask)" 4
.IX Item "$iow = $iow->events ($eventmask)"
.ie n .IP "$iow\fR = \f(CW$iow\->stop" 4
.el .IP "\f(CW$iow\fR = \f(CW$iow\fR\->stop" 4
.IX Item "$iow = $iow->stop"
-Stop watching for events on the given filehandle.
+Stop watching for events on the given file handle.
.ie n .Sh "The ""urxvt::iw"" Class"
.el .Sh "The \f(CWurxvt::iw\fP Class"
.IX Subsection "The urxvt::iw Class"
.ie n .IP "$pw\fR = \f(CW$timer\->start ($pid)" 4
.el .IP "\f(CW$pw\fR = \f(CW$timer\fR\->start ($pid)" 4
.IX Item "$pw = $timer->start ($pid)"
-Tells the wqtcher to start watching for process \f(CW$pid\fR.
+Tells the watcher to start watching for process \f(CW$pid\fR.
.ie n .IP "$pw\fR = \f(CW$pw\->stop" 4
.el .IP "\f(CW$pw\fR = \f(CW$pw\fR\->stop" 4
.IX Item "$pw = $pw->stop"
.IX Item ">= 3 - script loading and management"
.IP ">=10 \- all called hooks" 4
.IX Item ">=10 - all called hooks"
-.IP ">=11 \- hook reutrn values" 4
-.IX Item ">=11 - hook reutrn values"
+.IP ">=11 \- hook return values" 4
+.IX Item ">=11 - hook return values"
.PD
.SH "AUTHOR"
.IX Header "AUTHOR"
rxvt --perl-lib $HOME -pe grab_test
DESCRIPTION
- Everytime a terminal object gets created, extension scripts specified
+ Every time a terminal object gets created, extension scripts specified
via the "perl" resource are loaded and associated with it.
Scripts are compiled in a 'use strict' and 'use utf8' environment, and
The index number (0, 1...) must not have any holes, and each regex
must contain at least one pair of capturing parentheses, which will
- be used for the match. For example, the followign adds a regex that
+ be used for the match. For example, the following adds a regex that
matches everything between two vertical bars:
URxvt.selection.pattern-0: \\|([^|]+)\\|
called whenever the popup is being displayed.
It's sole argument is the popup menu, which can be modified. The
- selection is in $_, which can be used to decide wether to add
+ 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
reference will be called when the button gets activated and should
tabbed
This transforms the terminal into a tabbar with additional
- terminals, that is, it implements what is commonly refered to as
+ terminals, that is, it implements what is commonly referred to as
"tabbed terminal". The topmost line displays a "[NEW]" button,
which, when clicked, will add a new tab, followed by one button per
tab.
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
+ The accelerator key is grabbed regardless of any modifiers, 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
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. Exmaple:
+ pixmap. No scaling is supported in this mode. Example:
rxvt -pixmap background.xpm -pe automove-background
The following subroutines can be declared in extension files, and will
be called whenever the relevant event happens.
- The first argument passed to them is an extension oject as described in
+ The first argument passed to them is an extension object as described in
the in the "Extension Objects" section.
All of these hooks must return a boolean value. If any of the called
on_start $term
Called at the very end of initialisation of a new terminal, just
before trying to map (display) the toplevel and returning to the
- mainloop.
+ main loop.
on_destroy $term
Called whenever something tries to destroy terminal, when the
queried and changed by calling "$term->selection".
Returning a true value aborts selection grabbing. It will still be
- hilighted.
+ highlighted.
on_sel_extend $term
Called whenever the user tries to extend the selection (e.g. with a
double click) and is either supposed to return false (normal
- operation), or should extend the selection itelf and return true to
+ operation), or should extend the selection itself and return true to
suppress the built-in processing. This can happen multiple times, as
long as the callback returns true, it will be called on every
further click by the user and is supposed to enlarge the selection
See the selection example extension.
on_view_change $term, $offset
- Called whenever the view offset changes, i..e the user or program
+ Called whenever the view offset changes, i.e. the user or program
scrolls. Offset 0 means display the normal terminal, positive values
show this many lines of scrollback.
and this might be enforced in the future.
Be careful not ever to trust (in a security sense) the data you
- receive, as its source can not easily be controleld (e-mail content,
+ receive, as its source can not easily be controlled (e-mail content,
messages from other users on the same system etc.).
on_add_lines $term, $string
Called just after the screen gets redrawn. See "on_refresh_begin".
on_user_command $term, $string
- Called whenever the 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 rxvt(1) manpage).
+ 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 rxvt(1) manpage).
The event is simply the action string. This interface is assumed to
change slightly in the future.
on_resize_all_windows $tern, $new_width, $new_height
- Called just after the new window size has been calculcated, but
+ Called just after the new window size has been calculated, but
before windows are actually being resized or hints are being set. If
this hook returns TRUE, setting of the window hints is being
skipped.
rxvt-unicode does focus in processing.
on_focus_out $term
- Called wheneever the window loses keyboard focus, before
- rxvt-unicode does focus out processing.
+ Called whenever the window loses keyboard focus, before rxvt-unicode
+ does focus out processing.
on_configure_notify $term, $event
on_property_notify $term, $event
object, whenever a callback/hook is executing.
@urxvt::TERM_INIT
- All coderefs in this array will be called as methods of the next
- newly created "urxvt::term" object (during the "on_init" phase). The
- array gets cleared before the codereferences that were in it are
- being executed, so coderefs can push themselves onto it again if
- they so desire.
+ All code references in this array will be called as methods of the
+ next newly created "urxvt::term" object (during the "on_init"
+ phase). The array gets cleared before the code references that were
+ in it are being executed, so references can push themselves onto it
+ again if they so desire.
- This complements to the perl-eval commandline option, but gets
+ This complements to the perl-eval command line option, but gets
executed first.
@urxvt::TERM_EXT
@terms = urxvt::termlist
Returns all urxvt::term objects that exist in this process,
- regardless of wether they are started, being destroyed etc., so be
+ regardless of whether they are started, being destroyed etc., so be
careful. Only term objects that have perl extensions attached will
be returned (because there is no urxvt::term objet associated with
others).
hash %urxvt::OPTION. Options not enabled in this binary are not in
the hash.
- Here is a a likely non-exhaustive list of option names, please see
- the source file /src/optinc.h to see the actual list:
+ Here is a likely non-exhaustive list of option names, please see the
+ source file /src/optinc.h to see the actual list:
borderLess console cursorBlink cursorUnderline hold iconic insecure
intensityStyles jumpScroll loginShell mapAlert meta8 mouseWheelScrollPage
the terminal is destroyed, so changing options frequently will eat
memory.
- Here is a a likely non-exhaustive list of resource names, not all of
+ Here is a likely non-exhaustive list of resource names, not all of
which are supported in every build, please see the source file
/src/rsinc.h to see the actual list:
Returns the currently displayed screen (0 primary, 1 secondary).
$cursor_is_hidden = $term->hidden_cursor
- Returns wether the cursor is currently hidden or not.
+ Returns whether the cursor is currently hidden or not.
$view_start = $term->view_start ([$newvalue])
Returns the row number of the topmost displayed line. Maximum value
See "$term->ROW_t" for details.
$string = $term->special_decode $text
- Converts rxvt-unicodes text reprsentation into a perl string. See
+ Converts rxvt-unicodes text representation into a perl string. See
"$term->ROW_t" for details.
$success = $term->grab_button ($button, $modifiermask[, $window =
$success = $term->grab ($eventtime[, $sync])
Calls XGrabPointer and XGrabKeyboard in asynchronous (default) or
- synchronous ($sync is true). Also remembers the grab timestampe.
+ synchronous ($sync is true). Also remembers the grab timestamp.
$term->allow_events_async
Calls XAllowEvents with AsyncBoth for the most recent grab.
$reventmask is a bitset as described in the "events" method.
$iow = $iow->fd ($fd)
- Set the filedescriptor (not handle) to watch.
+ Set the file descriptor (not handle) to watch.
$iow = $iow->events ($eventmask)
Set the event mask to watch. The only allowed values are
Start watching for requested events on the given handle.
$iow = $iow->stop
- Stop watching for events on the given filehandle.
+ Stop watching for events on the given file handle.
The "urxvt::iw" Class
This class implements idle watchers, that get called automatically when
Set the callback to be called when the timer triggers.
$pw = $timer->start ($pid)
- Tells the wqtcher to start watching for process $pid.
+ Tells the watcher to start watching for process $pid.
$pw = $pw->stop
Stop the watcher.
== 0 - fatal messages
>= 3 - script loading and management
>=10 - all called hooks
- >=11 - hook reutrn values
+ >=11 - hook return values
AUTHOR
Marc Lehmann <pcg@goof.com>
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.8"
-#define DATE "2006-07-17"
+#define VERSION "7.9"
+#define DATE "2006-08-07"
projects / dana / urxvt.git / commitdiff