From cafe881a18ac5d0ad050cbe2cdf35a16e1ff5900 Mon Sep 17 00:00:00 2001 From: root Date: Mon, 7 Aug 2006 16:17:30 +0000 Subject: [PATCH] *** empty log message *** --- Changes | 7 +- README.FAQ | 46 +++++------ README.configure | 4 +- doc/rxvt.1.html | 165 ++++++++++++++++++------------------- doc/rxvt.1.man.in | 31 +++---- doc/rxvt.1.txt | 186 +++++++++++++++++++++--------------------- doc/rxvt.7.html | 44 +++++----- doc/rxvt.7.man.in | 42 +++++----- doc/rxvt.7.txt | 50 ++++++------ doc/rxvtc.1.html | 2 +- doc/rxvtc.1.man.in | 4 +- doc/rxvtc.1.txt | 2 +- doc/rxvtperl.3.html | 58 ++++++------- doc/rxvtperl.3.man.in | 62 +++++++------- doc/rxvtperl.3.txt | 70 ++++++++-------- src/Makefile.in | 99 ++++++++++++++++++++++ src/version.h | 4 +- 17 files changed, 489 insertions(+), 387 deletions(-) diff --git a/Changes b/Changes index a59ce17f..672cebfc 100644 --- a/Changes +++ b/Changes @@ -21,12 +21,13 @@ WISH: http://www120.pair.com/mccarthy/nextstep/intro.htmld/Workspace.html is the 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, diff --git a/README.FAQ b/README.FAQ index f0a6bdf3..b0e75e9a 100644 --- a/README.FAQ +++ b/README.FAQ @@ -60,7 +60,7 @@ RXVT-UNICODE/URXVT FREQUENTLY ASKED QUESTIONS 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 @@ -110,7 +110,7 @@ RXVT-UNICODE/URXVT FREQUENTLY ASKED QUESTIONS 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 @@ -204,8 +204,8 @@ RXVT-UNICODE/URXVT FREQUENTLY ASKED QUESTIONS 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: @@ -230,7 +230,7 @@ RXVT-UNICODE/URXVT FREQUENTLY ASKED QUESTIONS 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. @@ -459,7 +459,7 @@ RXVT-UNICODE/URXVT FREQUENTLY ASKED QUESTIONS 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 @@ -467,7 +467,7 @@ RXVT-UNICODE/URXVT FREQUENTLY ASKED QUESTIONS 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. @@ -498,7 +498,7 @@ RXVT-UNICODE/URXVT FREQUENTLY ASKED QUESTIONS 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 "^?". @@ -630,15 +630,15 @@ RXVT-UNICODE/URXVT FREQUENTLY ASKED QUESTIONS 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 @@ -699,12 +699,12 @@ RXVT-UNICODE/URXVT FREQUENTLY ASKED QUESTIONS 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. @@ -765,8 +765,8 @@ RXVT-UNICODE/URXVT FREQUENTLY ASKED QUESTIONS 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 @@ -809,9 +809,9 @@ RXVT-UNICODE/URXVT FREQUENTLY ASKED QUESTIONS 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 @@ -840,7 +840,7 @@ RXVT-UNICODE/URXVT FREQUENTLY ASKED QUESTIONS 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: @@ -978,7 +978,7 @@ RXVT-UNICODE/URXVT FREQUENTLY ASKED QUESTIONS - 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 @@ -1025,7 +1025,7 @@ RXVT-UNICODE/URXVT FREQUENTLY ASKED QUESTIONS 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. @@ -1067,10 +1067,10 @@ RXVT-UNICODE/URXVT FREQUENTLY ASKED QUESTIONS 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. diff --git a/README.configure b/README.configure index 7e60c429..42601a14 100644 --- a/README.configure +++ b/README.configure @@ -194,7 +194,7 @@ CONFIGURE OPTIONS 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. @@ -235,7 +235,7 @@ CONFIGURE OPTIONS 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" diff --git a/doc/rxvt.1.html b/doc/rxvt.1.html index f21188ed..c00f02fb 100644 --- a/doc/rxvt.1.html +++ b/doc/rxvt.1.html @@ -50,12 +50,12 @@

SYNOPSIS

-

urxvt [options] [-e command [ args ]]

+

rxvt [options] [-e command [ args ]]

DESCRIPTION

-

rxvt-unicode, version 7.8, is a colour vt102 terminal +

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 -- @@ -64,7 +64,7 @@ a significant advantage on a machine serving many X sessions.

FREQUENTLY ASKED QUESTIONS

-

See urxvt(7) (try man 7 urxvt) for a list of +

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.

@@ -79,13 +79,13 @@ especially cursive scripts such as arabic, vertically written scripts like mongolian or scripts requiring extremely complex combining rules, like tibetan or devenagari. Don't expect pretty output when using these scripts. Most other scripts, latin, cyrillic, kanji, thai etc. should work -fine, though. A somewhat difficult case are left-to-right scripts, such +fine, though. A somewhat difficult case are right-to-left scripts, such as hebrew: 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.

@@ -95,34 +95,34 @@ programs force onto its users never made sense to me: You should be able to choose any font for any script freely.

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.

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 urxvtd(1) (daemon) and -urxvtc(1) (client).

+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 +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 +

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 -h' gives a list of major compile-time options 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 +XIM on the 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 +

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 +far greater than those listed. For example: `rxvt --loginShell --color1 Orange'.

The following options are available:

@@ -173,7 +173,8 @@ resource depth.

Please note that transparency of any kind if completely unsupported by -the author. Don't bug him with installation questions!

+the author. Don't bug him with installation questions! Read the FAQ (man 7 +rxvt)!

-fade number @@ -202,7 +203,7 @@ used to brighten or darken the image in addition to tinting it; resource 
-   urxvt -tr -tint blue -sh 40
+ rxvt -tr -tint blue -sh 40
-sh @@ -275,12 +276,12 @@ 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).

+section of rxvt(7).

-fb fontlist @@ -471,7 +472,7 @@ resource termName.

-e command [arguments]
-

Run the command with its command-line arguments in the urxvt +

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 @@ -485,7 +486,7 @@ 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 @@ -580,7 +581,7 @@ info.

-hold|+hold
-

Turn on/off hold window after exit support. If enabled, urxvt +

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.

@@ -595,23 +596,23 @@ user; resource hold.

-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 +

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.

+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 +

It might be useful to know that rxvt will not close file descriptors passed to it (except for stdin/out/err, of course), so you can use file descriptors to communicate with the programs within the -terminal. This works regardless of wether the -embed option was used or +terminal. This works regardless of whether the -embed option was used or not.

@@ -623,20 +624,20 @@ 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 +

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.

@@ -657,7 +658,7 @@ longer example is in doc/pty-fd):

    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;
@@ -679,11 +680,11 @@ 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 +

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, +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
@@ -691,15 +692,15 @@ with later settings overwriting earlier ones:

   3. RESOURCE_MANAGER property on root-window OR $HOME/.Xdefaults
   4. SCREEN_RESOURCES for the current screen
   5. $XENVIRONMENT file OR $HOME/.Xdefaults-<nodename>
-

Note that when reading X resources, urxvt recognizes two class +

Note that when reading X resources, rxvt recognizes two class names: Rxvt and URxvt. The class name Rxvt allows resources -common to both urxvt and the original rxvt to be easily +common to both rxvt and the original rxvt to be easily configured, while the class name URxvt allows resources unique to -urxvt, to be shared between different urxvt +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 urxvtperl(3) manpage for additional settings by perl +check the rxvtperl(3) manpage for additional settings by perl extensions not documented here):

depth: bitdepth @@ -742,7 +743,7 @@ names used are listed in the COLORS AND GRAPHICS section.

Colours higher than 15 cannot be set using resources (yet), but can be -changed using an escape command (see urxvt(7)).

+changed using an escape command (see rxvt(7)).

Colours 16-79 form a standard 4x4x4 colour cube (the same as xterm with @@ -973,7 +974,7 @@ text font will being used for the given style.

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 (False, +intensity foreground/background colours. Disabling this option (False, option +is) disables this behaviour, the high intensity colours are not reachable.

@@ -1058,7 +1059,7 @@ option -ut. False: write record into the syste

This creates a new file in your home directory with the screen contents -everytime you hit Print.

+every time you hit Print.

scrollBar: boolean @@ -1102,7 +1103,7 @@ thumb with the pointer on middle button press/drag.

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.

+with scrollback buffer when tty receives new lines; option +sw.

scrollTtyKeypress: boolean @@ -1245,7 +1246,7 @@ with the Execute key.

When the selection extension is in use (the default if compiled in, see -the urxvtperl(3) manpage), a suitable regex using these characters +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.

@@ -1284,7 +1285,7 @@ another locale; option -imlocale.

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* 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 -imfont.

@@ -1348,7 +1349,7 @@ instead scroll the screen up.

hold: boolean
-

Turn on/off hold window after exit support. If enabled, urxvt +

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.

@@ -1390,12 +1391,12 @@ can start or end with whitespace.

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 `/' +with pattern list/PREFIX/MIDDLE/SUFFIX, where the delimiter `/' should be a character not used by the strings.

@@ -1416,7 +1417,7 @@ should be a character not used by the strings.

If string takes the form of command:STRING, the specified STRING -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 zh_CN.GBK when Control-Meta-c is being pressed'':

@@ -1426,9 +1427,9 @@ 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) +is passed to the on_keyboard_command perl handler. See the rxvtperl(3) manpage. For example, the selection extension (activated via -urxvt -pe selection) listens for selection:rot13 events:

+rxvt -pe selection) listens for selection:rot13 events:

@@ -1444,7 +1445,7 @@ 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:

@@ -1469,7 +1470,7 @@ font-switching at runtime:

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):

@@ -1496,7 +1497,7 @@ example, default,-selection will use all the default extension exce

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 extension +searchable scrollback to Alt/Meta-s). Mentioning the same extension multiple times with different arguments will pass multiple arguments to the extension.

@@ -1515,7 +1516,7 @@ all instances, while perl-ext is used for specific instances.

Perl code to be evaluated when all extensions have been registered. See -the urxvtperl(3) manpage. Due to security reasons, this resource +the rxvtperl(3) manpage. Due to security reasons, this resource will be ignored when running setuid/setgid.

@@ -1524,25 +1525,25 @@ will be ignored when running setuid/setgid.

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 +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 +

Selection auto-transform patterns, see the rxvtperl(3) manpage for details.

@@ -1578,9 +1579,9 @@ it almost invisible to window managers; option -override-redirect

THE SCROLLBAR

-

Lines of text that scroll off the top of the urxvt window +

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 +or by 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

Scroll down with Button1 (xterm-scrollbar) or Shift-Next. @@ -1626,7 +1627,7 @@ the selection.

Insertion:
-

Pressing and releasing the Middle mouse button in an urxvt +

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.

@@ -1712,16 +1713,16 @@ 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 +

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 +allow this 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 display up to 16 colours (8 ANSI colours plus +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.

@@ -1747,7 +1748,7 @@ colours with their names.

background, cursorColor, cursorColor2, colorBD, colorUL as a number 0-15, as a convenient shorthand to reference the colour name of color0-color15.

-

In addition to the colours defined above, urxvt offers an +

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).

@@ -1759,7 +1760,7 @@ always swapping the foreground/background colours. This is in contrast to 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 @@ -1783,26 +1784,26 @@ ARGB visuals out of the box, and rxvt-unicode just fudges around.

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.

+resources or on the command line.

COLORTERM
-

Either rxvt, rxvt-xpm, depending on wether urxvt was +

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.

