SEE ALSO

rxvt(7), rxvtc(1), rxvtd(1), xterm(1), sh(1), resize(1), X(1), pty(4), tty(4), utmp(5)

urxvt(7), urxvtc(1), urxvtd(1), xterm(1), sh(1), resize(1), X(1), pty(4), tty(4), utmp(5)

--- 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-06" "7.7" "RXVT-UNICODE"
+.TH @@RXVT_NAME@@ 1 "2006-07-17" "7.8" "RXVT-UNICODE"
 .SH "NAME"
 rxvt\-unicode (ouR XVT, unicode) \- (a VT102 emulator for the X window system)
 .SH "SYNOPSIS"
diff --git a/doc/rxvt.1.txt b/doc/rxvt.1.txt

--- a/doc/rxvt.1.txt
+++ b/doc/rxvt.1.txt
@@ -3,19 +3,19 @@ NAME
     system)

 SYNOPSIS
-    rxvt [options] [-e command [ args ]]
+    urxvt [options] [-e command [ args ]]

 DESCRIPTION
-    rxvt-unicode, version 7.7, is a colour vt102 terminal emulator intended
+    rxvt-unicode, version 7.8, is a colour vt102 terminal emulator intended
     as an *xterm*(1) replacement for users who do not require features such
     as Tektronix 4014 emulation and toolkit-style configurability. As a
     result, rxvt-unicode uses much less swap space -- a significant
     advantage on a machine serving many X sessions.

 FREQUENTLY ASKED QUESTIONS
-    See rxvt(7) (try "man 7 rxvt") for a list of frequently asked questions
-    and answer to them and some common problems. That document is also
-    accessible on the World-Wide-Web at
+    See urxvt(7) (try "man 7 urxvt") for a list of frequently asked
+    questions and answer to them and some common problems. That document is
+    also accessible on the World-Wide-Web at
     .

 RXVT-UNICODE VS. RXVT
@@ -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 rxvtd(1) (daemon) and rxvtc(1)
+    drastically reduces memory usage. See urxvtd(1) (daemon) and urxvtc(1)
     (client).

     It also makes technical information about escape sequences (which have
-    been extended) easier accessible: see rxvt(7) for technical reference
+    been extended) easier accessible: see urxvt(7) for technical reference
     documentation (escape sequences etc.).

 OPTIONS
