RXVT REFERENCE - FAQ, command sequences and other background information
# set a new font set printf '\33]50;%s\007' 9x15,xft:Kochi" Mincho"
# change the locale and tell rxvt-unicode about it export LC_CTYPE=ja_JP.EUC-JP; printf "\33]701;$LC_CTYPE\007"
# set window title printf '\33]2;%s\007' "new window title"
This document contains the FAQ, the RXVT TECHNICAL REFERENCE documenting all escape sequences, and other background information.
The newest version of this document is also available on the World Wide Web at http://cvs.schmorp.de/browse/*checkout*/rxvt-unicode/doc/rxvt.7.html.
ESC [ 8 n sets the window title to the version number.
reportbug to report the bug).
For other problems that also affect the Debian package, you can and probably should use the Debian BTS, too, because, after all, it's also a bug in the Debian version and it serves as a reminder for other users that might encounter the same issue.
The correct solution for this problem is to install the terminfo, this can be done like this (with ncurses' infocmp):
REMOTE=remotesystem.domain infocmp rxvt-unicode | ssh $REMOTE "cat >/tmp/ti && tic /tmp/ti"
... or by installing rxvt-unicode normally on the remote system,
If you cannot or do not want to do this, then you can simply set
TERM=rxvt or even TERM=xterm, and live with the small number of
problems arising, which includes wrong keymapping, less and different
colours and some refresh errors in fullscreen applications. It's a nice
quick-and-dirty workaround for rare cases, though.
If you always want to do this (and are fine with the consequences) you can either recompile rxvt-unicode with the desired TERM value or use a resource to set it:
URxvt.termName: rxvt
If you don't plan to use rxvt (quite common...) you could also replace the rxvt terminfo file with the rxvt-unicode one.
bash's readline does not work correctly under rxvt.rxvt-unicode.
You could use rxvt's termcap entry with resonable results in many cases. You can also create a termcap entry by using terminfo's infocmp program like this:
infocmp -C rxvt-unicode
Or you could use this termcap entry, generated by the command above:
rxvt-unicode|rxvt-unicode terminal (X Window System):\
:am:bw:eo:km:mi:ms:xn:xo:\
:co#80:it#8:li#24:lm#0:\
:AL=\E[%dL:DC=\E[%dP:DL=\E[%dM:DO=\E[%dB:IC=\E[%d@:\
:K1=\EOw:K2=\EOu:K3=\EOy:K4=\EOq:K5=\EOs:LE=\E[%dD:\
:RI=\E[%dC:SF=\E[%dS:SR=\E[%dT:UP=\E[%dA:ae=\E(B:al=\E[L:\
:as=\E(0:bl=^G:cd=\E[J:ce=\E[K:cl=\E[H\E[2J:\
:cm=\E[%i%d;%dH:cr=^M:cs=\E[%i%d;%dr:ct=\E[3g:dc=\E[P:\
:dl=\E[M:do=^J:ec=\E[%dX:ei=\E[4l:ho=\E[H:\
:i1=\E[?47l\E=\E[?1l:ic=\E[@:im=\E[4h:\
:is=\E[r\E[m\E[2J\E[H\E[?7h\E[?1;3;4;6l\E[4l:\
:k1=\E[11~:k2=\E[12~:k3=\E[13~:k4=\E[14~:k5=\E[15~:\
:k6=\E[17~:k7=\E[18~:k8=\E[19~:k9=\E[20~:kD=\E[3~:\
:kI=\E[2~:kN=\E[6~:kP=\E[5~:kb=\177:kd=\EOB:ke=\E[?1l\E>:\
:kh=\E[7~:kl=\EOD:kr=\EOC:ks=\E[?1h\E=:ku=\EOA:le=^H:\
:mb=\E[5m:md=\E[1m:me=\E[m\017:mr=\E[7m:nd=\E[C:rc=\E8:\
:sc=\E7:se=\E[27m:sf=^J:so=\E[7m:sr=\EM:st=\EH:ta=^I:\
:te=\E[r\E[?1049l:ti=\E[?1049h:ue=\E[24m:up=\E[A:\
:us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\
:vs=\E[?25h:
ls no longer have coloured output?ls in the GNU coreutils unfortunately doesn't use terminfo to
decide wether a terminal has colour, but uses it's own configuration
file. Needless to say, rxvt-unicode is not in it's default file (among
with most other terminals supporting colour). Either add:
TERM rxvt-unicode
to /etc/DIR_COLORS or simply add:
alias ls='ls --color=auto'
to your .profile or .bashrc.
TERM=rxvt-unicode. Some pre-packaged
distributions (most notably Debian GNU/Linux) break rxvt-unicode
by setting TERM to rxvt, which doesn't have these extra
features. Unfortunately, some of these (most notably, again, Debian
GNU/Linux) furthermore fail to even install the rxvt-unicode terminfo
file, so you will need to install it on your own (See the question When
I log-in to another system it tells me about missing terminfo data? on
how to do this).
TERM setting, although the details of wether and how
this can happen are unknown, as TERM=rxvt should offer a compatible
keymap. See the answer to the previous question, and please report if that
helped.
Rxvt-unicode must be started with the same LC_CTYPE setting as the
programs. Often rxvt-unicode is started in the C locale, while the
login script running within the rxvt-unicode window changes the locale to
something else, e.g. en_GB.UTF-8. Needless to say, this is not going to work.
The best thing is to fix your startup environment, as you will likely run into other problems. If nothing works you can try this in your .profile.
printf '\e]701;%s\007' "$LC_CTYPE"
If this doesn't work, then maybe you use a LC_CTYPE specification not
supported on your systems. Some systems have a locale command which
displays this (also, perl -e0 can be used to check locale settings, as
it will complain loudly if it cannot set the locale). If it displays something
like:
locale: Cannot set LC_CTYPE to default locale: ...
Then the locale you specified is not supported on your system.
If nothing works and you are sure that everything is set correctly then you will need to remember a little known fact: Some programs just don't support locales :(
rxvt-unicode makes a best-effort try at finding a replacement font. Often the result is fine, but sometimes the chosen font looks bad/ugly/wrong. Some fonts have totally strange characters that don't resemble the correct glyph at all, and rxvt-unicode lacks the artificial intelligence to detect that a specific glyph is wrong: it has to believe the font that the characters it claims to contain indeed look correct.
In that case, select a font of your taste and add it to the font list, e.g.:
rxvt -fn basefont,font2,font3...
When rxvt-unicode sees a character, it will first look at the base font. If the base font does not contain the character, it will go to the next font, and so on. Specifying your own fonts will also speed up this search and use less resources within rxvt-unicode and the X-server.
The only limitation is that none of the fonts may be larger than the base font, as the base font defines the terminal character cell size, which must be the same due to the way terminals work.
The workaround is easy: just tag a chinese font at the end of your font list (see the previous question). The key is to view the font list as a preference list: If you expect more japanese, list a japanese font first. If you expect more chinese, put a chinese font first.
In the future it might be possible to switch language preferences at runtime (the internal data structure has no problem with using different fonts for the same character at the same time, but no interface for this has been designed yet).
Until then, you might get away with switching fonts at runtime (see Can I switch the fonts at runtime? later in this document).
All of this requires that fonts do not lie about character sizes, however: Xft fonts often draw glyphs larger than their acclaimed bounding box, and rxvt-unicode has no way of detecting this (the correct way is to ask for the character bounding box, which unfortunately is wrong in these cases).
It's not clear (to me at least), wether this is a bug in Xft, freetype,
or the respective font. If you encounter this problem you might try using
the -lsp option to give the font more height. If that doesn't work, you
might be forced to use a different font.
All of this is not a problem when using X11 core fonts, as their bounding box data is correct.
In this case either do not specify a preeditStyle or specify more than one pre-edit style, such as OverTheSpot,Root,None.
Ctrl-Shift-2 to get an ASCII NUL character due to ISO 14755Ctrl-2 alone (it often is mapped to ASCII NUL even on
international keyboards) or simply use ISO 14755 support to your
advantage, typing <Ctrl-Shift-0> to get a ASCII NUL. This works for other
codes, too, such as Ctrl-Shift-1-d to type the default telnet escape
character and so on.
TERM=rxvt-unicode), which will get rid of most of these effects. Then
make sure you have specified colours for italic and bold, as otherwise
rxvt-unicode might use reverse video to simulate the effect:
URxvt.colorBD: white URxvt.colorIT: green
In the meantime, you can either edit your rxvt-unicode terminfo
definition to only claim 8 colour support or use TERM=rxvt, which will
fix colours but keep you from using other rxvt-unicode features.
__STDC_ISO_10646__ to be defined
in your compile environment, or an implementation that implements it,
wether it defines the symbol or not. __STDC_ISO_10646__ requires that
wchar_t is represented as unicode.
As you might have guessed, FreeBSD does neither define this symobl nor does it support it. Instead, it uses it's own internal representation of wchar_t. This is, of course, completely fine with respect to standards.
However, __STDC_ISO_10646__ is the only sane way to support
multi-language apps in an OS, as using a locale-dependent (and
non-standardized) representation of wchar_t makes it impossible to
convert between wchar_t (as used by X11 and your applications) and any
other encoding without implementing OS-specific-wrappers for each and
every locale. There simply are no APIs to convert wchar_t into anything
except the current locale encoding.
Some applications (such as the formidable mlterm) work around this by carrying their own replacement functions for character set handling with them, and either implementing OS-dependent hacks or doing multiple conversions (which is slow and unreliable in case the OS implements encodings slightly different than the terminal emulator).
The rxvt-unicode author insists that the right way to fix this is in the system libraries once and for all, instead of forcing every app to carry complete replacements for them :)
The reasons is that there exists a perfectly fine mechanism for selecting
the encoding, doing I/O and (most important) communicating this to all
applications so everybody agrees on character properties such as width
and code number. This mechanism is the locale. Applications not using
that info will have problems (for example, xterm gets the width of
characters wrong as it uses it's own, locale-independent table under all
locales).
Rxvt-unicode uses the LC_CTYPE locale category to select encoding. All
programs doing the same (that is, most) will automatically agree in the
interpretation of characters.
Unfortunately, there is no system-independent way to select locales, nor is there a standard on how locale specifiers will look like.
On most systems, the content of the LC_CTYPE environment variable
contains an arbitrary string which corresponds to an already-installed
locale. Common names for locales are en_US.UTF-8, de_DE.ISO-8859-15,
ja_JP.EUC-JP, i.e. language_country.encoding, but other forms
(i.e. de or german) are also common.
Rxvt-unicode ignores all other locale categories, and except for
the encoding, ignores country or language-specific settings,
i.e. de_DE.UTF-8 and ja_JP.UTF-8 are the normally same to
rxvt-unicode.
If you want to use a specific encoding you have to make sure you start
rxvt-unicode with the correct LC_CTYPE category.
LC_CTYPE.
printf '\e]701;%s\007' ja_JP.SJIS
See also the previous answer.
Sometimes this capability is rather handy when you want to work in
one locale (e.g. de_DE.UTF-8) but some programs don't support it
(e.g. UTF-8). For example, I use this script to start xjdic, which
first switches to a locale supported by xjdic and back later:
printf '\e]701;%s\007' ja_JP.SJIS xjdic -js printf '\e]701;%s\007' de_DE.UTF-8
You can also use xterm's luit program, which usually works fine, except
for some locales where character width differs between program- and
rxvt-unicode-locales.
-fn switch, and takes effect immediately:
printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic"
This is useful if you e.g. work primarily with japanese (and prefer a japanese font), but you have to switch to chinese temporarily, where japanese fonts would only be in your way.
You can think of this as a kind of manual ISO-2022 switching.
xft:Bitstream Vera Sans
Mono completely fails in it's italic face. A workaround might be to
enable freetype autohinting, i.e. like this:
URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true
imlocale:
URxvt*imlocale: ja_JP.EUC-JP
Now you can start your terminal with LC_CTYPE=ja_JP.UTF-8 and still
use your input method. Please note, however, that you will not be able to
input characters outside EUC-JP in a normal way then, as your input
method limits you.
So the only workaround is not to kill your Input Method Servers.
Also, many people (me included) like large windows and even larger
scrollback buffers: Without --enable-unicode3, rxvt-unicode will use
6 bytes per screen cell. For a 160x?? window this amounts to almost a
kilobyte per line. A scrollback buffer of 10000 lines will then (if full)
use 10 Megabytes of memory. With --enable-unicode3 it gets worse, as
rxvt-unicode then uses 8 bytes per screen cell.
:antialiasing=false), which saves lots of
memory and also speeds up rendering considerably.
If you want antialiasing, you have to specify the fonts manually.
rxvt(7)
colorBD:, bold will invert text using the
standard foreground colour.
For the standard background colour, blinking will actually make the
text blink when compiled with --enable-blinking. with standard
colours. Without --enable-blinking, the blink attribute will be
ignored.
On ANSI colours, bold/blink attributes are used to set high-intensity foreground/background colors.
color0-7 are the low-intensity colors.
color8-15 are the corresponding high-intensity colors.
Here are values that are supposed to resemble a VGA screen, including the murky brown that passes for low-intensity yellow:
URxvt.color0: #000000 URxvt.color1: #A80000 URxvt.color2: #00A800 URxvt.color3: #A8A800 URxvt.color4: #0000A8 URxvt.color5: #A800A8 URxvt.color6: #00A8A8 URxvt.color7: #A8A8A8
URxvt.color8: #000054 URxvt.color9: #FF0054 URxvt.color10: #00FF54 URxvt.color11: #FFFF54 URxvt.color12: #0000FF URxvt.color13: #FF00FF URxvt.color14: #00FFFF URxvt.color15: #FFFFFF
And here is a more complete set of non-standard colors described (not by me) as ``pretty girly''.
URxvt.cursorColor: #dc74d1 URxvt.pointerColor: #dc74d1 URxvt.background: #0e0e0e URxvt.foreground: #4ad5e1 URxvt.color0: #000000 URxvt.color8: #8b8f93 URxvt.color1: #dc74d1 URxvt.color9: #dc74d1 URxvt.color2: #0eb8c7 URxvt.color10: #0eb8c7 URxvt.color3: #dfe37e URxvt.color11: #dfe37e URxvt.color5: #9e88f0 URxvt.color13: #9e88f0 URxvt.color6: #73f7ff URxvt.color14: #73f7ff URxvt.color7: #e1dddd URxvt.color15: #e1dddd
To ensure rxvtd is listening on it's socket, you can use the following method to wait for the startup message before continuing:
{ rxvtd & } | read
^H and ^?.
Historically, either value is correct, but rxvt-unicode adopts the debian
policy of using ^? when unsure, because it's the one only only correct
choice :).
Rxvt-unicode tries to inherit the current stty settings and uses the value of `erase' to guess the value for backspace. If rxvt-unicode wasn't started from a terminal (say, from a menu or by remote shell), then the system value of `erase', which corresponds to CERASE in <termios.h>, will be used (which may not be the same as your stty setting).
For starting a new rxvt-unicode:
# use Backspace = ^H $ stty erase ^H $ rxvt
# use Backspace = ^? $ stty erase ^? $ rxvt
Toggle with ESC [ 36 h / ESC [ 36 l as documented in rxvt(7).
For an existing rxvt-unicode:
# use Backspace = ^H $ stty erase ^H $ echo -n "^[[36h"
# use Backspace = ^? $ stty erase ^? $ echo -n "^[[36l"
This helps satisfy some of the Backspace discrepancies that occur, but
if you use Backspace = ^H, make sure that the termcap/terminfo value
properly reflects that.
The Delete key is a another casualty of the ill-defined Backspace problem.
To avoid confusion between the Backspace and Delete keys, the Delete
key has been assigned an escape sequence to match the vt100 for Execute
(ESC [ 3 ~) and is in the supplied termcap/terminfo.
Some other Backspace problems:
some editors use termcap/terminfo, some editors (vim I'm told) expect Backspace = ^H, GNU Emacs (and Emacs-like editors) use ^H for help.
Perhaps someday this will all be resolved in a consistent manner.
--disable-resources option you can
use the `keysym' resource to alter the keystrings associated with keysyms.
Here's an example for a URxvt session started using rxvt -name URxvt
URxvt.keysym.Home: \033[1~ URxvt.keysym.End: \033[4~ URxvt.keysym.C-apostrophe: \033<C-'> URxvt.keysym.C-slash: \033<C-/> URxvt.keysym.C-semicolon: \033<C-;> URxvt.keysym.C-grave: \033<C-`> URxvt.keysym.C-comma: \033<C-,> URxvt.keysym.C-period: \033<C-.> URxvt.keysym.C-0x60: \033<C-`> URxvt.keysym.C-Tab: \033<C-Tab> URxvt.keysym.C-Return: \033<C-Return> URxvt.keysym.S-Return: \033<S-Return> URxvt.keysym.S-space: \033<S-Space> URxvt.keysym.M-Up: \033<M-Up> URxvt.keysym.M-Down: \033<M-Down> URxvt.keysym.M-Left: \033<M-Left> URxvt.keysym.M-Right: \033<M-Right> URxvt.keysym.M-C-0: list \033<M-C- 0123456789 > URxvt.keysym.M-C-a: list \033<M-C- abcdefghijklmnopqrstuvwxyz > URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007
See some more examples in the documentation for the keysym resource.
KP_Insert == Insert F22 == Print F27 == Home F29 == Prior F33 == End F35 == Next
Rather than have rxvt-unicode try to accommodate all the various possible keyboard mappings, it is better to use `xmodmap' to remap the keys as required for your particular machine.
Courtesy of Chuck Blake <cblake@BBN.COM> with the following shell script snippets:
# Bourne/Korn/POSIX family of shells:
[ ${TERM:-foo} = foo ] && TERM=xterm # assume an xterm if we don't know
if [ ${TERM:-foo} = xterm ]; then
stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not
echo -n '^[Z'
read term_id
stty icanon echo
if [ ""${term_id} = '^[[?1;2C' -a ${DISPLAY:-foo} = foo ]; then
echo -n '^[[7n' # query the rxvt we are in for the DISPLAY string
read DISPLAY # set it in our local shell
fi
fi
make alldoc.
irc.freenode.net,
channel #rxvt-unicode has some rxvt-unicode enthusiasts that might be
interested in learning about new and exciting problems (but not FAQs :).
The rest of this document describes various technical aspects of
rxvt-unicode. First the description of supported command sequences,
followed by menu and pixmap support and last by a description of all
features selectable at configure time.
c >C >Ps >Pm >; character(s).
Pt >
ENQ >ESC [ Ps c >.
BEL >BS >TAB >LF >VT >LF >
FF >LF >
CR >SO >SI >SPC >
ESC # 8 >ESC 7 >ESC 8 >ESC = >ESC >>Note: If the numeric keypad is activated, eg, Num_Lock has been pressed, numbers or control functions are generated by the numeric keypad (see Key Codes).
ESC D >ESC E >ESC H >ESC M >ESC N >ESC O >ESC Z >ESC [ ? 1 ; 2 C > rxvt-unicode compile-time option
ESC c >ESC n >ESC o >ESC ( C >C.
ESC ) C >C.
ESC * C >C.
ESC + C >C.
ESC $ C >Where C > is one of:
| C = 0 | DEC Special Character and Line Drawing Set |
| C = A | United Kingdom (UK) |
| C = B | United States (USASCII) |
| C = < | Multinational character set unimplemented |
| C = 5 | Finnish character set unimplemented |
| C = C | Finnish character set unimplemented |
| C = K | German character set unimplemented |
ESC [ Ps @ >Ps > (Blank) Character(s) [default: 1] (ICH)
ESC [ Ps A >Ps > Times [default: 1] (CUU)
ESC [ Ps B >Ps > Times [default: 1] (CUD)
ESC [ Ps C >Ps > Times [default: 1] (CUF)
ESC [ Ps D >Ps > Times [default: 1] (CUB)
ESC [ Ps E >Ps > Times [default: 1] and to first column
ESC [ Ps F >Ps > Times [default: 1] and to first column
ESC [ Ps G >Ps > (HPA)
ESC [ Ps;Ps H >ESC [ Ps I >Ps > tab stops [default: 1]
ESC [ Ps J >| Ps = 0 | Clear Below (default) |
| Ps = 1 | Clear Above |
| Ps = 2 | Clear All |
ESC [ Ps K >| Ps = 0 | Clear to Right (default) |
| Ps = 1 | Clear to Left |
| Ps = 2 | Clear All |
ESC [ Ps L >Ps > Line(s) [default: 1] (IL)
ESC [ Ps M >Ps > Line(s) [default: 1] (DL)
ESC [ Ps P >Ps > Character(s) [default: 1] (DCH)
ESC [ Ps;Ps;Ps;Ps;Ps T >ESC [ Ps W >| Ps = 0 | Tab Set (HTS) |
| Ps = 2 | Tab Clear (TBC), Clear Current Column (default) |
| Ps = 5 | Tab Clear (TBC), Clear All |
ESC [ Ps X >Ps > Character(s) [default: 1] (ECH)
ESC [ Ps Z >Ps > [default: 1] tab stops
ESC [ Ps ' >ESC [ Ps G >
ESC [ Ps a >ESC [ Ps C >
ESC [ Ps c >Ps = 0 > (or omitted): request attributes from terminal
returns: ESC [ ? 1 ; 2 c > (``I am a VT100 with Advanced Video
Option'')
ESC [ Ps d >Ps > (VPA)
ESC [ Ps e >ESC [ Ps A >
ESC [ Ps;Ps f >ESC [ Ps g >| Ps = 0 | Clear Current Column (default) |
| Ps = 3 | Clear All (TBC) |
ESC [ Pm h >ESC [ Pm l > sequence for description of Pm.
ESC [ Ps i >print-pipe resource.
| Ps = 0 | print screen (MC0) |
| Ps = 4 | disable transparent print mode (MC4) |
| Ps = 5 | enable transparent print mode (MC5) |
ESC [ Pm l >Ps = 4 >| h | Insert Mode (SMIR) |
| l | Replace Mode (RMIR) |
Ps = 20 > (partially implemented)| h | Automatic Newline (LNM) |
| l | Normal Linefeed (LNM) |
ESC [ Pm m >| Ps = 0 | Normal (default) |
| Ps = 1 / 21 | On / Off Bold (bright fg) |
| Ps = 3 / 23 | On / Off Italic |
| Ps = 4 / 24 | On / Off Underline |
| Ps = 5 / 25 | On / Off Slow Blink (bright bg) |
| Ps = 6 / 26 | On / Off Rapid Blink (bright bg) |
| Ps = 7 / 27 | On / Off Inverse |
| Ps = 8 / 27 | On / Off Invisible (NYI) |
| Ps = 30 / 40 | fg/bg Black |
| Ps = 31 / 41 | fg/bg Red |
| Ps = 32 / 42 | fg/bg Green |
| Ps = 33 / 43 | fg/bg Yellow |
| Ps = 34 / 44 | fg/bg Blue |
| Ps = 35 / 45 | fg/bg Magenta |
| Ps = 36 / 46 | fg/bg Cyan |
| Ps = 38;5 / 48;5 | set fg/bg to color #m (ISO 8613-6) |
| Ps = 37 / 47 | fg/bg White |
| Ps = 39 / 49 | fg/bg Default |
| Ps = 90 / 100 | fg/bg Bright Black |
| Ps = 91 / 101 | fg/bg Bright Red |
| Ps = 92 / 102 | fg/bg Bright Green |
| Ps = 93 / 103 | fg/bg Bright Yellow |
| Ps = 94 / 104 | fg/bg Bright Blue |
| Ps = 95 / 105 | fg/bg Bright Magenta |
| Ps = 96 / 106 | fg/bg Bright Cyan |
| Ps = 97 / 107 | fg/bg Bright White |
| Ps = 99 / 109 | fg/bg Bright Default |
ESC [ Ps n >| Ps = 5 | Status Report ESC [ 0 n (``OK'') |
| Ps = 6 | Report Cursor Position (CPR) [row;column] as ESC [ r ; c R |
| Ps = 7 | Request Display Name |
| Ps = 8 | Request Version Number (place in window title) |
ESC [ Ps;Ps r >ESC [ s >ESC [ Ps;Pt t >| Ps = 1 | Deiconify (map) window |
| Ps = 2 | Iconify window |
| Ps = 3 | ESC [ 3 ; X ; Y t Move window to (X|Y) |
| Ps = 4 | ESC [ 4 ; H ; W t Resize to WxH pixels |
| Ps = 5 | Raise window |
| Ps = 6 | Lower window |
| Ps = 7 | Refresh screen once |
| Ps = 8 | ESC [ 8 ; R ; C t Resize to R rows and C columns |
| Ps = 11 | Report window state (responds with Ps = 1 or Ps = 2) |
| Ps = 13 | Report window position (responds with Ps = 3) |
| Ps = 14 | Report window pixel size (responds with Ps = 4) |
| Ps = 18 | Report window text size (responds with Ps = 7) |
| Ps = 19 | Currently the same as Ps = 18, but responds with Ps = 9 |
| Ps = 20 | Reports icon label (ESC ] L NAME \234) |
| Ps = 21 | Reports window title (ESC ] l NAME \234) |
| Ps = 24.. | Set window height to Ps rows |
ESC [ u >ESC [ Ps x >
ESC [ ? Pm h >ESC [ ? Pm l >ESC [ ? Pm r >ESC [ ? Pm s >ESC [ ? Pm t >Ps = 1 > (DECCKM)| h | Application Cursor Keys |
| l | Normal Cursor Keys |
Ps = 2 > (ANSI/VT52 mode)| h | Enter VT52 mode |
| l | Enter VT52 mode |
Ps = 3 >| h | 132 Column Mode (DECCOLM) |
| l | 80 Column Mode (DECCOLM) |
Ps = 4 >| h | Smooth (Slow) Scroll (DECSCLM) |
| l | Jump (Fast) Scroll (DECSCLM) |
Ps = 5 >| h | Reverse Video (DECSCNM) |
| l | Normal Video (DECSCNM) |
Ps = 6 >| h | Origin Mode (DECOM) |
| l | Normal Cursor Mode (DECOM) |
Ps = 7 >| h | Wraparound Mode (DECAWM) |
| l | No Wraparound Mode (DECAWM) |
Ps = 8 > unimplemented| h | Auto-repeat Keys (DECARM) |
| l | No Auto-repeat Keys (DECARM) |
Ps = 9 > X10 XTerm| h | Send Mouse X & Y on button press. |
| l | No mouse reporting. |
Ps = 10 > (rxvt)| h | menuBar visible |
| l | menuBar invisible |
Ps = 25 >| h | Visible cursor {cnorm/cvvis} |
| l | Invisible cursor {civis} |
Ps = 30 >| h | scrollBar visisble |
| l | scrollBar invisisble |
Ps = 35 > (rxvt)| h | Allow XTerm Shift+key sequences |
| l | Disallow XTerm Shift+key sequences |
Ps = 38 > unimplementedPs = 40 >| h | Allow 80/132 Mode |
| l | Disallow 80/132 Mode |
Ps = 44 > unimplemented| h | Turn On Margin Bell |
| l | Turn Off Margin Bell |
Ps = 45 > unimplemented| h | Reverse-wraparound Mode |
| l | No Reverse-wraparound Mode |
Ps = 46 > unimplementedPs = 47 >| h | Use Alternate Screen Buffer |
| l | Use Normal Screen Buffer |
Ps = 66 >| h | Application Keypad (DECPAM) == ESC = |
| l | Normal Keypad (DECPNM) == ESC > |
Ps = 67 >| h | Backspace key sends BS (DECBKM) |
| l | Backspace key sends DEL |
Ps = 1000 > (X11 XTerm)| h | Send Mouse X & Y on button press and release. |
| l | No mouse reporting. |
Ps = 1001 > (X11 XTerm) unimplemented| h | Use Hilite Mouse Tracking. |
| l | No mouse reporting. |
Ps = 1010 > (rxvt)| h | Don't scroll to bottom on TTY output |
| l | Scroll to bottom on TTY output |
Ps = 1011 > (rxvt)| h | Scroll to bottom when a key is pressed |
| l | Don't scroll to bottom when a key is pressed |
Ps = 1047 >| h | Use Alternate Screen Buffer |
| l | Use Normal Screen Buffer - clear Alternate Screen Buffer if returning from it |
Ps = 1048 >| h | Save cursor position |
| l | Restore cursor position |
Ps = 1049 >| h | Use Alternate Screen Buffer - clear Alternate Screen Buffer if switching to it |
| l | Use Normal Screen Buffer |
ESC ] Ps;Pt ST >| Ps = 0 | Change Icon Name and Window Title to Pt |
| Ps = 1 | Change Icon Name to Pt |
| Ps = 2 | Change Window Title to Pt |
| Ps = 3 | If Pt starts with a ?, query the (STRING) property of the window and return it. If Pt contains a =, set the named property to the given value, else delete the specified property. |
| Ps = 4 | Pt is a semi-colon separated sequence of one or more semi-colon separated number/name pairs, where number is an index to a colour and name is the name of a colour. Each pair causes the numbered colour to be changed to name. Numbers 0-7 corresponds to low-intensity (normal) colours and 8-15 corresponds to high-intensity colours. 0=black, 1=red, 2=green, 3=yellow, 4=blue, 5=magenta, 6=cyan, 7=white |
| Ps = 10 | Change colour of text foreground to Pt (NB: may change in future) |
| Ps = 11 | Change colour of text background to Pt (NB: may change in future) |
| Ps = 12 | Change colour of text cursor foreground to Pt |
| Ps = 13 | Change colour of mouse foreground to Pt |
| Ps = 17 | Change colour of highlight characters to Pt |
| Ps = 18 | Change colour of bold characters to Pt |
| Ps = 19 | Change colour of underlined characters to Pt |
| Ps = 20 | Change default background to Pt |
| Ps = 39 | Change default foreground colour to Pt. |
| Ps = 46 | Change Log File to Pt unimplemented |
| Ps = 49 | Change default background colour to Pt. |
| Ps = 50 | Set fontset to Pt, with the following special values of Pt (rxvt) #+n change up n #-n change down n if n is missing of 0, a value of 1 is used empty change to font0 n change to font n |
| Ps = 55 | Log all scrollback buffer and all of screen to Pt |
| Ps = 701 | Change current locale to Pt, or, if Pt is ?, return the current locale (Compile frills). |
| Ps = 703 | Menubar command Pt (Compile menubar). |
| Ps = 704 | Change colour of italic characters to Pt |
| Ps = 705 | Change background pixmap tint colour to Pt (Compile transparency). |
| Ps = 710 | Set normal fontset to Pt. Same as Ps = 50. |
| Ps = 711 | Set bold fontset to Pt. Similar to Ps = 50 (Compile styles). |
| Ps = 712 | Set italic fontset to Pt. Similar to Ps = 50 (Compile styles). |
| Ps = 713 | Set bold-italic fontset to Pt. Similar to Ps = 50 (Compile styles). |
| Ps = 720 | Move viewing window up by Pt lines, or clear scrollback buffer if Pt = 0 (Compile frills). |
| Ps = 721 | Move viewing window down by Pt lines, or clear scrollback buffer if Pt = 0 (Compile frills). |
The exact syntax used is almost solidified. > In the menus, DON'T try to use menuBar commands that add or remove a menuBar.
Note that in all of the commands, the /path/ > cannot be omitted: use ./ to specify a menu relative to the current menu.
For the menuBar XTerm escape sequence ESC ] 703 ; Pt ST, the syntax
of Pt can be used for a variety of tasks:
At the top level is the current menuBar which is a member of a circular linked-list of other such menuBars.
The menuBar acts as a parent for the various drop-down menus, which in turn, may have labels, separator lines, menuItems and subMenus.
The menuItems are the useful bits: you can use them to mimic keyboard input or even to send text or escape sequences back to rxvt.
The menuBar syntax is intended to provide a simple yet robust method of constructing and manipulating menus and navigating through the menuBars.
The first step is to use the tag [menu:name] > which creates the menuBar called name and allows access. You may now or menus, subMenus, and menuItems. Finally, use the tag [done] to set the menuBar access as readonly to prevent accidental corruption of the menus. To re-access the current menuBar for alterations, use the tag [menu], make the alterations and then use [done]
B<%n> rxvt name (as per the B<-name> command-line option) B<%v> rxvt version B<%%> literal B<%> character
Blank and comment lines (starting with #) are ignored. Actually, since any invalid menu commands are also ignored, almost anything could be construed as a comment line, but this may be tightened up in the future ... so don't count on it!.
A Future implementation may make this local to the menubar >)
The following commands may also be + prefixed.
To send a string starting with a NUL (^@) character to the program, start action with a pair of NUL characters (^@^@), the first of which will be stripped off and the balance directed to the program. Otherwise if action begins with NUL followed by non-+NUL characters, the leading NUL is stripped off and the balance is sent back to rxvt.
As a convenience for the many Emacs-type editors, action may start with M- (eg, M-$ is equivalent to \E$) and a CR will be appended if missed from M-x commands.
As a convenience for issuing XTerm ESC ] sequences from a menubar (or quick arrow), a BEL (^G) will be appended if needed.
The option {right-rtext} > will be right-justified. In the absence of a specified action, this text will be used as the action as well.
The left label is necessary, since it's used for matching, but implicitly hiding the left label (by using same name for both left and right labels), or explicitly hiding the left label (by preceeding it with a dot), makes it possible to have right-justified text only.
The menus also provide a hook for quick arrows to provide easier user access. If nothing has been explicitly set, the default is to emulate the curror keys. The syntax permits each arrow to be altered individually or all four at once without re-entering their common beginning/end text. For example, to explicitly associate cursor actions with the arrows, any of the following forms could be used:
<u>\E[A
<d>\E[B
<r>\E[C
<l>\E[D
<u>\E[AZ<><d>\E[BZ<><r>\E[CZ<><l>\E[D
<b>\E[<u>AZ<><d>BZ<><r>CZ<><l>D
A short summary of the most common commands:
menuBar(s)
menuBar(s)
For the XPM XTerm escape sequence ESC ] 20 ; Pt ST > then value
of Pt > can be the name of the background pixmap followed by a
sequence of scaling/positioning commands separated by semi-colons. The
scaling/positioning commands are as follows:
WxH+X (== WxH+X+X)
WxH (same as WxH+50+50)
W+X+Y (same as WxW+X+Y)
W+X (same as WxW+X+X)
W (same as WxW+50+50)
=+X (same as =+X+Y)
+X (same as +X+Y)
0xH -> H *= (H/100)
For example:
ESC [ M <b> <x> <y> >The lower 2 bits of <b> > indicate the button:
(<b> - SPACE) & 3 >| 0 | Button1 pressed |
| 1 | Button2 pressed |
| 2 | Button3 pressed |
| 3 | button released (X11 mouse report) |
The upper bits of <b> > indicate the modifiers when the
button was pressed and are added together (X11 mouse report only):
(<b> - SPACE) & 60 >| 4 | Shift |
| 8 | Meta |
| 16 | Control |
| 32 | Double Click (Rxvt extension) |
Col = <x> - SPACE >
Row = <y> - SPACE >
Note: Shift + F1-F10 generates F11-F20
For the keypad, use Shift to temporarily override Application-Keypad setting use Num_Lock to toggle Application-Keypad setting if Num_Lock is off, toggle Application-Keypad setting. Also note that values of Home, End, Delete may have been compiled differently on your system.
| Normal | Shift | Control | Ctrl+Shift | |
| Tab | ^I | ESC [ Z | ^I | ESC [ Z |
| BackSpace | ^H | ^? | ^? | ^? |
| Find | ESC [ 1 ~ | ESC [ 1 $ | ESC [ 1 ^ | ESC [ 1 @ |
| Insert | ESC [ 2 ~ | paste | ESC [ 2 ^ | ESC [ 2 @ |
| Execute | ESC [ 3 ~ | ESC [ 3 $ | ESC [ 3 ^ | ESC [ 3 @ |
| Select | ESC [ 4 ~ | ESC [ 4 $ | ESC [ 4 ^ | ESC [ 4 @ |
| Prior | ESC [ 5 ~ | scroll-up | ESC [ 5 ^ | ESC [ 5 @ |
| Next | ESC [ 6 ~ | scroll-down | ESC [ 6 ^ | ESC [ 6 @ |
| Home | ESC [ 7 ~ | ESC [ 7 $ | ESC [ 7 ^ | ESC [ 7 @ |
| End | ESC [ 8 ~ | ESC [ 8 $ | ESC [ 8 ^ | ESC [ 8 @ |
| Delete | ESC [ 3 ~ | ESC [ 3 $ | ESC [ 3 ^ | ESC [ 3 @ |
| F1 | ESC [ 11 ~ | ESC [ 23 ~ | ESC [ 11 ^ | ESC [ 23 ^ |
| F2 | ESC [ 12 ~ | ESC [ 24 ~ | ESC [ 12 ^ | ESC [ 24 ^ |
| F3 | ESC [ 13 ~ | ESC [ 25 ~ | ESC [ 13 ^ | ESC [ 25 ^ |
| F4 | ESC [ 14 ~ | ESC [ 26 ~ | ESC [ 14 ^ | ESC [ 26 ^ |
| F5 | ESC [ 15 ~ | ESC [ 28 ~ | ESC [ 15 ^ | ESC [ 28 ^ |
| F6 | ESC [ 17 ~ | ESC [ 29 ~ | ESC [ 17 ^ | ESC [ 29 ^ |
| F7 | ESC [ 18 ~ | ESC [ 31 ~ | ESC [ 18 ^ | ESC [ 31 ^ |
| F8 | ESC [ 19 ~ | ESC [ 32 ~ | ESC [ 19 ^ | ESC [ 32 ^ |
| F9 | ESC [ 20 ~ | ESC [ 33 ~ | ESC [ 20 ^ | ESC [ 33 ^ |
| F10 | ESC [ 21 ~ | ESC [ 34 ~ | ESC [ 21 ^ | ESC [ 34 ^ |
| F11 | ESC [ 23 ~ | ESC [ 23 $ | ESC [ 23 ^ | ESC [ 23 @ |
| F12 | ESC [ 24 ~ | ESC [ 24 $ | ESC [ 24 ^ | ESC [ 24 @ |
| F13 | ESC [ 25 ~ | ESC [ 25 $ | ESC [ 25 ^ | ESC [ 25 @ |
| F14 | ESC [ 26 ~ | ESC [ 26 $ | ESC [ 26 ^ | ESC [ 26 @ |
| F15 (Help) | ESC [ 28 ~ | ESC [ 28 $ | ESC [ 28 ^ | ESC [ 28 @ |
| F16 (Menu) | ESC [ 29 ~ | ESC [ 29 $ | ESC [ 29 ^ | ESC [ 29 @ |
| F17 | ESC [ 31 ~ | ESC [ 31 $ | ESC [ 31 ^ | ESC [ 31 @ |
| F18 | ESC [ 32 ~ | ESC [ 32 $ | ESC [ 32 ^ | ESC [ 32 @ |
| F19 | ESC [ 33 ~ | ESC [ 33 $ | ESC [ 33 ^ | ESC [ 33 @ |
| F20 | ESC [ 34 ~ | ESC [ 34 $ | ESC [ 34 ^ | ESC [ 34 @ |
| Application | ||||
| Up | ESC [ A | ESC [ a | ESC O a | ESC O A |
| Down | ESC [ B | ESC [ b | ESC O b | ESC O B |
| Right | ESC [ C | ESC [ c | ESC O c | ESC O C |
| Left | ESC [ D | ESC [ d | ESC O d | ESC O D |
| KP_Enter | ^M | ESC O M | ||
| KP_F1 | ESC O P | ESC O P | ||
| KP_F2 | ESC O Q | ESC O Q | ||
| KP_F3 | ESC O R | ESC O R | ||
| KP_F4 | ESC O S | ESC O S | ||
| XK_KP_Multiply | * | ESC O j | ||
| XK_KP_Add | + | ESC O k | ||
| XK_KP_Separator | , | ESC O l | ||
| XK_KP_Subtract | - | ESC O m | ||
| XK_KP_Decimal | . | ESC O n | ||
| XK_KP_Divide | / | ESC O o | ||
| XK_KP_0 | 0 | ESC O p | ||
| XK_KP_1 | 1 | ESC O q | ||
| XK_KP_2 | 2 | ESC O r | ||
| XK_KP_3 | 3 | ESC O s | ||
| XK_KP_4 | 4 | ESC O t | ||
| XK_KP_5 | 5 | ESC O u | ||
| XK_KP_6 | 6 | ESC O v | ||
| XK_KP_7 | 7 | ESC O w | ||
| XK_KP_8 | 8 | ESC O x | ||
| XK_KP_9 | 9 | ESC O y |
General hint: if you get compile errors, then likely your configuration hasn't been tested well. Either try with --enable-everything or use the ./reconf script as a base for experiments. ./reconf is used by myself, so it should generally be a working config. Of course, you should always report when a combination doesn't work, so it can be fixed. Marc Lehmann <rxvt@schmorp.de>.
| all | all available codeset groups |
| zh | common chinese encodings |
| zh_ext | rarely used but very big chinese encodigs |
| jp | common japanese encodings |
| jp_ext | rarely used but big japanese encodings |
| kr | korean encodings |
Please note that rxvt-unicode can store unicode code points >65535 even without this flag, but the number of such characters is limited to a view thousand (shared with combining characters, see next switch), and right now rxvt-unicode cannot display them (input/output and cut&paste still work, though).
Without --enable-unicode3, the number of additional precomposed characters is rather limited (2048, if this is full, rxvt-unicode will use the private use area, extending the number of combinations to 8448). With --enable-unicode3, no practical limit exists.
This option will also enable storage (but not display) of characters beyond plane 0 (>65535) when --enable-unicode3 was not specified.
The combining table also contains entries for arabic presentation forms, but these are not currently used. Bug me if you want these to be used (and tell me how these are to be used...).
XGetDefault() instead of our small
version which only checks ~/.Xdefaults, or if that doesn't exist then
~/.Xresources.
Please note that nowadays, things like XIM will automatically pull in and use the full X resource manager, so the overhead of using it might be very small, if nonexistant.
memset() function and other
various routines, overriding your system's versions which may
have been hand-crafted in assembly or may require extra libraries
to link in. (this breaks ANSI-C rules and has problems on many
GNU/Linux systems).
A non-exhaustive list of features enabled by --enable-frills (possibly
in combination with other switches) is:
MWM-hints EWMH-hints (pid, utf8 names) and protocols (ping) seperate underline colour settable border widths and borderless switch settable extra linespacing iso-14755-2 and -3, and visual feedback backindex and forwardindex escape sequence window op and some xterm/OSC escape sequences tripleclickwords settable insecure mode keysym remapping support -embed and -pty-fd options
--enable-frills, while support for 5.2, 5.3 and 5.4 is enabled with
this switch.
You can only use either this option and the following (should you use either) .
urxvt, resulting
in urxvt, urxvtd etc.). Specify --with-name=rxvt to replace with
rxvt.
rxvt-unicode)
Marc Lehmann <rxvt@schmorp.de> converted this document to pod and reworked it from the original Rxvt documentation, which was done by Geoff Wing <gcw@pobox.com>, who in turn used the XTerm documentation and other sources.