@@ -1814,7 +1815,7 @@ compiled with XPM support, and optionally with the added extension the colour code used as default foreground/text colour (or the 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 +string default), and xpm is the string default if rxvt was compiled with XPM support. Libraries like ncurses and slang can (and do) use this information to optimize screen output.

@@ -1822,7 +1823,7 @@ was compiled with XPM support. Libraries like ncurses and sla
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).

@@ -1830,14 +1831,14 @@ 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.

@@ -1850,8 +1851,8 @@ display in its child processes.

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 >>>.

@@ -1875,7 +1876,7 @@ daemon communications and to locate various resource files (such as

If set and accessible, gives the name of a X resource file to be loaded by -urxvt.

+rxvt.

@@ -1895,7 +1896,7 @@ urxvt.

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)

diff --git a/doc/rxvt.1.man.in b/doc/rxvt.1.man.in index e47d8026..26205234 100644 --- a/doc/rxvt.1.man.in +++ b/doc/rxvt.1.man.in @@ -129,7 +129,7 @@ .\" ======================================================================== .\" .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" @@ -157,14 +157,14 @@ especially cursive scripts such as arabic, vertically written scripts like mongolian or scripts requiring extremely complex combining rules, like tibetan or devenagari. Don't expect pretty output when using these scripts. Most other scripts, latin, cyrillic, kanji, thai etc. should work -fine, though. A somewhat difficult case are left-to-right scripts, such +fine, though. A somewhat difficult case are right-to-left scripts, such as hebrew: \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. @@ -176,7 +176,7 @@ to choose any font for any script freely. .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 @@ -188,7 +188,7 @@ drastically reduces memory usage. See @@RXVT_NAME@@d(1) (daemon) and @@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" @@ -235,7 +235,8 @@ Turn on/off inheriting parent window's pixmap. Alternative form is \&\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 @@ -508,7 +509,7 @@ The window will not be destroyed when @@RXVT_NAME@@ exits. 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 @@ -524,7 +525,7 @@ used (a longer example is in \fIdoc/embed\fR): .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 @@ -769,7 +770,7 @@ text font will being used for the given style. .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 @@ -824,7 +825,7 @@ Example: .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: @@ -850,7 +851,7 @@ thumb with the pointer on middle button press/drag. .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 @@ -1040,7 +1041,7 @@ Xlib itself does its own de-escaping (you can use \f(CW\*(C`\e033\*(C'\fR instea 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: @@ -1129,7 +1130,7 @@ example, \f(CW\*(C`default,\-selection\*(C'\fR will use all the default extensio .Sp Extension names can also be followed by an argument in angle brackets (e.g. \f(CW\*(C`searchable\-scrollback\*(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 @@ -1389,10 +1390,10 @@ the author. Don't bug him with installation questions!\fR .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 diff --git a/doc/rxvt.1.txt b/doc/rxvt.1.txt index 1f3fe107..cb952fc7 100644 --- a/doc/rxvt.1.txt +++ b/doc/rxvt.1.txt @@ -3,19 +3,19 @@ NAME 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 . RXVT-UNICODE VS. RXVT @@ -26,14 +26,14 @@ 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. @@ -45,7 +45,7 @@ RXVT-UNICODE VS. RXVT 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. @@ -54,27 +54,27 @@ RXVT-UNICODE VS. RXVT without most of its features to get a lean binary. It also comes with a client/daemon pair that lets you open any number of terminal windows from within a single process, which makes startup time very fast and - drastically reduces memory usage. See urxvtd(1) (daemon) and urxvtc(1) + drastically reduces memory usage. See rxvtd(1) (daemon) and rxvtc(1) (client). It also makes technical information about escape sequences (which have - been extended) 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: @@ -104,7 +104,8 @@ OPTIONS -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 @@ -122,7 +123,7 @@ OPTIONS 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 @@ -165,11 +166,11 @@ OPTIONS 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 @@ -283,7 +284,7 @@ OPTIONS 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 @@ -295,7 +296,7 @@ OPTIONS 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 @@ -350,7 +351,7 @@ OPTIONS 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. @@ -359,21 +360,21 @@ OPTIONS 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): @@ -381,16 +382,16 @@ OPTIONS 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. @@ -405,7 +406,7 @@ OPTIONS 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 @@ -417,12 +418,12 @@ OPTIONS 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 @@ -431,15 +432,15 @@ RESOURCES (available also as long-options) 4. SCREEN_RESOURCES for the current screen 5. $XENVIRONMENT file OR $HOME/.Xdefaults- - 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; @@ -467,7 +468,7 @@ RESOURCES (available also as long-options) 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. @@ -624,7 +625,7 @@ RESOURCES (available also as long-options) 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. @@ -677,7 +678,7 @@ RESOURCES (available also as long-options) 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 @@ -702,7 +703,7 @@ RESOURCES (available also as long-options) 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 @@ -789,7 +790,7 @@ RESOURCES (available also as long-options) (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. @@ -815,7 +816,7 @@ RESOURCES (available also as long-options) 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. @@ -857,7 +858,7 @@ RESOURCES (available also as long-options) 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. @@ -891,11 +892,11 @@ RESOURCES (available also as long-options) 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: @@ -909,7 +910,7 @@ RESOURCES (available also as long-options) URxvt.keysym.Meta-Control-0x63: \033 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": @@ -917,9 +918,8 @@ RESOURCES (available also as long-options) 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 @@ -931,7 +931,7 @@ RESOURCES (available also as long-options) 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: @@ -949,7 +949,7 @@ RESOURCES (available also as long-options) 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 @@ -968,7 +968,7 @@ RESOURCES (available also as long-options) Extension names can also be followed by an argument in angle brackets (e.g. "searchable-scrollback", 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. @@ -983,24 +983,24 @@ RESOURCES (available also as long-options) 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* @@ -1021,9 +1021,9 @@ RESOURCES (available also as long-options) -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* @@ -1060,7 +1060,7 @@ TEXT SELECTION AND INSERTION 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. @@ -1148,13 +1148,13 @@ ISO 14755 SUPPORT 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. @@ -1181,7 +1181,7 @@ COLORS AND GRAPHICS 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). @@ -1195,7 +1195,7 @@ COLORS AND GRAPHICS *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. @@ -1216,20 +1216,20 @@ COLORS AND GRAPHICS 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. @@ -1239,27 +1239,27 @@ ENVIRONMENT 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-*Rxvt-unicode uses gobs of memory, how can I reduce that?
  • How can I start urxvtd in a race-free way?
  • How can I start urxvtd automatically when I run URXVT_NAME@@c?
    • -
  • 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.
  • How do I set the correct, full IP address for the DISPLAY variable?
  • How do I compile the manual pages on my own?
  • Isn't rxvt-unicode supposed to be small? Don't all those features bloat?
    • @@ -229,7 +229,7 @@ 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 variable to decide @@ -280,7 +280,7 @@ already in use in this mode.

    188985 9048 66616 18222 1788 urxvt --disable-everything

    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
@@ -363,7 +363,7 @@ are unable to read.
    
    urxvt -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc

    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.

    4. Use xcompmgr and let it do the job:

    @@ -386,7 +386,7 @@ however: Xft fonts often draw glyphs larger than their acclaimed bounding 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).

    -

    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.

    @@ -605,7 +605,7 @@ circumstances, it will move your cursor around when you click into the 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.

    -

    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
    @@ -614,7 +614,7 @@ extension:

    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 how +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.

    @@ -649,7 +649,7 @@ depressed.

    What's with the strange Backspace/Delete key behaviour?

    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: ^H and ^?.

    Historically, either value is correct, but rxvt-unicode adopts the debian @@ -768,14 +768,14 @@ directory and also tells urxvt to use a large number of extensions. I develop for myself mostly, so I actually use most of the extensions I 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
@@ -827,12 +827,12 @@ iconified till people msg me (which beeps).
    
    urxvt.italicFont:       xft:Bitstream Vera Sans Mono:italic:autohint=true
    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 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.

    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) @@ -885,7 +885,7 @@ re-login after every change (or run xrdb -merge $HOME/.Xresources).

       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 +specifying resources), make sure you understand whether and why it works. If unsure, use the form above.

    @@ -926,7 +926,7 @@ the rxvt terminfo file with the rxvt-unicode one and use TERM=rxvt. 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 rxvt-unicode.

    -

    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:

    @@ -957,7 +957,7 @@ like this:
    
 
    
 
    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:
    
 
    @@ -1094,7 +1094,7 @@ rxvt-unicode-locales.
    
 
 
    
 
    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
+@im=kinput2. For scim, use @im=SCIM. You can see what input
 method servers are running with this command:
    
 
    
 
    
@@ -1148,7 +1148,7 @@ might encounter the same issue.
    
 
    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 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.
    
@@ -1189,9 +1189,9 @@ following ugly workaround to get non-double-wide-characters working:
    
 
    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.
    
 
    However, that means rxvt-unicode only works in POSIX, ISO-8859-1 and
@@ -2499,7 +2499,7 @@ in combination with other switches) is:
    
 
    --enable-iso14755 (default: on)
 
 
    
-
    Enable extended ISO 14755 support (see urxvt(1), or
+
    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.
    
@@ -2569,7 +2569,7 @@ the screen in a fixed position.
    
 
    --enable-perl (default: on)
 
 
    
-
    Enable an embedded perl interpreter. See the urxvtperl(3)
+
    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 environment
diff --git a/doc/rxvt.7.man.in b/doc/rxvt.7.man.in
index 8a1e7f89..3306e39b 100644
--- a/doc/rxvt.7.man.in
+++ b/doc/rxvt.7.man.in
@@ -129,7 +129,7 @@
 .\" ========================================================================
 .\"
 .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"
@@ -231,8 +231,8 @@ meaning it couldn't connect to the daemon, it will start the daemon and
 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,
@@ -293,7 +293,7 @@ already in use in this mode.
 .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
@@ -402,7 +402,7 @@ are unable to read.
 .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
@@ -432,7 +432,7 @@ 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).
 .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.
@@ -710,7 +710,7 @@ 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.
 .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
@@ -722,7 +722,7 @@ extension:
 .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.
@@ -762,7 +762,7 @@ depressed.
 .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
@@ -913,7 +913,7 @@ develop for myself mostly, so I actually use most of the extensions I
 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
@@ -922,8 +922,8 @@ relevant file and go tot he error line number.
 .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
@@ -1002,12 +1002,12 @@ I once thought this is a great idea.
 .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
@@ -1075,7 +1075,7 @@ Also consider the form resources have to use:
 .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
@@ -1130,7 +1130,7 @@ 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 \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
@@ -1167,7 +1167,7 @@ Or you could use this termcap entry, generated by the command above:
 .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
@@ -1335,7 +1335,7 @@ For example, \fBkinput2\fR does not support \s-1UTF\-8\s0 locales, you should us
 .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
@@ -1393,7 +1393,7 @@ might encounter the same issue.
 .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.
@@ -1443,10 +1443,10 @@ following ugly workaround to get non-double-wide-characters working:
 .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
diff --git a/doc/rxvt.7.txt b/doc/rxvt.7.txt
index 85d62a68..65d461d7 100644
--- a/doc/rxvt.7.txt
+++ b/doc/rxvt.7.txt
@@ -81,7 +81,7 @@ RXVT-UNICODE/URXVT FREQUENTLY ASKED QUESTIONS
     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
@@ -131,7 +131,7 @@ RXVT-UNICODE/URXVT FREQUENTLY ASKED QUESTIONS
 
     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
@@ -225,8 +225,8 @@ RXVT-UNICODE/URXVT FREQUENTLY ASKED QUESTIONS
     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:
 
@@ -251,7 +251,7 @@ RXVT-UNICODE/URXVT FREQUENTLY ASKED QUESTIONS
     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.
@@ -480,7 +480,7 @@ RXVT-UNICODE/URXVT FREQUENTLY ASKED QUESTIONS
     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
@@ -488,7 +488,7 @@ RXVT-UNICODE/URXVT FREQUENTLY ASKED QUESTIONS
    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.
@@ -519,7 +519,7 @@ RXVT-UNICODE/URXVT FREQUENTLY ASKED QUESTIONS
     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 "^?".
 
@@ -651,15 +651,15 @@ RXVT-UNICODE/URXVT FREQUENTLY ASKED QUESTIONS
     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
@@ -720,12 +720,12 @@ RXVT-UNICODE/URXVT FREQUENTLY ASKED QUESTIONS
        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.
 
@@ -786,8 +786,8 @@ RXVT-UNICODE/URXVT FREQUENTLY ASKED QUESTIONS
       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
@@ -830,9 +830,9 @@ RXVT-UNICODE/URXVT FREQUENTLY ASKED QUESTIONS
     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
 
@@ -861,7 +861,7 @@ RXVT-UNICODE/URXVT FREQUENTLY ASKED QUESTIONS
 
    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:
 
@@ -999,7 +999,7 @@ RXVT-UNICODE/URXVT FREQUENTLY ASKED QUESTIONS
     - 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
@@ -1046,7 +1046,7 @@ RXVT-UNICODE/URXVT FREQUENTLY ASKED QUESTIONS
    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.
@@ -1088,10 +1088,10 @@ RXVT-UNICODE/URXVT FREQUENTLY ASKED QUESTIONS
    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.
 
@@ -1928,7 +1928,7 @@ CONFIGURE OPTIONS
           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.
 
@@ -1969,7 +1969,7 @@ CONFIGURE OPTIONS
         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"
diff --git a/doc/rxvtc.1.html b/doc/rxvtc.1.html
index 3a34b505..ea1d569e 100644
--- a/doc/rxvtc.1.html
+++ b/doc/rxvtc.1.html
@@ -50,7 +50,7 @@ contacting the daemon.
    
 
    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
+process environment and any file descriptor (e.g. for -pty-fd) are
 preserved, this rarely makes a difference.
    
 
    
 
    
diff --git a/doc/rxvtc.1.man.in b/doc/rxvtc.1.man.in
index d667eb42..1abda749 100644
--- a/doc/rxvtc.1.man.in
+++ b/doc/rxvtc.1.man.in
@@ -129,7 +129,7 @@
 .\" ========================================================================
 .\"
 .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"
@@ -147,7 +147,7 @@ contacting the daemon.
 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"
diff --git a/doc/rxvtc.1.txt b/doc/rxvtc.1.txt
index 8ee41683..04103365 100644
--- a/doc/rxvtc.1.txt
+++ b/doc/rxvtc.1.txt
@@ -14,7 +14,7 @@ OPTIONS
     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
diff --git a/doc/rxvtperl.3.html b/doc/rxvtperl.3.html
index 65a73e04..3e88d27f 100644
--- a/doc/rxvtperl.3.html
+++ b/doc/rxvtperl.3.html
@@ -71,7 +71,7 @@
 
    
 
    
 
    DESCRIPTION
    
-
    Everytime a terminal object gets created, extension scripts specified via
+
    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
 thus must be encoded as UTF-8.
    
@@ -117,7 +117,7 @@ specifying resources of the form:
    
 
    
 
    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:
    
 
    
 
    
@@ -196,7 +196,7 @@ 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 something or not.
+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 transform $_.
    
@@ -319,7 +319,7 @@ the message into vi commands to load the file.
    
 
 
    
 
    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.
    
 
    
@@ -388,7 +388,7 @@ or show it again.
    
 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.
    
 
    
 
    
@@ -402,7 +402,7 @@ extension will actually grab a physical key just for this function.
    
 
    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:
    
 
    
 
    
 
    @@ -583,7 +583,7 @@ to overwrite time-critical hooks only temporarily.
    
 
    Hooks
    
 
    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
 hooks returns true, then the event counts as being consumed, and the
@@ -605,7 +605,7 @@ place.
    
 
 
    
 
    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.
    
 
    
 
 
    on_destroy $term
@@ -656,7 +656,7 @@ requested from the server.  The selection text can be queried and changed
 by calling $term->selection.
    
 
    
 
    
-
    Returning a true value aborts selection grabbing. It will still be hilighted.
    
+
    Returning a true value aborts selection grabbing. It will still be highlighted.
    
 
    
 
 
    on_sel_extend $term
@@ -664,7 +664,7 @@ by calling $term->selection.
    
 
    
 
    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.
    
@@ -676,7 +676,7 @@ supposed to enlarge the selection more and more, if possible.
    
 
    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.
    
 
    
@@ -719,7 +719,7 @@ 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, messages from
+as its source can not easily be controlled (e-mail content, messages from
 other users on the same system etc.).
    
 
    
 
@@ -776,7 +776,7 @@ code is run after this hook, and takes precedence.
    
 
    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 perl:string action bound to a key, see description of the keysym
 resource in the rxvt(1) manpage).
    
 
    
@@ -788,7 +788,7 @@ slightly in the future.
    
 
    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 TRUE, setting of the window hints is being skipped.
    
 
    
@@ -817,7 +817,7 @@ does focus in processing.
    
 
    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.
    
 
    
 
@@ -901,13 +901,13 @@ object, whenever a callback/hook is executing.
    
 
    @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 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.
    
+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 executed
+
    This complements to the perl-eval command line option, but gets executed
 first.
    
 
    
 
@@ -951,7 +951,7 @@ correct place, e.g. on stderr of the connecting urxvtc client.
    
 
 
    
 
    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).
    
 
    
@@ -1110,7 +1110,7 @@ optionally change it. All option values are stored by name in the 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
+
    Here is a likely non-exhaustive list of option names, please see the
 source file /src/optinc.h to see the actual list:
    
 
    
 
    