-    The rxvt options (mostly a subset of *xterm*'s) are listed below. In
+    The urxvt options (mostly a subset of *xterm*'s) are listed below. In
     keeping with the smaller-is-better philosophy, options may be eliminated
     or default values chosen at compile-time, so options and defaults listed
-    may not accurately reflect the version installed on your system. `rxvt
+    may not accurately reflect the version installed on your system. `urxvt
     -h' gives a list of major compile-time options on the *Options* line.
     Option descriptions may be prefixed with which compile option each is
     dependent upon. e.g. `Compile *XIM*:' requires *XIM* on the *Options*
-    line. Note: `rxvt -help' gives a list of all command-line options
+    line. Note: `urxvt -help' gives a list of all command-line options
     compiled into your version.

-    Note that rxvt permits the resource name to be used as a long-option
+    Note that urxvt permits the resource name to be used as a long-option
     (--/++ option) so the potential command-line options are far greater
-    than those listed. For example: `rxvt --loginShell --color1 Orange'.
+    than those listed. For example: `urxvt --loginShell --color1 Orange'.

     The following options are available:

@@ -122,7 +122,7 @@ OPTIONS
         be used to brighten or darken the image in addition to tinting it;
         resource *tintColor*. Example:

-           rxvt -tr -tint blue -sh 40
+           urxvt -tr -tint blue -sh 40

     -sh *number* Darken (0 .. 100) or lighten (-1 .. -100) the transparent
         background image in addition to tinting it (i.e. -tint must be
@@ -165,11 +165,11 @@ OPTIONS
         prefix it with "x:". To specify an XFT-font, you need to prefix it
         with "xft:", e.g.:

-           rxvt -fn "xft:Bitstream Vera Sans Mono:pixelsize=15"
-           rxvt -fn "9x15bold,xft:Bitstream Vera Sans Mono"
+           urxvt -fn "xft:Bitstream Vera Sans Mono:pixelsize=15"
+           urxvt -fn "9x15bold,xft:Bitstream Vera Sans Mono"

         See also the question "How does rxvt-unicode choose fonts?" in the
-        FAQ section of rxvt(7).
+        FAQ section of urxvt(7).

     -fb *fontlist*
         Compile *font-styles*: The bold font list to use when bold
@@ -283,7 +283,7 @@ OPTIONS
         resource termName.

     -e *command [arguments]*
-        Run the command with its command-line arguments in the rxvt window;
+        Run the command with its command-line arguments in the urxvt window;
         also sets the window title and icon name to be the basename of the
         program being executed if neither *-title* (*-T*) nor *-n* are given
         on the command line. If this option is used, it must be the last on
@@ -295,7 +295,7 @@ OPTIONS
         want to run shell commands, you have to specify the shell, like
         this:

-          rxvt -e sh -c "shell commands"
+          urxvt -e sh -c "shell commands"

     -title *text*
         Window title (-T still respected); the default title is the basename
@@ -350,7 +350,7 @@ OPTIONS
         secondaryScroll.

     -hold|+hold
-        Turn on/off hold window after exit support. If enabled, rxvt will
+        Turn on/off hold window after exit support. If enabled, urxvt will
         not immediately destroy its window when the program executed within
         it exits. Instead, it will wait till it is being killed or closed by
         the user; resource hold.
@@ -359,21 +359,21 @@ OPTIONS
         Remap a key symbol. See resource keysym.

     -embed *windowid*
-        Tells rxvt to embed its windows into an already-existing window,
+        Tells urxvt to embed its windows into an already-existing window,
         which enables applications to easily embed a terminal.

-        Right now, rxvt will first unmap/map the specified window, so it
-        shouldn't be a top-level window. rxvt will also reconfigure it quite
-        a bit, so don't expect it to keep some specific state. It's best to
-        create an extra subwindow for rxvt and leave it alone.
+        Right now, urxvt will first unmap/map the specified window, so it
+        shouldn't be a top-level window. urxvt will also reconfigure it
+        quite a bit, so don't expect it to keep some specific state. It's
+        best to create an extra subwindow for urxvt and leave it alone.

-        The window will not be destroyed when rxvt exits.
+        The window will not be destroyed when urxvt exits.

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

         Here is a short Gtk2-perl snippet that illustrates how this option
         can be used (a longer example is in doc/embed):
@@ -381,16 +381,16 @@ OPTIONS
            my $rxvt = new Gtk2::Socket;
            $rxvt->signal_connect_after (realize => sub {
               my $xid = $_[0]->window->get_xid;
-              system "rxvt -embed $xid &";
+              system "urxvt -embed $xid &";
            });

     -pty-fd *file descriptor*
-        Tells rxvt NOT to execute any commands or create a new pty/tty pair
+        Tells urxvt NOT to execute any commands or create a new pty/tty pair
         but instead use the given filehandle as the tty master. This is
-        useful if you want to drive rxvt as a generic terminal emulator
+        useful if you want to drive urxvt as a generic terminal emulator
         without having to run a program within it.

-        If this switch is given, rxvt will not create any utmp/wtmp entries
+        If this switch is given, urxvt will not create any utmp/wtmp entries
         and will not tinker with pty/tty permissions - you have to do that
         yourself if you want that.

@@ -405,7 +405,7 @@ OPTIONS

            my $pty = new IO::Pty;
            fcntl $pty, F_SETFD, 0; # clear close-on-exec
-           system "rxvt -pty-fd " . (fileno $pty) . "&";
+           system "urxvt -pty-fd " . (fileno $pty) . "&";
            close $pty;

            # now communicate with rxvt
@@ -417,12 +417,12 @@ OPTIONS
         use) in this terminal instance. See resource perl-ext for details.

 RESOURCES (available also as long-options)
-    Note: `rxvt --help' gives a list of all resources (long options)
+    Note: `urxvt --help' gives a list of all resources (long options)
     compiled into your version.

     You can set and change the resources using X11 tools like xrdb. Many
     distribution do also load settings from the ~/.Xresources file when X
-    starts. rxvt will consult the following files/resources in order, with
+    starts. urxvt will consult the following files/resources in order, with
     later settings overwriting earlier ones:

       1. system-wide app-defaults file, either locale-dependent OR global
@@ -431,15 +431,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, rxvt recognizes two class names:
-    Rxvt and URxvt. The class name Rxvt allows resources common to both rxvt
-    and the original *rxvt* to be easily configured, while the class name
-    URxvt allows resources unique to rxvt, to be shared between different
-    rxvt configurations. If no resources are specified, suitable defaults
-    will be used. Command-line arguments can be used to override resource
-    settings. The following resources are supported (you might want to check
-    the rxvtperl(3) manpage for additional settings by perl extensions not
-    documented here):
+    Note that when reading X resources, urxvt recognizes two class names:
+    Rxvt and URxvt. The class name Rxvt allows resources common to both
+    urxvt and the original *rxvt* to be easily configured, while the class
+    name URxvt allows resources unique to urxvt, to be shared between
+    different urxvt configurations. If no resources are specified, suitable
+    defaults will be used. Command-line arguments can be used to override
+    resource settings. The following resources are supported (you might want
+    to check the urxvtperl(3) manpage for additional settings by perl
+    extensions not documented here):

     depth: *bitdepth*
         Compile *xft*: Attempt to find a visual with the given bit depth;
@@ -467,7 +467,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 rxvt(7)).
+        be changed using an escape command (see urxvt(7)).

         Colours 16-79 form a standard 4x4x4 colour cube (the same as xterm
         with 88 colour support). Colours 80-87 are evenly spaces grey steps.
@@ -789,7 +789,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 rxvtperl(3) manpage), a suitable regex using these
+        see the urxvtperl(3) manpage), a suitable regex using these
         characters will be created (if the resource exists, otherwise, no
         regex will be created). In this mode, characters outside ISO-8859-1
         can be used.
@@ -815,7 +815,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 rxvt. The default will be set-up to chose *any*
+        font lists used in urxvt. The default will be set-up to chose *any*
         suitable found found, preferably one or two pixels differing in size
         to the base font. option -imfont.

@@ -857,7 +857,7 @@ RESOURCES (available also as long-options)
         instead scroll the screen up.

     hold: *boolean*
-        Turn on/off hold window after exit support. If enabled, rxvt will
+        Turn on/off hold window after exit support. If enabled, urxvt will
         not immediately destroy its window when the program executed within
         it exits. Instead, it will wait till it is being killed or closed by
         the user.
@@ -891,7 +891,7 @@ 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 rxvt's own
+        "\e" (and so on), which will work with both Xt and urxvt's own
         processing).

         You can define a range of keysyms in one shot by providing a
@@ -909,7 +909,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 rxvt's control sequence. For example
+        is interpreted and executed as urxvt's control sequence. For example
         the following means "change the current locale to "zh_CN.GBK" when
         Control-Meta-c is being pressed":

@@ -917,8 +917,9 @@ 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
-        rxvtperl(3) manpage. For example, the selection extension (activated
-        via "rxvt -pe selection") listens for "selection:rot13" events:
+        urxvtperl(3) manpage. For example, the selection extension
+        (activated via "urxvt -pe selection") listens for "selection:rot13"
+        events:

           URxvt.keysym.M-C-c: perl:selection:rot13

@@ -930,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 rxvt's
+        if you overwrite the "Insert" key you will disable urxvt's
         "Shift-Insert" mapping. To re-enable that, you can poke "holes" into
         the user-defined keymap using the "builtin:" replacement:

@@ -948,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 rxvt(7) for more
+        Other things are possible, e.g. resizing (see urxvt(7) for more
         info):

           URxvt.keysym.M-C-3: command:\033[8;25;80t
@@ -982,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 rxvtperl(3) manpage. Due to security reasons, this resource
+        See the urxvtperl(3) manpage. Due to security reasons, this resource
         will be ignored when running setuid/setgid.

     perl-lib: *path*
         Colon-separated list of additional directories that hold extension
         scripts. When looking for extensions specified by the "perl"
-        resource, rxvt will first look in these directories and then in
-        /opt/rxvt/lib/urxvt/perl/. Due to security reasons, this resource
+        resource, urxvt will first look in these directories and then in
+        /usr/local/lib/urxvt/perl/. Due to security reasons, this resource
         will be ignored when running setuid/setgid.

-        See the rxvtperl(3) manpage.
+        See the urxvtperl(3) manpage.

     selection.pattern-*idx*: *perl-regex*
-        Additional selection patterns, see the rxvtperl(3) manpage for
+        Additional selection patterns, see the urxvtperl(3) manpage for
         details.

     selection-autotransform.*idx*: *perl-transform*
-        Selection auto-transform patterns, see the rxvtperl(3) manpage for
+        Selection auto-transform patterns, see the urxvtperl(3) manpage for
         details.

     searchable-scrollback: *keysym*
@@ -1020,9 +1021,9 @@ RESOURCES (available also as long-options)
         -override-redirect.

 THE SCROLLBAR
-    Lines of text that scroll off the top of the rxvt window (resource:
+    Lines of text that scroll off the top of the urxvt window (resource:
     saveLines) and can be scrolled back using the scrollbar or by
-    keystrokes. The normal rxvt scrollbar has arrows and its behaviour is
+    keystrokes. The normal urxvt scrollbar has arrows and its behaviour is
     fairly intuitive. The xterm-scrollbar is without arrows and its
     behaviour mimics that of *xterm*

@@ -1059,7 +1060,7 @@ TEXT SELECTION AND INSERTION
         removed from the selection.

     Insertion:
-        Pressing and releasing the Middle mouse button in an rxvt window
+        Pressing and releasing the Middle mouse button in an urxvt window
         causes the value of the PRIMARY selection (or CLIPBOARD with the
         Meta modifier) to be inserted as if it had been typed on the
         keyboard.
@@ -1147,13 +1148,13 @@ ISO 14755 SUPPORT
     both scenario A and B of ISO 14755, including part 5.2.

 LOGIN STAMP
-    rxvt tries to write an entry into the *utmp*(5) file so that it can be
+    urxvt tries to write an entry into the *utmp*(5) file so that it can be
     seen via the *who(1)* command, and can accept messages. To allow this
-    feature, rxvt may need to be installed setuid root on some systems or
+    feature, urxvt may need to be installed setuid root on some systems or
     setgid to root or to some other group on others.

 COLORS AND GRAPHICS
-    In addition to the default foreground and background colours, rxvt can
+    In addition to the default foreground and background colours, urxvt can
     display up to 16 colours (8 ANSI colours plus high-intensity bold/blink
     versions of the same). Here is a list of the colours with their names.

@@ -1180,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, rxvt offers an additional 72
+    In addition to the colours defined above, urxvt offers an additional 72
     colours. The first 64 of those (with indices 16 to 79) consist of a
     4*4*4 RGB colour cube (i.e. *index = r * 16 + g * 4 + b + 16*), followed
     by 8 additional shades of gray (with indices 80 to 87).
@@ -1194,7 +1195,7 @@ COLORS AND GRAPHICS
     *xterm*(1) where the colours are only swapped if they have not otherwise
     been specified. For example,

-    rxvt -fg Black -bg White -rv
+    urxvt -fg Black -bg White -rv
         would yield White on Black, while on *xterm*(1) it would yield Black
         on White.

@@ -1215,20 +1216,20 @@ COLORS AND GRAPHICS
     For example, the following selects an almost completely transparent red
     background, and an almost opaque pink foreground:

-       rxvt -depth 32 -bg rgba:0000/0000/0000/2222 -fg "[e]pink"
+       urxvt -depth 32 -bg rgba:0000/0000/0000/2222 -fg "[e]pink"

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

 ENVIRONMENT
-    rxvt sets and/or uses the following environment variables:
+    urxvt sets and/or uses the following environment variables:

     TERM
         Normally set to "rxvt-unicode", unless overwritten at configure
         time, via resources or on the commandline.

     COLORTERM
-        Either "rxvt", "rxvt-xpm", depending on wether rxvt was compiled
+        Either "rxvt", "rxvt-xpm", depending on wether urxvt was compiled
         with XPM support, and optionally with the added extension "-mono" to
         indicate that rxvt-unicode runs on a monochrome screen.

@@ -1238,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 rxvt was compiled with XPM support. Libraries like "ncurses" and
+        if urxvt was compiled with XPM support. Libraries like "ncurses" and
         "slang" can (and do) use this information to optimize screen output.

     WINDOWID
-        Set to the (decimal) X Window ID of the rxvt window (the toplevel
+        Set to the (decimal) X Window ID of the urxvt window (the toplevel
         window, which usually has subwindows for the scrollbar, the terminal
         window and so on).

     TERMINFO
-        Set to the terminfo directory iff rxvt was configured with
+        Set to the terminfo directory iff urxvt was configured with
         "--with-terminfo=PATH".

     DISPLAY
-        Used by rxvt to connect to the display and set to the correct
+        Used by urxvt to connect to the display and set to the correct
         display in its child processes.

     SHELL
         The shell to be used for command execution, defaults to "/bin/sh".

     RXVT_SOCKET
-        The unix domain socket path used by rxvtc(1) and rxvtd(1).
+        The unix domain socket path used by urxvtc(1) and urxvtd(1).

         Default $HOME/.rxvt-unicode-*
index 81b14886d5bad3ab5c16f11f76a6bc134c9457ce..
index ..02956512e63774ae1fe9ad62bb8eff493b4904f0 100644
--- a/doc/rxvt.7.html
+++ b/doc/rxvt.7.html
@@ -2499,7 +2499,7 @@ in combination with other switches) is:

 
--enable-iso14755 (default: on)

 

-
Enable extended ISO 14755 support (see rxvt(1), or
+
Enable extended ISO 14755 support (see urxvt(1), or
 doc/rxvt.1.txt). Basic support (section 5.1) is enabled by
 --enable-frills, while support for 5.2, 5.3 and 5.4 is enabled with
 this switch.
@@ -2569,7 +2569,7 @@ the screen in a fixed position.

 
--enable-perl (default: on)

 

-
Enable an embedded perl interpreter. See the rxvtperl(3)
+
Enable an embedded perl interpreter. See the urxvtperl(3)
 manpage (doc/rxvtperl.txt) for more info on this feature, or the files
 in src/perl-ext/ for the extensions that are installed by default. The
 perl interpreter that is used can be specified via the PERL environment
diff --git a/doc/rxvt.7.man.in b/doc/rxvt.7.man.in

index b389a2f7b639bb676af825112bb4f29f6a7be433..
index ..8a1e7f8901bed37b3708f7d91c5c70db04cad399 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-06" "7.7" "RXVT-UNICODE"
+.TH @@RXVT_NAME@@ 7 "2006-07-17" "7.8" "RXVT-UNICODE"
 .SH "NAME"
 RXVT REFERENCE \- FAQ, command sequences and other background information
 .SH "SYNOPSIS"
diff --git a/doc/rxvt.7.txt b/doc/rxvt.7.txt

index d39449e0dd49132212a515871ddc8621bdb7cfe9..
index ..85d62a680d52d691922c7d6a93306e3e82446cc3 100644
--- a/doc/rxvt.7.txt
+++ b/doc/rxvt.7.txt
@@ -1928,7 +1928,7 @@ CONFIGURE OPTIONS
           verbose X error handling

     --enable-iso14755 (default: on)
-        Enable extended ISO 14755 support (see rxvt(1), or doc/rxvt.1.txt).
+        Enable extended ISO 14755 support (see urxvt(1), or doc/rxvt.1.txt).
         Basic support (section 5.1) is enabled by "--enable-frills", while
         support for 5.2, 5.3 and 5.4 is enabled with this switch.

@@ -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 rxvtperl(3) manpage
+        Enable an embedded perl interpreter. See the urxvtperl(3) manpage
         (doc/rxvtperl.txt) for more info on this feature, or the files in
         src/perl-ext/ for the extensions that are installed by default. The
         perl interpreter that is used can be specified via the "PERL"
diff --git a/doc/rxvtc.1.html b/doc/rxvtc.1.html

index 8b14a70b2456f56944bbe6594697c71bf61e57a6..
index ..7f051138d730189665f1a21dc54763cae0f60faa 100644
--- a/doc/rxvtc.1.html
+++ b/doc/rxvtc.1.html
@@ -1,7 +1,9 @@
+
 
 
 
-
+
+
 
 

@@ -26,62 +28,63 @@
 

 
 
NAME
-
rxvtc - control the rxvtd daemon
+
urxvtc - control the urxvtd daemon
 

 
 

 
SYNOPSIS
-
rxvtc [same options as for rxvt]
+
urxvtc [same options as for urxvt]
 

 
 

 
DESCRIPTION
-
This manpage describes the rxvtc client program. It connects
-to the rxvtd daemon and requests a new terminal window. It
-takes the same arguments as the rxvt program. The environment
+
This manpage describes the urxvtc client program. It connects
+to the urxvtd daemon and requests a new terminal window. It
+takes the same arguments as the urxvt program. The environment
 will also be respected. Currently, it always returns immediately after
 contacting the daemon.
 

 
 

 
OPTIONS
-
All options that are valid for rxvt are valid for
-rxvtc, too. Please note that all options are currently
+
All options that are valid for urxvt are valid for
+urxvtc, too. Please note that all options are currently
 interpreted in the context of the daemon process, which makes a difference
 for options that specify a file descriptor (such as -pty-fd).
 

 
 

 
EXIT STATUS
-
If everything went well, rxvtc returns with an exit status of 0.
+
If everything went well, urxvtc returns with an exit status of 0.
 If contacting the daemon fails, it exits with the exit status 2. In all other error
 cases it returns with status 1.
 
This can be used to implement auto-starting behaviour, by checking for an
-exit status of 2, running rxvtd -f -q and retrying the call
-to rxvtc.
+exit status of 2, running urxvtd -f -q and retrying the call
+to urxvtc.

 

 
 

 
ENVIRONMENT
 
All environment variables of the current process will be made available
-to the new instance, and will be interpreted as if rxvt were
+to the new instance, and will be interpreted as if urxvt were
 started directly.
 

-
RXVT_SOCKET

-
+
RXVT_SOCKET
+
 

-Both rxvtc and rxvtd use the environment variable
+
Both urxvtc and urxvtd use the environment variable
 RXVT_SOCKET to create a listening socket and to contact the
-rxvtd, respectively. If the variable is missing,
+urxvtd, respectively. If the variable is missing,
 $HOME/.rxvt-unicode-<nodename > >>> is used.  The variable must
-specify the absolute path of the socket to create.
+specify the absolute path of the socket to create.
 
-

+
+
 

 
 

 
SEE ALSO
-
rxvt(7), rxvtd(1)
+
urxvt(7), urxvtd(1)

 

diff --git a/doc/rxvtc.1.man.in b/doc/rxvtc.1.man.in

index 18eb947a82e6a998b629880561ae08257d34957c..
index ..f38d2acdc266b2fbc9275dc3f921acdb6f789e7d 100644
--- a/doc/rxvtc.1.man.in
+++ b/doc/rxvtc.1.man.in
@@ -1,4 +1,4 @@
-.\" Automatically generated by Pod::Man v1.37, Pod::Parser v1.14
+.\" Automatically generated by Pod::Man 2.09 (Pod::Simple 3.04)
 .\"
 .\" Standard preamble:
 .\" ========================================================================
@@ -128,8 +128,8 @@
 .rm #[ #] #H #V #F C
 .\" ========================================================================
 .\"
-.IX Title "rxvt 1"
-.TH rxvt 1 "2006-02-02" "7.5" "RXVT-UNICODE"
+.IX Title "@@RXVT_NAME@@ 1"
+.TH @@RXVT_NAME@@ 1 "2006-07-17" "7.8" "RXVT-UNICODE"
 .SH "NAME"
 @@RXVT_NAME@@c \- control the @@RXVT_NAME@@d daemon
 .SH "SYNOPSIS"
@@ -167,7 +167,7 @@ started directly.
 Both @@RXVT_NAME@@c and @@RXVT_NAME@@d use the environment variable
 \&\fI\s-1RXVT_SOCKET\s0\fR to create a listening socket and to contact the
 @@RXVT_NAME@@d, respectively. If the variable is missing,
-\&\fI$HOME/.rxvt\-unicode\-\fI\fI\fR is used.  The variable must
+\&\fI\f(CI$HOME\fI/.rxvt\-unicode\-\fI\fI\fR is used.  The variable must
 specify the absolute path of the socket to create.
 .SH "SEE ALSO"
 .IX Header "SEE ALSO"
diff --git a/doc/rxvtc.1.txt b/doc/rxvtc.1.txt

index 871987903a1ea13f60029033348d2e0418241f27..
index ..71a3563fa54cb805e609719862468429efc55fd6 100644
--- a/doc/rxvtc.1.txt
+++ b/doc/rxvtc.1.txt
@@ -1,41 +1,42 @@
 NAME
-    rxvtc - control the rxvtd daemon
+    urxvtc - control the urxvtd daemon

 SYNOPSIS
-    rxvtc [same options as for rxvt]
+    urxvtc [same options as for urxvt]

 DESCRIPTION
-    This manpage describes the rxvtc client program. It connects to the
-    rxvtd daemon and requests a new terminal window. It takes the same
-    arguments as the rxvt program. The environment will also be respected.
+    This manpage describes the urxvtc client program. It connects to the
+    urxvtd daemon and requests a new terminal window. It takes the same
+    arguments as the urxvt program. The environment will also be respected.
     Currently, it always returns immediately after contacting the daemon.

 OPTIONS
-    All options that are valid for rxvt are valid for rxvtc, too. Please
+    All options that are valid for urxvt are valid for urxvtc, too. Please
     note that all options are currently interpreted in the context of the
     daemon process, which makes a difference for options that specify a file
     descriptor (such as -pty-fd).

 EXIT STATUS
-    If everything went well, rxvtc returns with an exit status of 0. If
+    If everything went well, urxvtc returns with an exit status of 0. If
     contacting the daemon fails, it exits with the exit status 2. In all
     other error cases it returns with status 1.

     This can be used to implement auto-starting behaviour, by checking for
-    an exit status of 2, running "rxvtd -f -q" and retrying the call to
-    rxvtc.
+    an exit status of 2, running "urxvtd -f -q" and retrying the call to
+    urxvtc.

 ENVIRONMENT
     All environment variables of the current process will be made available
-    to the new instance, and will be interpreted as if rxvt were started
+    to the new instance, and will be interpreted as if urxvt were started
     directly.

     RXVT_SOCKET
-        Both rxvtc and rxvtd use the environment variable RXVT_SOCKET to
-        create a listening socket and to contact the rxvtd, respectively. If
-        the variable is missing, $HOME/.rxvt-unicode-** is used.
-        The variable must specify the absolute path of the socket to create.
+        Both urxvtc and urxvtd use the environment variable RXVT_SOCKET to
+        create a listening socket and to contact the urxvtd, respectively.
+        If the variable is missing, $HOME/.rxvt-unicode-** is
+        used. The variable must specify the absolute path of the socket to
+        create.

 SEE ALSO
-    rxvt(7), rxvtd(1)
+    urxvt(7), urxvtd(1)

diff --git a/doc/rxvtd.1.html b/doc/rxvtd.1.html

index 05956720f0a577d73390a12cc13805dcb4d8089e..
index ..ab7d02859ae9078138170073759534f39a8ff757 100644
--- a/doc/rxvtd.1.html
+++ b/doc/rxvtd.1.html
@@ -1,7 +1,9 @@
+
 
 
 
-
+
+
 
 

@@ -26,101 +28,102 @@
 

 
 
NAME
-
rxvtd - rxvt terminal daemon
+
urxvtd - urxvt terminal daemon
 

 
 

 
SYNOPSIS
-
rxvtd [-q|--quiet] [-o|--opendisplay] [-f|--fork]
+
urxvtd [-q|--quiet] [-o|--opendisplay] [-f|--fork]
 

 
 

 
DESCRIPTION
-
This manpage describes the rxvtd daemon, which is the same vt102
-terminal emulator as rxvt, but runs as a daemon that can open
+
This manpage describes the urxvtd daemon, which is the same vt102
+terminal emulator as urxvt, but runs as a daemon that can open
 multiple terminal windows within the same process.
 
You can run it from your X startup scripts, for example, although it is
 not dependent on a working DISPLAY and, in fact, can open windows on
 multiple X displays on the same time.
-
Advantages of running a rxvt daemon include faster creation time
+
Advantages of running a urxvt daemon include faster creation time
 for terminal windows and a lot of saved memory.
 
The disadvantage is a possible impact on stability - if the
 main program crashes, all processes in the terminal windows are
 terminated. For example, as there is no way to cleanly react to abnormal
 connection closes, xkill and server resets/restarts will kill the
-rxvtd instance including all windows it has opened.
+urxvtd instance including all windows it has opened.

 

 
 

 
OPTIONS
-
rxvtd currently understands a few options only. Bundling of
+
urxvtd currently understands a few options only. Bundling of
 options is not yet supported.
 

-
-q, --quiet

-
+
-q, --quiet
+
 

-Normally, rxvtd outputs the message rxvt-unicode daemon
+
Normally, urxvtd outputs the message rxvt-unicode daemon
 listening on <path> after binding to its control socket. This option
-will suppress this message (errors and warnings will still be logged).
+will suppress this message (errors and warnings will still be logged).
 

-

-
-o, --opendisplay

-
+
+
-o, --opendisplay
+
 

-This forces rxvtd to open a connection to the current
-$DISPLAY and keep it open.
+
This forces urxvtd to open a connection to the current
+$DISPLAY and keep it open.
 
 

-
This is useful if you want to bind an instance of rxvtd to
+
This is useful if you want to bind an instance of urxvtd to
 the lifetime of a specific display/server. If the server does a reset,
-rxvtd will be killed automatically.
+urxvtd will be killed automatically.

 
-

-
-f, --fork

-
+
+
-f, --fork
+
 

-This makes rxvtd fork after it has bound itself to its control
-socket.
+
This makes urxvtd fork after it has bound itself to its control
+socket.
 
-

+
+
 

 
 

 
EXAMPLES
-
This is a useful invocation of rxvtd in a .xsession-style
+
This is a useful invocation of urxvtd in a .xsession-style
 script:
 
-   B<rxvtd> -q -f -o
+   B<urxvtd> -q -f -o

 
This waits till the control socket is available, opens the current display
 and forks into the background. When you log-out, the server is reset and
-rxvtd is killed.
+urxvtd is killed.

 

 
 

 
ENVIRONMENT
 

-
RXVT_SOCKET

-
+
RXVT_SOCKET
+
 

-Both rxvtc and rxvtd use the environment
+
Both urxvtc and urxvtd use the environment
 variable RXVT_SOCKET to create a listening socket and to contact
-the rxvtd, respectively. If the variable is missing,
+the urxvtd, respectively. If the variable is missing,
 $HOME/.rxvt-unicode-<nodename > >>> is used. The variable must
-specify the absolute path of the socket to create.
+specify the absolute path of the socket to create.
 
-

-
DISPLAY

-
+
+
DISPLAY
+
 

-Only used when the --opendisplay option is specified. Must contain a
-valid X display name.
+
Only used when the --opendisplay option is specified. Must contain a
+valid X display name.
 
 
 

 
 

 
SEE ALSO
-
rxvt(7), rxvtc(1)
+
urxvt(7), urxvtc(1)

 

diff --git a/doc/rxvtd.1.man.in b/doc/rxvtd.1.man.in

--- a/doc/rxvtd.1.man.in
+++ b/doc/rxvtd.1.man.in
@@ -1,4 +1,4 @@
-.\" Automatically generated by Pod::Man v1.37, Pod::Parser v1.3
+.\" Automatically generated by Pod::Man 2.09 (Pod::Simple 3.04)
 .\"
 .\" Standard preamble:
 .\" ========================================================================
@@ -128,8 +128,8 @@
 .rm #[ #] #H #V #F C
 .\" ========================================================================
 .\"
-.IX Title "rxvt 1"
-.TH rxvt 1 "2005-12-17" "5.9" "RXVT-UNICODE"
+.IX Title "@@RXVT_NAME@@ 1"
+.TH @@RXVT_NAME@@ 1 "2006-07-17" "7.8" "RXVT-UNICODE"
 .SH "NAME"
 @@RXVT_NAME@@d \- @@RXVT_NAME@@ terminal daemon
 .SH "SYNOPSIS"
@@ -180,7 +180,7 @@ This is a useful invocation of \fB@@RXVT_NAME@@d\fR in a \fI.xsession\fR\-style
 script:
 .PP
 .Vb 1
-\&   B<@@RXVT_NAME@@d> -q -f -o
+\&   B<@@RXVT_NAME@@d> \-q \-f \-o
 .Ve
 .PP
 This waits till the control socket is available, opens the current display
@@ -193,14 +193,24 @@ and forks into the background. When you log\-out, the server is reset and
 Both \fB@@RXVT_NAME@@c\fR and \fB@@RXVT_NAME@@d\fR use the environment
 variable \fI\s-1RXVT_SOCKET\s0\fR to create a listening socket and to contact
 the @@RXVT_NAME@@d, respectively. If the variable is missing,
-\&\fI$HOME/.rxvt\-unicode\-\fI\fI\fR is used. The variable must
+\&\fI\f(CI$HOME\fI/.rxvt\-unicode\-\fI\fI\fR is used. The variable must
 specify the absolute path of the socket to create.
 .IP "\fB\s-1DISPLAY\s0\fR" 4
 .IX Item "DISPLAY"
 Only used when the \f(CW\*(C`\-\-opendisplay\*(C'\fR option is specified. Must contain a
 valid X display name.
 .RS 4
+.RE
+.RS 4
+.RE
 .SH "SEE ALSO"
 .IX Header "SEE ALSO"
-.RS 4
 @@RXVT_NAME@@(7), @@RXVT_NAME@@c(1)
+.SH "POD ERRORS"
+.IX Header "POD ERRORS"
+Hey! \fBThe above document had some coding errors, which are explained below:\fR
+.IP "Around line 87:" 4
+.IX Item "Around line 87:"
+You forgot a '=back' before '=head1'
+.Sp
+You forgot a '=back' before '=head1'
diff --git a/doc/rxvtd.1.txt b/doc/rxvtd.1.txt

--- a/doc/rxvtd.1.txt
+++ b/doc/rxvtd.1.txt
@@ -1,68 +1,78 @@
 NAME
-    rxvtd - rxvt terminal daemon
+    urxvtd - urxvt terminal daemon

 SYNOPSIS
-    rxvtd [-q|--quiet] [-o|--opendisplay] [-f|--fork]
+    urxvtd [-q|--quiet] [-o|--opendisplay] [-f|--fork]

 DESCRIPTION
-    This manpage describes the rxvtd daemon, which is the same vt102
-    terminal emulator as rxvt, but runs as a daemon that can open multiple
+    This manpage describes the urxvtd daemon, which is the same vt102
+    terminal emulator as urxvt, but runs as a daemon that can open multiple
     terminal windows within the same process.

     You can run it from your X startup scripts, for example, although it is
     not dependent on a working DISPLAY and, in fact, can open windows on
     multiple X displays on the same time.

-    Advantages of running a rxvt daemon include faster creation time for
+    Advantages of running a urxvt daemon include faster creation time for
     terminal windows and a lot of saved memory.

     The disadvantage is a possible impact on stability - if the main program
     crashes, all processes in the terminal windows are terminated. For
     example, as there is no way to cleanly react to abnormal connection
-    closes, "xkill" and server resets/restarts will kill the rxvtd instance
+    closes, "xkill" and server resets/restarts will kill the urxvtd instance
     including all windows it has opened.

 OPTIONS
-    rxvtd currently understands a few options only. Bundling of options is
+    urxvtd currently understands a few options only. Bundling of options is
     not yet supported.

     -q, --quiet
-        Normally, rxvtd outputs the message "rxvt-unicode daemon listening
+        Normally, urxvtd outputs the message "rxvt-unicode daemon listening
         on " after binding to its control socket. This option will
         suppress this message (errors and warnings will still be logged).

     -o, --opendisplay
-        This forces rxvtd to open a connection to the current $DISPLAY and
+        This forces urxvtd to open a connection to the current $DISPLAY and
         keep it open.

-        This is useful if you want to bind an instance of rxvtd to the
+        This is useful if you want to bind an instance of urxvtd to the
         lifetime of a specific display/server. If the server does a reset,
-        rxvtd will be killed automatically.
+        urxvtd will be killed automatically.

     -f, --fork
-        This makes rxvtd fork after it has bound itself to its control
+        This makes urxvtd fork after it has bound itself to its control
         socket.

 EXAMPLES
-    This is a useful invocation of rxvtd in a .xsession-style script:
+    This is a useful invocation of urxvtd in a .xsession-style script:

-       B -q -f -o
+       B -q -f -o

     This waits till the control socket is available, opens the current
     display and forks into the background. When you log-out, the server is
-    reset and rxvtd is killed.
+    reset and urxvtd is killed.

 ENVIRONMENT
     RXVT_SOCKET
-        Both rxvtc and rxvtd use the environment variable RXVT_SOCKET to
-        create a listening socket and to contact the rxvtd, respectively. If
-        the variable is missing, $HOME/.rxvt-unicode-** is used.
-        The variable must specify the absolute path of the socket to create.
+        Both urxvtc and urxvtd use the environment variable RXVT_SOCKET to
+        create a listening socket and to contact the urxvtd, respectively.
+        If the variable is missing, $HOME/.rxvt-unicode-** is
+        used. The variable must specify the absolute path of the socket to
+        create.

     DISPLAY
         Only used when the "--opendisplay" option is specified. Must contain
         a valid X display name.

 SEE ALSO
-            rxvt(7), rxvtc(1)
+    urxvt(7), urxvtc(1)
+
+POD ERRORS
+    Hey! The above document had some coding errors, which are explained
+    below:
+
+    Around line 87:
+        You forgot a '=back' before '=head1'
+
+        You forgot a '=back' before '=head1'

diff --git a/doc/rxvtperl.3.html b/doc/rxvtperl.3.html

--- a/doc/rxvtperl.3.html
+++ b/doc/rxvtperl.3.html
@@ -371,6 +371,31 @@ kinput2.

    rxvt -pt OnTheSpot -pe xim-onthespot

--- a/doc/rxvtperl.3.man.in
+++ b/doc/rxvtperl.3.man.in
@@ -128,8 +128,8 @@
 .rm #[ #] #H #V #F C
 .\" ========================================================================
 .\"
-.IX Title "rxvt 3"
-.TH rxvt 3 "2006-07-06" "7.7" "RXVT-UNICODE"
+.IX Title "@@RXVT_NAME@@ 3"
+.TH @@RXVT_NAME@@ 3 "2006-07-17" "7.8" "RXVT-UNICODE"
 .SH "NAME"
 @@RXVT_NAME@@perl \- rxvt\-unicode's embedded perl interpreter
 .SH "SYNOPSIS"
@@ -406,6 +406,24 @@ You enable it by specifying this extension and a preedit style of
 .Vb 1
 \&   @@RXVT_NAME@@ \-pt OnTheSpot \-pe xim\-onthespot
 .Ve
+.IP "kuake" 4
+.IX Item "kuake"
+A very primitive quake-console-like extension. It was inspired by a
+description of how the programs \f(CW\*(C`kuake\*(C'\fR and \f(CW\*(C`yakuake\*(C'\fR work: Whenever the
+user presses a global accelerator key (by default \f(CW\*(C`F10\*(C'\fR), the terminal
+will show or hide itself. Another press of the accelerator key will hide
+or show it again.
+.Sp
+Initially, the window will not be shown when using this extension.
+.Sp
+This is useful if you need a single terminal thats not using any desktop
+space most of the time but is quickly available at the press of a key.
+.Sp
+The accelerator key is grabbed regardless of any modifers, so this
+extension will actually grab a physical key just for this function.
+.Sp
+If you want a quake-like animation, tell your window manager to do so
+(fvwm can do it).
 .IP "automove-background" 4
 .IX Item "automove-background"
 This is basically a very small extension that dynamically changes the
@@ -718,6 +736,10 @@ returns \s-1TRUE\s0, setting of the window hints is being skipped.
 Called on every X event received on the vt window (and possibly other
 windows). Should only be used as a last resort. Most event structure
 members are not passed.
+.ie n .IP "on_root_event $term\fR, \f(CW$event" 4
+.el .IP "on_root_event \f(CW$term\fR, \f(CW$event\fR" 4
+.IX Item "on_root_event $term, $event"
+Like \f(CW\*(C`on_x_event\*(C'\fR, but is called for events on the root window.
 .ie n .IP "on_focus_in $term" 4
 .el .IP "on_focus_in \f(CW$term\fR" 4
 .IX Item "on_focus_in $term"
diff --git a/doc/rxvtperl.3.txt b/doc/rxvtperl.3.txt

--- a/doc/rxvtperl.3.txt
+++ b/doc/rxvtperl.3.txt
@@ -237,6 +237,25 @@ PREPACKAGED EXTENSIONS

            rxvt -pt OnTheSpot -pe xim-onthespot

+    kuake
+        A very primitive quake-console-like extension. It was inspired by a
+        description of how the programs "kuake" and "yakuake" work: Whenever
+        the user presses a global accelerator key (by default "F10"), the
+        terminal will show or hide itself. Another press of the accelerator
+        key will hide or show it again.
+
+        Initially, the window will not be shown when using this extension.
+
+        This is useful if you need a single terminal thats not using any
+        desktop space most of the time but is quickly available at the press
+        of a key.
+
+        The accelerator key is grabbed regardless of any modifers, so this
+        extension will actually grab a physical key just for this function.
+
+        If you want a quake-like animation, tell your window manager to do
+        so (fvwm can do it).
+
     automove-background
         This is basically a very small extension that dynamically changes
         the background pixmap offset to the window position, in effect
@@ -518,6 +537,9 @@ API DOCUMENTATION
         other windows). Should only be used as a last resort. Most event
         structure members are not passed.

+    on_root_event $term, $event
+        Like "on_x_event", but is called for events on the root window.
+
     on_focus_in $term
         Called whenever the window gets the keyboard focus, before
         rxvt-unicode does focus in processing.
diff --git a/src/Makefile.in b/src/Makefile.in

--- a/src/Makefile.in
+++ b/src/Makefile.in
@@ -1334,3 +1334,201 @@ 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
+
+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

--- a/src/version.h
+++ b/src/version.h
@@ -1,3 +1,3 @@
 // VERSION _must_ be \d.\d+
-#define VERSION "7.7"
-#define DATE	"2006-02-21"
+#define VERSION "7.8"
+#define DATE	"2006-07-17"