[ViewVC] Diff of: cvs/rxvt-unicode/doc/rxvt.1.pod

Comparing rxvt-unicode/doc/rxvt.1.pod (file contents):
Revision 1.58 by root, Wed Feb 16 21:49:36 2005 UTC vs.
Revision 1.66 by root, Thu Jun 30 14:02:17 2005 UTC

 Put scrollbar on right/left; resource B<scrollBar_right>.
 =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>
 If enabled (default), "Horizontal Tab" characters are being stored as
 =item B<-ssr>|B<+ssr>
 Turn on/off secondary screen scroll (default enabled); resource
 B<secondaryScroll>.
-=item B<-keysym.>I<sym>: I<string>
+=item B<-keysym.>I<sym> I<string>
 Remap a key symbol. See resource B<keysym>.
-=item B<-embed>: I<windowid>
+=item B<-embed> I<windowid>
 Tells @@RXVT_NAME@@ to embed it's windows into an already-existing window,
 which enables applications to easily embed a terminal.
 Right now, @@RXVT_NAME@@ will first unmap/map the specified window, so it
 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 C<-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 F<doc/embed>):
+   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>
+Tells @@RXVT_NAME@@ 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_NAME@@ as a generic terminal emulator
+without having to run a program within it.
+If this switch is given, @@RXVT_NAME@@ 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.
+Here is a example in perl that illustrates how this option can be used (a
+longer example is in F<doc/pty-fd>):
+   use IO::Pty;
+   use Fcntl;
+   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;
+   while (<$slave>) { print $slave "got <$_>\n" }
 =back
 =head1 RESOURCES (available also as long-options)
 Use the specified colour for the scrollbar [default #B2B2B2].
 =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>
 The colour of the border around the text area and between the scrollbar
 and the text.
 xterm style selection.
 =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>
 Set window title string, the default title is the command-line
 specified after the B<-e> option, if any, otherwise the application
 =item B<print-pipe:> I<string>
 Specify a command pipe for vt100 printer [default I<lpr(1)>]. Use
 B<Print> to initiate a screen dump to the printer and B<Ctrl-Print> or
 B<Shift-Print> to include the scrollback as well.
+The string will be interpreted as if typed into the shell as-is.
+Example:
+   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 C<Print>.
 =item B<scrollBar:> I<boolean>
 B<True>: enable the scrollbar [default]; option B<-sb>. B<False>:
 disable the scrollbar; option B<+sb>.
 Mouse pointer background colour.
 =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>
 The string to send when the backspace key is pressed. If set to B<DEC>
 or unset it will send B<Delete> (code 127) or, if shifted, B<Backspace>
 is interpreted and executed as @@RXVT_NAME@@'s control sequence. For
 example the following means "change the current locale to C<zh_CN.GBK>
 when Control-Meta-c is being pressed":
   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:

Diff Legend

-–
+Removed lines
-+
+Added lines
-<
+Changed lines
->
+Changed lines

Comparing rxvt-unicode/doc/rxvt.1.pod (file contents): Revision 1.58 by root, Wed Feb 16 21:49:36 2005 UTC vs. Revision 1.66 by root, Thu Jun 30 14:02:17 2005 UTC

Diff Legend

Comparing rxvt-unicode/doc/rxvt.1.pod (file contents):
Revision 1.58 by root, Wed Feb 16 21:49:36 2005 UTC vs.
Revision 1.66 by root, Thu Jun 30 14:02:17 2005 UTC