--- rxvt-unicode/doc/rxvt.1.pod	2005/02/17 15:07:48	1.59
+++ rxvt-unicode/doc/rxvt.1.pod	2005/06/17 12:05:31	1.64
@@ -240,7 +240,7 @@
 
 =item B<-st>|B<+st>
 
-Display normal (non XTerm/NeXT) scrollbar without/with a trough;
+Display rxvt (non XTerm/NeXT) scrollbar without/with a trough;
 resource B<scrollBar_floating>.
 
 =item B<-ptab>|B<+ptab>
@@ -395,12 +395,11 @@
 Here is a short Gtk2-perl snippet that illustrates how this option can be
 used (a longer example is in F<doc/embed>):
 
-   my $rxvt = new Gtk2::DrawingArea;
-   $...->add ($rxvt); # important to add it somewhere first
-   $rxvt->realize; # now it can be realized
-   my $xid = $rxvt->window->get_xid;
-
-   system "@@RXVT_NAME@@ -embed $xid &";
+   my $rxvt = new Gtk2::Socket;
+   $rxvt->signal_connect_after (realize => sub {
+      my $xid = $_[0]->window->get_xid;
+      system "@@RXVT_NAME@@ -embed $xid &";
+   });
 
 =item B<-pty-fd> I<fileno>
 
@@ -421,8 +420,8 @@
 
    my $pty = new IO::Pty;
    fcntl $pty, F_SETFD, 0; # clear close-on-exec
-
    system "@@RXVT_NAME@@ -pty-fd " . (fileno $pty) . "&";
+   close $pty;
 
    # now communicate with rxvt
    my $slave = $pty->slave;
@@ -569,7 +568,7 @@
 =item B<troughColor:> I<colour>
 
 Use the specified colour for the scrollbar's trough area [default
-#969696]. Only relevant for normal (non XTerm/NeXT) scrollbar.
+#969696]. Only relevant for rxvt (non XTerm/NeXT) scrollbar.
 
 =item B<borderColor:> I<colour>
 
@@ -671,7 +670,7 @@
 =item B<scrollstyle:> I<mode>
 
 Set scrollbar style to B<rxvt>, B<plain>, B<next> or B<xterm>. B<plain> is
-the author's favourite..
+the author's favourite.
 
 =item B<title:> I<string>
 
@@ -818,7 +817,8 @@
 
 =item B<pointerBlankDelay:> I<number>
 
-Specifies number of seconds before blanking the pointer [default 2].
+Specifies number of seconds before blanking the pointer [default 2]. Use a
+large number (e.g. C<987654321>) to effectively disable the timeout.
 
 =item B<backspacekey:> I<string>
 
@@ -960,6 +960,25 @@
 
   URxvt.keysym.M-C-c: command:\033]701;zh_CN.GBK\007
 
+Due the the large number of modifier combinations, a defined key mapping
+will match if at I<at least> the specified identifiers are being set, and
+no other key mappings with those and more bits are being defined. That
+means that defining a key map for C<a> will automatically provide
+definitions for C<Meta-a>, C<Shift-a> and so on, unless some of those are defined
+mappings themselves.
+
+Unfortunately, this will override built-in key mappings. For example
+if you overwrite the C<Insert> key you will disable @@RXVT_NAME@@'s
+C<Shift-Insert> mapping. To re-enable that, you can poke "holes" into the
+user-defined keymap using the C<builtin:> replacement:
+
+  URxvt.keysym.Insert: <my insert key sequence>
+  URxvt.keysym.S-Insert: builtin:
+
+The first line defines a mapping for C<Insert> and I<any> combination
+of modifiers. The second line re-establishes the default mapping for
+C<Shift-Insert>.
+
 The following example will map Control-Meta-1 and Control-Meta-2 to
 the fonts C<suxuseuro> and C<9x15bold>, so you can have some limited
 font-switching at runtime: