rxvt-unicode, version 4.9, 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 -- @@ -58,8 +57,10 @@
See rxvt(7) (try man 7 rxvt) for a list of frequently
-asked questions and answer to them and some common problems.
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.
+ 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" }
@@ -529,8 +613,16 @@ Xresource data: using the X libraries (Xrm*-functions) or internal Xresources reader (~/.Xdefaults). For the first method (ie. rxvt -h lists XGetDefaults), you can set and change the -resources using X11 tools like xset. Many distribution do also load -settings from the ~/.Xresources file when X starts.
+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 later settings +overwriting earlier ones: ++ 1. system-wide app-defaults file, either locale-dependent OR global + 2. app-defaults file in $XAPPLRESDIR + 3. RESOURCE_MANAGER property on root-window OR $HOME/.Xdefaults + 4. SCREEN_RESOURCES for the current screen + 5. $XENVIRONMENT file OR $HOME/.Xdefaults-<nodename>
If compiled with internal Xresources support (i.e. rxvt -h lists .Xdefaults) then rxvt accepts application defaults set in XAPPLOADDIR/URxvt (compile-time defined: usually @@ -659,13 +751,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.
Please note that you need to double the \ when using
+--enable-xgetdefault, as X itself does it's own de-escaping (you can
+use \033 instead of \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 `/' should be a character not used by the strings.
@@ -1177,40 +1298,69 @@- URxvt.keysym.M-C-0x61: list|\e<M-C-|abc|>+ URxvt.keysym.M-C-0x61: list|\033<M-C-|abc|>
The above line is equivalent to the following three lines:
- URxvt.keysym.Meta-Control-0x61: \e<M-C-a> - URxvt.keysym.Meta-Control-0x62: \e<M-C-b> - URxvt.keysym.Meta-Control-0x63: \e<M-C-c>+ URxvt.keysym.Meta-Control-0x61: \033<M-C-a> + URxvt.keysym.Meta-Control-0x62: \033<M-C-b> + URxvt.keysym.Meta-Control-0x63: \033<M-C-c>
If string takes the form of proto:STRING, the specified STRING
+
If string takes the form of command:STRING, the specified STRING
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'':
- URxvt.keysym.M-C-c: proto:\033]701;zh_CN.GBK\007+ 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 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 cna have some limited
+the fonts suxuseuro and 9x15bold, so you can have some limited
font-switching at runtime:
- URxvt.keysym.M-C-1: proto:\033]50;suxuseuro\007 - URxvt.keysym.M-C-2: proto:\033]50;9x15bold\007+ URxvt.keysym.M-C-1: command:\033]50;suxuseuro\007 + URxvt.keysym.M-C-2: command:\033]50;9x15bold\007
proto:\033]701;zh_CN.GBK\007 means: change the current locale to
-zh_CN.GBK.
Other things are possible, e.g. resizing (see rxvt(7) for more
+info):
+ URxvt.keysym.M-C-3: command:\033[8;25;80t + URxvt.keysym.M-C-4: command:\033[8;48;110t
@@ -1234,9 +1384,9 @@ (Alt) key while performing the desired mouse action.
If mouse reporting mode is active, the normal scrollbar actions are disabled -- on the assumption that we are using a fullscreen -application. Instead, pressing Button1 and Button3 sends ESC[6~ -(Next) and ESC[5~ (Prior), respectively. Similarly, clicking on the -up and down arrows sends ESC[A (Up) and ESC[B (Down), +application. Instead, pressing Button1 and Button3 sends ESC [ 6 ~ +(Next) and ESC [ 5 ~ (Prior), respectively. Similarly, clicking on the +up and down arrows sends ESC [ A (Up) and ESC [ B (Down), respectively.
@@ -1391,12 +1541,107 @@
rxvt sets the environment variables TERM, COLORTERM -and COLORFGBG. The environment variable WINDOWID is set to the X -window id number of the rxvt window and it also uses and -sets the environment variable DISPLAY to specify which display -terminal to use. rxvt uses the environment variables -RXVTPATH and PATH to find XPM files.
+rxvt sets and/or uses the following environment variables:
+rxvt-unicode, unless overwritten at configure time, via
+resources or on the commandline.
+rxvt, rxvt-xpm, depending on wether rxvt was
+compiled with XPM support, and optionally with the added extension
+-mono to indicate that rxvt-unicode runs on a monochrome screen.
+fg;bg or fg;xpm;bg, where fg is
+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 rxvt
+was compiled with XPM support. Libraries like ncurses and slang can
+(and do) use this information to optimize screen output.
+--with-terminfo=PATH.
+/bin/sh.
+RXVTPATH.
+rxvtc(1) and
+rxvtd(1).
+Default $HOME/.rxvt-unicode-<nodename >>>.
+.Xdefaults)
+
rxvt(7), xterm(1), sh(1), resize(1), X(1), pty(4), tty(4), utmp(5)
-
-Check the BUGS file for an up-to-date list.
-Cursor change support is not yet implemented.
-Click-and-drag doesn't work with X11 mouse report overriding.
+rxvt(7), rxvtc(1), rxvtd(1), xterm(1), sh(1), resize(1), X(1), pty(4), tty(4), utmp(5)
@@ -1485,7 +1717,7 @@ (changes.txt 2.4.6 - rxvt-unicode)
-