--- rxvt-unicode/doc/rxvt.1.html 2005/02/11 18:14:07 1.11 +++ rxvt-unicode/doc/rxvt.1.html 2005/10/25 20:04:58 1.24 @@ -49,7 +49,7 @@
rxvt-unicode, version 5.0, is a colour vt102 terminal +
rxvt-unicode, version 5.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 -- @@ -152,7 +152,7 @@ Turn on/off jump scrolling; resource jumpScroll.
-+ rxvt -tr -tint blue -sh 40
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 rxvt 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.
Here is a short Gtk2-perl snippet that illustrates how this option can be +used (a longer example is in doc/embed):
++ my $rxvt = new Gtk2::Socket; + $rxvt->signal_connect_after (realize => sub { + my $xid = $_[0]->window->get_xid; + system "rxvt -embed $xid &"; + });+
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.
+Here is a example in perl that illustrates how this option can be used (a +longer example is in doc/pty-fd):
++ use IO::Pty; + use Fcntl;+
+ my $pty = new IO::Pty; + fcntl $pty, F_SETFD, 0; # clear close-on-exec + system "rxvt -pty-fd " . (fileno $pty) . "&"; + close $pty;+
+ # now communicate with rxvt + my $slave = $pty->slave; + while (<$slave>) { print $slave "got <$_>\n" }
@@ -675,13 +752,21 @@
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 Print
.
987654321
) to effectively disable the timeout.
Due the the large number of modifier combinations, a defined key mapping
+will match if at 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 a
will automatically provide
+definitions for Meta-a
, 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 Insert
key you will disable rxvt's
+Shift-Insert
mapping. To re-enable that, you can poke ``holes'' into the
+user-defined keymap using the builtin:
replacement:
+ URxvt.keysym.Insert: <my insert key sequence> + URxvt.keysym.S-Insert: builtin:+
The first line defines a mapping for Insert
and any combination
+of modifiers. The second line re-establishes the default mapping for
+Shift-Insert
.
The following example will map Control-Meta-1 and Control-Meta-2 to
the fonts suxuseuro
and 9x15bold
, so you can have some limited
font-switching at runtime:
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 slang
can (and do) use
-this information to optimize screen output.
+was compiled with XPM support. Libraries like ncurses
and slang
can
+(and do) use this information to optimize screen output.
Default $HOME/.rxvt-unicode-<nodename
.
Default $HOME/.rxvt-unicode-<nodename >>>.
rxvt(7), 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)
@@ -1601,7 +1725,7 @@ (changes.txt 2.4.6 - rxvt-unicode)
-