@@ -1145,7 +1145,7 @@ likely change).
    
 terminal is destroyed, so changing options frequently will eat memory.
    
 
    
 
    
-
    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 /src/rsinc.h
 to see the actual list:
    
 
    
@@ -1502,7 +1502,7 @@ AltGr), the meta key (often Alt) and the num lock key, if applicable.
    
 
    $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])
@@ -1647,7 +1647,7 @@ where one character corresponds to one screen cell. See
 
    $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.
    
 
    
 
@@ -1664,7 +1664,7 @@ manpage.
    
 
 
    
 
    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
@@ -1872,7 +1872,7 @@ is a bitset as described in the events m
 
    $iow = $iow->fd ($fd)
 
 
    
-
    Set the filedescriptor (not handle) to watch.
    
+
    Set the file descriptor (not handle) to watch.
    
 
    
 
 
    $iow = $iow->events ($eventmask)
@@ -1892,7 +1892,7 @@ together, or urxvt::EVENT_NONE.
    
 
    $iow = $iow->stop
 
 
    
-
    Stop watching for events on the given filehandle.
    
+
    Stop watching for events on the given file handle.
    
 
    
 
 
@@ -1959,7 +1959,7 @@ process exits, after which they stop automatically.
    
 
    $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
@@ -1985,7 +1985,7 @@ numbers indicate more verbose output.
    
 
 
    >=10 - all called hooks
 
-
    >=11 - hook reutrn values
+
    >=11 - hook return values
 
 
 
    
diff --git a/doc/rxvtperl.3.man.in b/doc/rxvtperl.3.man.in
index 62af4eef..05f20e98 100644
--- a/doc/rxvtperl.3.man.in
+++ b/doc/rxvtperl.3.man.in
@@ -129,7 +129,7 @@
 .\" ========================================================================
 .\"
 .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"
@@ -148,7 +148,7 @@
 .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
@@ -195,7 +195,7 @@ specifying resources of the form:
 .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
