From 723b9c5522e1d9dd02b1be3a37e03c14dab2a374 Mon Sep 17 00:00:00 2001
From: root
+ 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.
+ 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.
+SYNOPSIS
+
+ # 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"
+
+DESCRIPTION
+
FREQUENTLY ASKED QUESTIONS
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).
+
@@ -85,8 +126,9 @@ 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 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,19 +139,27 @@ the desired TERM value or use a resource to set it: 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:
@@ -174,6 +224,17 @@ 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
-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 +261,9 @@ into other problems. If nothing works you can try this in your .profile.
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 +291,10 @@ to display.
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 +311,23 @@ 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 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 +336,13 @@ 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 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.
__STDC_ISO_10646__
requires th
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 +457,7 @@ 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.
+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 Rxvt-unicode ignores all other locale categories, and except for
the encoding, ignores country or language-specific settings,
-i.e. LC_CTYPE
locale category to select encoding. All
@@ -429,7 +497,8 @@ locale. Common names for locales are en_US.UTF-8
, de_DE.ISO-8
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 +508,7 @@ rxvt-unicode with the correct LC_CTYPE
category.
LC_CTYPE
.
LC_CTYPE
.
printf '\e]701;%s\007' ja_JP.SJIS
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 +530,16 @@ locale supported by xjdic and back later: 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
- 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 +717,22 @@ including the murky brown that passes for low-intensity yellow: 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 +795,7 @@ 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.
+(ESC [ 3 ~
) and is in the supplied termcap/terminfo.
Some other Backspace problems:
@@ -727,30 +817,30 @@ you have run ``configure'' with theHere's an example for a URxvt session started using `rxvt -name URxvt'
+Here's an example for a URxvt session started using rxvt -name URxvt
- URxvt.keysym.Home: \e[1~ - URxvt.keysym.End: \e[4~ - URxvt.keysym.C-apostrophe: \e<C-'> - URxvt.keysym.C-slash: \e<C-/> - URxvt.keysym.C-semicolon: \e<C-;> - URxvt.keysym.C-grave: \e<C-`> - URxvt.keysym.C-comma: \e<C-,> - URxvt.keysym.C-period: \e<C-.> - URxvt.keysym.C-0x60: \e<C-`> - URxvt.keysym.C-Tab: \e<C-Tab> - URxvt.keysym.C-Return: \e<C-Return> - URxvt.keysym.S-Return: \e<S-Return> - URxvt.keysym.S-space: \e<S-Space> - URxvt.keysym.M-Up: \e<M-Up> - URxvt.keysym.M-Down: \e<M-Down> - URxvt.keysym.M-Left: \e<M-Left> - URxvt.keysym.M-Right: \e<M-Right> - URxvt.keysym.M-C-0: list \e<M-C- 0123456789 > + 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: proto:\033]701;zh_CN.GBK\007+ URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007
See some more examples in the documentation for the keysym resource.
@@ -774,7 +864,7 @@ has the following mappings that rxvt-unicode doesn't recognize.
- # 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"+
configure
time.
-
-c
>ESC Z
>ESC[?1;2C
> rxvt-unicode compile-time option
+Obsolete form of returns: ESC [ ? 1 ; 2 C
> rxvt-unicode compile-time option
ESC c
>ESC
( C >>ESC ( C
>C
.
ESC
) C >>ESC ) C
>C
.
@@ -1259,7 +1336,7 @@ See ESC [ Ps C
&g
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'')
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.
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.