rxvt-unicode, version , is a colour vt102 terminal +
rxvt-unicode, version 7.0, 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 +151,7 @@ Turn on/off jump scrolling; resource jumpScroll.
-+ rxvt -tr -tint blue -sh 40
Please note that you must specify a program with arguments. If you want to +run shell commands, you have to specify the shell, like this:
++ rxvt -e sh -c "shell commands"+
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.
+As an extremely special case, specifying -1 will completely suppress
+pty/tty operations.
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" }
+@@ -533,34 +655,26 @@
Note: `rxvt --help' gives a list of all resources (long options) compiled into your version.
-There are two different methods that rxvt can use to get the -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 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:
+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 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 -/usr/lib/X11/app-defaults/URxvt) and resources set in -~/.Xdefaults, or ~/.Xresources if ~/.Xdefaults does not exist. -Note that when reading X resources, rxvt recognizes two -class names: XTerm 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, notably colours and key-handling, 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 allowed:
+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):
Each font can either be a standard X11 core font (XLFD) name, with @@ -819,6 +941,16 @@ text font will being used for the given style.
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.
LC_CTYPE of e.g.
de_DE.UTF-8 for normal text processing but ja_JP.EUC-JP for the
input extension to be able to input japanese characters while staying in
-another locale. option -imlocale.
+another locale; option -imlocale.
write(1) or any other means. Therefore, these sequences are disabled by
+default. (Note that many other terminals, including xterm, have these
+sequences enabled by default, which doesn't make it safer, though).
+
+You can enable them by setting this boolean resource or specifying +-insecure as an option. At the moment, this enables display-answer, +locale, findfont, icon label and window title requests as well as dynamic +menubar dispatch.
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).
Please note that you need to double the \ in resource files, as
+Xlib 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 @@ -1221,6 +1389,40 @@ URxvt.keysym.M-C-c: command:\033]701;zh_CN.GBK\007
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:
+ URxvt.keysym.M-C-c: perl:selection:rot13+
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:
list(s) of perl extension scripts (default: default) to
+use in this terminal instance; option -pe.
+Extension names can be prefixed with a - sign to prohibit using
+them. This can be useful to selectively disable some extensions loaded
+by default, or specified via the perl-ext-common resource. For
+example, default,-selection will use all the default extension except
+selection.
Extension names can also be followed by an argument in angle brackets
+(e.g. searchable-scrollback<M-s>, which binds the hotkey for
+searchable scorllback to Alt/Meta-s). Mentioning the same extension
+multiple times with different arguments will pass multiple arguments to
+the extension.
Each extension is looked up in the library directories, loaded if +necessary, and bound to the current terminal instance.
+If both of these resources are the empty string, then the perl +interpreter will not be initialized. The idea behind two options is that +perl-ext-common will be used for extensions that should be available to +all instances, while perl-ext is used for specific instances.
+rxvtperl(3) manpage. Due to security reasons, this resource
+will be ignored when running setuid/setgid.
+perl resource,
+rxvt will first look in these directories and then in
+/opt/rxvt/lib/urxvt/perl/. Due to security reasons, this resource
+will be ignored when running setuid/setgid.
+See the rxvtperl(3) manpage.
selection-popup and mark-urls perl extensions.
+@@ -1283,8 +1552,10 @@
Starting a selection while pressing the Meta key (or Meta+Ctrl keys) -(Compile: frills) will create a rectangular selection instead of a normal -one.
+(Compile: frills) will create a rectangular selection instead of a +normal one. In this mode, every selected row becomes its own line in the +selection, and trailing whitespace is visually underlined and removed from +the selection.You can, however, switch fonts at runtime using escape sequences (and therefore using the menubar), e.g.:
- printf '\e]701;%s\007' "9x15bold,xft:Kochi Gothic"+ printf '\e]710;%s\007' "9x15bold,xft:Kochi Gothic"
rxvt-unicode will automatically re-apply these fonts to the output so far.
@@ -1495,7 +1766,7 @@ rxvtd(1).
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)
-
-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)