@@ -260,7 +260,7 @@ onto \f(CW\*(C`@{ $term\-\*(C'\fR{selection_popup_hook} }>, which gets called wh
 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.
@@ -366,7 +366,7 @@ the message into vi commands to load the file.
 .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
@@ -419,7 +419,7 @@ Initially, the window will not be shown when using this extension.
 This is useful if you need a single terminal thats not using any desktop
 space most of the time but is quickly available at the press of a key.
 .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
@@ -429,7 +429,7 @@ 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
@@ -568,7 +568,7 @@ Dynamically disable the given hooks.
 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
@@ -589,7 +589,7 @@ place.
 .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"
@@ -626,13 +626,13 @@ Called whenever a selection has been copied, but before the selection is
 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.
@@ -641,7 +641,7 @@ See the \fIselection\fR example extension.
 .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
@@ -675,7 +675,7 @@ it from commands for other extensions, and this might be enforced in the
 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
@@ -718,7 +718,7 @@ Called just after the screen gets redrawn. See \f(CW\*(C`on_refresh_begin\*(C'\f
 .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
@@ -727,7 +727,7 @@ slightly in the future.
 .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
@@ -748,7 +748,7 @@ does focus in processing.
 .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
@@ -827,12 +827,12 @@ object, whenever a callback/hook is executing.
 .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
@@ -864,7 +864,7 @@ Messages have a size limit of 1023 bytes currently.
 .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
@@ -984,7 +984,7 @@ Returns true if the option specified by \f(CW$optval\fR is enabled, and
 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
@@ -1013,7 +1013,7 @@ likely change).
 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
@@ -1315,7 +1315,7 @@ Returns the currently displayed screen (0 primary, 1 secondary).
 .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])"
@@ -1429,7 +1429,7 @@ where one character corresponds to one screen cell. See
 .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
@@ -1445,7 +1445,7 @@ manpage.
 .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"
@@ -1621,7 +1621,7 @@ is a bitset as described in the \f(CW\*(C`events\*(C'\fR method.
 .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)"
@@ -1635,7 +1635,7 @@ Start watching for requested events on the given handle.
 .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"
@@ -1686,7 +1686,7 @@ Set the callback to be called when the timer triggers.
 .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"
@@ -1704,8 +1704,8 @@ numbers indicate more verbose output.
 .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"
diff --git a/doc/rxvtperl.3.txt b/doc/rxvtperl.3.txt
index a65d9d71..f623d552 100644
--- a/doc/rxvtperl.3.txt
+++ b/doc/rxvtperl.3.txt
@@ -14,7 +14,7 @@ SYNOPSIS
        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
@@ -55,7 +55,7 @@ PREPACKAGED EXTENSIONS
 
         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: \\|([^|]+)\\|
@@ -109,7 +109,7 @@ PREPACKAGED EXTENSIONS
         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
@@ -200,7 +200,7 @@ PREPACKAGED EXTENSIONS
 
     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.
@@ -250,7 +250,7 @@ PREPACKAGED EXTENSIONS
         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
@@ -260,7 +260,7 @@ PREPACKAGED EXTENSIONS
         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
 
@@ -383,7 +383,7 @@ API DOCUMENTATION
     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
@@ -403,7 +403,7 @@ API DOCUMENTATION
     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
@@ -436,12 +436,12 @@ API DOCUMENTATION
         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
@@ -450,7 +450,7 @@ API DOCUMENTATION
         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.
 
@@ -481,7 +481,7 @@ API DOCUMENTATION
         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
@@ -519,15 +519,15 @@ API DOCUMENTATION
         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.
@@ -545,8 +545,8 @@ API DOCUMENTATION
         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
@@ -594,13 +594,13 @@ API DOCUMENTATION
         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
@@ -627,7 +627,7 @@ API DOCUMENTATION
 
     @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).
@@ -736,8 +736,8 @@ API DOCUMENTATION
         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
@@ -763,7 +763,7 @@ API DOCUMENTATION
         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:
 
@@ -984,7 +984,7 @@ API DOCUMENTATION
         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
@@ -1078,7 +1078,7 @@ API DOCUMENTATION
         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 =
@@ -1089,7 +1089,7 @@ API DOCUMENTATION
 
     $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.
@@ -1212,7 +1212,7 @@ API DOCUMENTATION
         $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
@@ -1223,7 +1223,7 @@ API DOCUMENTATION
         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
@@ -1263,7 +1263,7 @@ API DOCUMENTATION
         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.
@@ -1276,7 +1276,7 @@ ENVIRONMENT
     == 0 - fatal messages
     >= 3 - script loading and management
     >=10 - all called hooks
-    >=11 - hook reutrn values
+    >=11 - hook return values
 
 AUTHOR
      Marc Lehmann 
diff --git a/src/Makefile.in b/src/Makefile.in
index 07dbb4c3..2c3e2ba1 100644
--- a/src/Makefile.in
+++ b/src/Makefile.in
@@ -1532,3 +1532,102 @@ xdefaults.lo: keyboard.h
 xpm.lo: ../config.h rxvt.h rxvtlib.h optinc.h feature.h encoding.h rxvtutil.h
 xpm.lo: rxvtfont.h rxvttoolkit.h iom.h iom_conf.h callback.h salloc.h
 xpm.lo: libptytty.h rxvtperl.h hookinc.h rsinc.h
+
+command.lo: ../config.h rxvt.h rxvtlib.h optinc.h feature.h encoding.h
+command.lo: rxvtutil.h rxvtfont.h rxvttoolkit.h iom.h iom_conf.h callback.h
+command.lo: salloc.h libptytty.h rxvtperl.h hookinc.h rsinc.h version.h
+command.lo: command.h keyboard.h
+encoding.lo: ../config.h encoding.h table/iso8859_1.h table/iso8859_15.h
+encoding.lo: table/iso8859_2.h table/iso8859_3.h table/iso8859_4.h
+encoding.lo: table/iso8859_5.h table/iso8859_6.h table/iso8859_7.h
+encoding.lo: table/iso8859_8.h table/iso8859_9.h table/iso8859_10.h
+encoding.lo: table/iso8859_11.h table/iso8859_13.h table/iso8859_14.h
+encoding.lo: table/iso8859_16.h table/koi8_r.h table/koi8_u.h
+encoding.lo: table/ksc5601_1987_0.h table/big5.h table/gbk_0.h
+encoding.lo: table/gb2312_1980_0.h table/cns11643_1992_1.h
+encoding.lo: table/cns11643_1992_2.h table/cns11643_1992_3.h
+encoding.lo: table/cns11643_1992_4.h table/cns11643_1992_5.h
+encoding.lo: table/cns11643_1992_6.h table/cns11643_1992_7.h
+encoding.lo: table/cns11643_1992_f.h table/big5_ext.h table/big5_plus.h
+encoding.lo: table/viscii.h table/jis0201_1976_0.h table/jis0208_1990_0.h
+encoding.lo: table/jis0212_1990_0.h table/jis0213_1.h table/jis0213_2.h
+encoding.lo: table/compose.h table/category.h
+fdpass.lo: ../config.h libptytty.h
+init.lo: ../config.h rxvt.h rxvtlib.h optinc.h feature.h encoding.h
+init.lo: rxvtutil.h rxvtfont.h rxvttoolkit.h iom.h iom_conf.h callback.h
+init.lo: salloc.h libptytty.h rxvtperl.h hookinc.h rsinc.h init.h
+iom.lo: iom.h iom_conf.h rxvtutil.h callback.h
+keyboard.lo: ../config.h rxvt.h rxvtlib.h optinc.h feature.h encoding.h
+keyboard.lo: rxvtutil.h rxvtfont.h rxvttoolkit.h iom.h iom_conf.h callback.h
+keyboard.lo: salloc.h libptytty.h rxvtperl.h hookinc.h rsinc.h keyboard.h
+keyboard.lo: command.h
+logging.lo: ../config.h ptytty.h libptytty.h ptytty_conf.h rxvt.h rxvtlib.h
+logging.lo: optinc.h feature.h encoding.h rxvtutil.h rxvtfont.h rxvttoolkit.h
+logging.lo: iom.h iom_conf.h callback.h salloc.h rxvtperl.h hookinc.h rsinc.h
+main.lo: ../config.h rxvt.h rxvtlib.h optinc.h feature.h encoding.h
+main.lo: rxvtutil.h rxvtfont.h rxvttoolkit.h iom.h iom_conf.h callback.h
+main.lo: salloc.h libptytty.h rxvtperl.h hookinc.h rsinc.h keyboard.h
+misc.lo: ../config.h rxvt.h rxvtlib.h optinc.h feature.h encoding.h
+misc.lo: rxvtutil.h rxvtfont.h rxvttoolkit.h iom.h iom_conf.h callback.h
+misc.lo: salloc.h libptytty.h rxvtperl.h hookinc.h rsinc.h
+netdisp.lo: ../config.h rxvt.h rxvtlib.h optinc.h feature.h encoding.h
+netdisp.lo: rxvtutil.h rxvtfont.h rxvttoolkit.h iom.h iom_conf.h callback.h
+netdisp.lo: salloc.h libptytty.h rxvtperl.h hookinc.h rsinc.h
+proxy.lo: ../config.h ptytty.h libptytty.h ptytty_conf.h rxvt.h rxvtlib.h
+proxy.lo: optinc.h feature.h encoding.h rxvtutil.h rxvtfont.h rxvttoolkit.h
+proxy.lo: iom.h iom_conf.h callback.h salloc.h rxvtperl.h hookinc.h rsinc.h
+ptytty.lo: ../config.h ptytty.h libptytty.h ptytty_conf.h rxvt.h rxvtlib.h
+ptytty.lo: optinc.h feature.h encoding.h rxvtutil.h rxvtfont.h rxvttoolkit.h
+ptytty.lo: iom.h iom_conf.h callback.h salloc.h rxvtperl.h hookinc.h rsinc.h
+rxvt.lo: ../config.h rxvt.h rxvtlib.h optinc.h feature.h encoding.h
+rxvt.lo: rxvtutil.h rxvtfont.h rxvttoolkit.h iom.h iom_conf.h callback.h
+rxvt.lo: salloc.h libptytty.h rxvtperl.h hookinc.h rsinc.h
+rxvtc.lo: ../config.h rxvtdaemon.h rxvtutil.h libptytty.h rxvt.h rxvtlib.h
+rxvtc.lo: optinc.h feature.h encoding.h rxvtfont.h rxvttoolkit.h iom.h
+rxvtc.lo: iom_conf.h callback.h salloc.h rxvtperl.h hookinc.h rsinc.h
+rxvtd.lo: ../config.h rxvt.h rxvtlib.h optinc.h feature.h encoding.h
+rxvtd.lo: rxvtutil.h rxvtfont.h rxvttoolkit.h iom.h iom_conf.h callback.h
+rxvtd.lo: salloc.h libptytty.h rxvtperl.h hookinc.h rsinc.h rxvtdaemon.h
+rxvtdaemon.lo: rxvtdaemon.h rxvtutil.h
+rxvtfont.lo: ../config.h rxvt.h rxvtlib.h optinc.h feature.h encoding.h
+rxvtfont.lo: rxvtutil.h rxvtfont.h rxvttoolkit.h iom.h iom_conf.h callback.h
+rxvtfont.lo: salloc.h libptytty.h rxvtperl.h hookinc.h rsinc.h
+rxvtfont.lo: table/linedraw.h
+rxvtperl.lo: ../config.h iom.h iom_conf.h rxvtutil.h callback.h rxvt.h
+rxvtperl.lo: rxvtlib.h optinc.h feature.h encoding.h rxvtfont.h rxvttoolkit.h
+rxvtperl.lo: salloc.h libptytty.h rxvtperl.h hookinc.h rsinc.h keyboard.h
+rxvtperl.lo: perlxsi.c
+rxvttoolkit.lo: ../config.h rxvt.h rxvtlib.h optinc.h feature.h encoding.h
+rxvttoolkit.lo: rxvtutil.h rxvtfont.h rxvttoolkit.h iom.h iom_conf.h
+rxvttoolkit.lo: callback.h salloc.h libptytty.h rxvtperl.h hookinc.h rsinc.h
+rxvtutil.lo: rxvtutil.h
+salloc.lo: salloc.h
+screen.lo: ../config.h rxvt.h rxvtlib.h optinc.h feature.h encoding.h
+screen.lo: rxvtutil.h rxvtfont.h rxvttoolkit.h iom.h iom_conf.h callback.h
+screen.lo: salloc.h libptytty.h rxvtperl.h hookinc.h rsinc.h salloc.C
+scrollbar-next.lo: ../config.h rxvt.h rxvtlib.h optinc.h feature.h encoding.h
+scrollbar-next.lo: rxvtutil.h rxvtfont.h rxvttoolkit.h iom.h iom_conf.h
+scrollbar-next.lo: callback.h salloc.h libptytty.h rxvtperl.h hookinc.h
+scrollbar-next.lo: rsinc.h
+scrollbar-plain.lo: ../config.h rxvt.h rxvtlib.h optinc.h feature.h
+scrollbar-plain.lo: encoding.h rxvtutil.h rxvtfont.h rxvttoolkit.h iom.h
+scrollbar-plain.lo: iom_conf.h callback.h salloc.h libptytty.h rxvtperl.h
+scrollbar-plain.lo: hookinc.h rsinc.h
+scrollbar-rxvt.lo: ../config.h rxvt.h rxvtlib.h optinc.h feature.h encoding.h
+scrollbar-rxvt.lo: rxvtutil.h rxvtfont.h rxvttoolkit.h iom.h iom_conf.h
+scrollbar-rxvt.lo: callback.h salloc.h libptytty.h rxvtperl.h hookinc.h
+scrollbar-rxvt.lo: rsinc.h
+scrollbar-xterm.lo: ../config.h rxvt.h rxvtlib.h optinc.h feature.h
+scrollbar-xterm.lo: encoding.h rxvtutil.h rxvtfont.h rxvttoolkit.h iom.h
+scrollbar-xterm.lo: iom_conf.h callback.h salloc.h libptytty.h rxvtperl.h
+scrollbar-xterm.lo: hookinc.h rsinc.h
+scrollbar.lo: ../config.h rxvt.h rxvtlib.h optinc.h feature.h encoding.h
+scrollbar.lo: rxvtutil.h rxvtfont.h rxvttoolkit.h iom.h iom_conf.h callback.h
+scrollbar.lo: salloc.h libptytty.h rxvtperl.h hookinc.h rsinc.h
+xdefaults.lo: ../config.h rxvt.h rxvtlib.h optinc.h feature.h encoding.h
+xdefaults.lo: rxvtutil.h rxvtfont.h rxvttoolkit.h iom.h iom_conf.h callback.h
+xdefaults.lo: salloc.h libptytty.h rxvtperl.h hookinc.h rsinc.h version.h
+xdefaults.lo: keyboard.h
+xpm.lo: ../config.h rxvt.h rxvtlib.h optinc.h feature.h encoding.h rxvtutil.h
+xpm.lo: rxvtfont.h rxvttoolkit.h iom.h iom_conf.h callback.h salloc.h
+xpm.lo: libptytty.h rxvtperl.h hookinc.h rsinc.h
diff --git a/src/version.h b/src/version.h
index de0f6511..2edb85fe 100644
--- a/src/version.h
+++ b/src/version.h
@@ -1,3 +1,3 @@
 // VERSION _must_ be \d.\d+
-#define VERSION "7.8"
-#define DATE	"2006-07-17"
+#define VERSION "7.9"
+#define DATE	"2006-08-07"
-- 
2.34.1