+ # 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[8n sets the window title to the version number.
+sequence 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.
If you always want to do this you can either recompile rxvt-unicode with -the desired TERM value or use a resource to set it:
+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:
@@ -97,40 +139,49 @@ 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: +like this:
infocmp -C rxvt-unicode
OR you could this termcap entry:
+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:\
+ :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=^O:al=\E[L:\
- :as=^N: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:\
- :k0=\E[21~: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:\
+ :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:
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
-sth. else, e.h. en_GB.UTF-8. Needless to say, this is not going to work.
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 @@ -200,7 +262,9 @@
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. If it displays sth. like:
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:
@@ -228,10 +292,10 @@
rxvt-unicode makes a best-effort try at finding a replacement font. Often the result is fine, but sometimes the chosen font looks -bad. Many 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 contains indeed look correct.
+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, @@ -248,23 +312,23 @@ search and use less resources within rxvt-unicode and the X-server.
The only limitation is that all the fonts must not be larger than the base -font, as the base font defines the principal cell size, which must be the -same due to the way terminals work.
+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 @@ -273,10 +337,13 @@ first. If you expect more chinese, put a chinese font first.
In the future it might be possible to switch 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).
+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).
urxvt), 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:
+First of all, make sure you are running with the right terminal settings
+(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+ URxvt.colorBD: white + URxvt.colorIT: green
In the meantime, you can either edit your urxvt 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.
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.
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 legal.
+wchar_t. This is, of course, completely fine with respect to standards.However, __STDC_ISO_10646__ is the only sane way to support
@@ -392,7 +458,7 @@
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.
+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 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
@@ -429,7 +498,8 @@
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 same for rxvt-unicode.
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 @@ -439,7 +509,7 @@
LC_CTYPE.
See also the previous question.
+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 UTF-8. For
-example, I use this script to start xjdic, which first switches to a
-locale supported by xjdic and back later:
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:
@@ -461,11 +531,16 @@
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:
xft:Bitstream Vera Sans
-Mono completely fails in it's italic face. A workaround is to enable
-freetype autohinting, i.e. like this:
+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+ URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true + URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true
So the only workaround is not to kill your Input Method Servers.
+- 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.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+ 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 as -``pretty girly'':
+And here is a more complete set of non-standard colors described (not by +me) as ``pretty girly''.
@@ -643,6 +732,22 @@
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
+Toggle with ``ESC[36h'' / ``ESC[36l'' as documented in rxvt(7).
+Toggle with ESC [ 36 h / ESC [ 36 l as documented in rxvt(7).
For an existing rxvt-unicode:
@@ -705,7 +810,7 @@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.
+(ESC [ 3 ~) and is in the supplied termcap/terminfo.
Some other Backspace problems:
@@ -724,60 +829,36 @@--disable-resources option you can
-use the `keysym' resource to alter the keystrings associated with keysym
-0xFF00 - 0xFFFF (function, cursor keys, etc).
+use the `keysym' resource to alter the keystrings associated with keysyms.
Here's an example for a tn3270 session started using `rxvt -name tn3270'
+Here's an example for a URxvt session started using rxvt -name URxvt
- !# ----- special uses ------: - ! tn3270 login, remap function and arrow keys. - tn3270*font: *clean-bold-*-*--15-*+ 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
- ! keysym - used by rxvt only - ! Delete - ^D - tn3270*keysym.0xFFFF: \004-
- ! Home - ^A - tn3270*keysym.0xFF50: \001 - ! Left - ^B - tn3270*keysym.0xFF51: \002 - ! Up - ^P - tn3270*keysym.0xFF52: \020 - ! Right - ^F - tn3270*keysym.0xFF53: \006 - ! Down - ^N - tn3270*keysym.0xFF54: \016 - ! End - ^E - tn3270*keysym.0xFF57: \005-
- ! F1 - F12 - tn3270*keysym.0xFFBE: \e1 - tn3270*keysym.0xFFBF: \e2 - tn3270*keysym.0xFFC0: \e3 - tn3270*keysym.0xFFC1: \e4 - tn3270*keysym.0xFFC2: \e5 - tn3270*keysym.0xFFC3: \e6 - tn3270*keysym.0xFFC4: \e7 - tn3270*keysym.0xFFC5: \e8 - tn3270*keysym.0xFFC6: \e9 - tn3270*keysym.0xFFC7: \e0 - tn3270*keysym.0xFFC8: \e- - tn3270*keysym.0xFFC9: \e=-
- ! map Prior/Next to F7/F8 - tn3270*keysym.0xFF55: \e7 - tn3270*keysym.0xFF56: \e8+
See some more examples in the documentation for the keysym resource.
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.
+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.
- # 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"+
-
-ESC ( C >>ESC ( C >C.
ESC ) C >>ESC ) C >C.
@@ -1283,7 +1351,7 @@
Ps = 0 > (or omitted): request attributes from terminal
-returns: ESC[?1;2c > (``I am a VT100 with Advanced Video
+returns: ESC [ ? 1 ; 2 c > (``I am a VT100 with Advanced Video
Option'')
ESC [ Ps x >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 >@@ -1689,9 +1780,12 @@
+ B<%n> rxvt name (as per the B<-name> command-line option) + B<%v> rxvt version + B<%%> literal B<%> character
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 +
As a convenience for issuing XTerm ESC ] sequences from a menubar (or quick arrow), a BEL (^G) will be appended if needed.
Without --enable-unicode3, the number of additional precomposed -characters is rather limited (2048, if this is full, rxvt will use the +
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 will also enable -storage of characters >65535.
+--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.
+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.
+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.
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 locale change escape sequences + tripleclickwords + settable insecure mode + keysym remapping support + -embed and -pty-fd options+
urxvt, resulting
+in urxvt, urxvtd etc.). Specify --with-name=rxvt to replace with
+rxvt.
rxvt-unicode)