| 1 |
FREQUENTLY ASKED QUESTIONS |
| 2 |
How do I know which rxvt-unicode version I'm using? |
| 3 |
The version number is displayed with the usage (-h). Also the escape |
| 4 |
sequence "ESC [ 8 n" sets the window title to the version number. |
| 5 |
|
| 6 |
I am using Debian GNU/Linux and have a problem... |
| 7 |
The Debian GNU/Linux package of rxvt-unicode in sarge contains large |
| 8 |
patches that considerably change the behaviour of rxvt-unicode. |
| 9 |
Before reporting a bug to the original rxvt-unicode author please |
| 10 |
download and install the genuine version |
| 11 |
(<http://software.schmorp.de#rxvt-unicode>) and try to reproduce the |
| 12 |
problem. If you cannot, chances are that the problems are specific |
| 13 |
to Debian GNU/Linux, in which case it should be reported via the |
| 14 |
Debian Bug Tracking System (use "reportbug" to report the bug). |
| 15 |
|
| 16 |
For other problems that also affect the Debian package, you can and |
| 17 |
probably should use the Debian BTS, too, because, after all, it's |
| 18 |
also a bug in the Debian version and it serves as a reminder for |
| 19 |
other users that might encounter the same issue. |
| 20 |
|
| 21 |
When I log-in to another system it tells me about missing terminfo data? |
| 22 |
The terminal description used by rxvt-unicode is not as widely |
| 23 |
available as that for xterm, or even rxvt (for which the same |
| 24 |
problem often arises). |
| 25 |
|
| 26 |
The correct solution for this problem is to install the terminfo, |
| 27 |
this can be done like this (with ncurses' infocmp): |
| 28 |
|
| 29 |
REMOTE=remotesystem.domain |
| 30 |
infocmp rxvt-unicode | ssh $REMOTE "cat >/tmp/ti && tic /tmp/ti" |
| 31 |
|
| 32 |
... or by installing rxvt-unicode normally on the remote system, |
| 33 |
|
| 34 |
If you cannot or do not want to do this, then you can simply set |
| 35 |
"TERM=rxvt" or even "TERM=xterm", and live with the small number of |
| 36 |
problems arising, which includes wrong keymapping, less and |
| 37 |
different colours and some refresh errors in fullscreen |
| 38 |
applications. It's a nice quick-and-dirty workaround for rare cases, |
| 39 |
though. |
| 40 |
|
| 41 |
If you always want to do this (and are fine with the consequences) |
| 42 |
you can either recompile rxvt-unicode with the desired TERM value or |
| 43 |
use a resource to set it: |
| 44 |
|
| 45 |
URxvt.termName: rxvt |
| 46 |
|
| 47 |
If you don't plan to use rxvt (quite common...) you could also |
| 48 |
replace the rxvt terminfo file with the rxvt-unicode one. |
| 49 |
|
| 50 |
"tic" outputs some error when compiling the terminfo entry. |
| 51 |
Most likely it's the empty definition for "enacs=". Just replace it |
| 52 |
by "enacs=\E[0@" and try again. |
| 53 |
|
| 54 |
"bash"'s readline does not work correctly under rxvt. |
| 55 |
I need a termcap file entry. |
| 56 |
One reason you might want this is that some distributions or |
| 57 |
operating systems still compile some programs using the |
| 58 |
long-obsoleted termcap library (Fedora Core's bash is one example) |
| 59 |
and rely on a termcap entry for "rxvt-unicode". |
| 60 |
|
| 61 |
You could use rxvt's termcap entry with resonable results in many |
| 62 |
cases. You can also create a termcap entry by using terminfo's |
| 63 |
infocmp program like this: |
| 64 |
|
| 65 |
infocmp -C rxvt-unicode |
| 66 |
|
| 67 |
Or you could use this termcap entry, generated by the command above: |
| 68 |
|
| 69 |
rxvt-unicode|rxvt-unicode terminal (X Window System):\ |
| 70 |
:am:bw:eo:km:mi:ms:xn:xo:\ |
| 71 |
:co#80:it#8:li#24:lm#0:\ |
| 72 |
:AL=\E[%dL:DC=\E[%dP:DL=\E[%dM:DO=\E[%dB:IC=\E[%d@:\ |
| 73 |
:K1=\EOw:K2=\EOu:K3=\EOy:K4=\EOq:K5=\EOs:LE=\E[%dD:\ |
| 74 |
:RI=\E[%dC:SF=\E[%dS:SR=\E[%dT:UP=\E[%dA:ae=\E(B:al=\E[L:\ |
| 75 |
:as=\E(0:bl=^G:cd=\E[J:ce=\E[K:cl=\E[H\E[2J:\ |
| 76 |
:cm=\E[%i%d;%dH:cr=^M:cs=\E[%i%d;%dr:ct=\E[3g:dc=\E[P:\ |
| 77 |
:dl=\E[M:do=^J:ec=\E[%dX:ei=\E[4l:ho=\E[H:\ |
| 78 |
:i1=\E[?47l\E=\E[?1l:ic=\E[@:im=\E[4h:\ |
| 79 |
:is=\E[r\E[m\E[2J\E[H\E[?7h\E[?1;3;4;6l\E[4l:\ |
| 80 |
:k1=\E[11~:k2=\E[12~:k3=\E[13~:k4=\E[14~:k5=\E[15~:\ |
| 81 |
:k6=\E[17~:k7=\E[18~:k8=\E[19~:k9=\E[20~:kD=\E[3~:\ |
| 82 |
:kI=\E[2~:kN=\E[6~:kP=\E[5~:kb=\177:kd=\EOB:ke=\E[?1l\E>:\ |
| 83 |
:kh=\E[7~:kl=\EOD:kr=\EOC:ks=\E[?1h\E=:ku=\EOA:le=^H:\ |
| 84 |
:mb=\E[5m:md=\E[1m:me=\E[m\017:mr=\E[7m:nd=\E[C:rc=\E8:\ |
| 85 |
:sc=\E7:se=\E[27m:sf=^J:so=\E[7m:sr=\EM:st=\EH:ta=^I:\ |
| 86 |
:te=\E[r\E[?1049l:ti=\E[?1049h:ue=\E[24m:up=\E[A:\ |
| 87 |
:us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\ |
| 88 |
:vs=\E[?25h: |
| 89 |
|
| 90 |
Why does "ls" no longer have coloured output? |
| 91 |
The "ls" in the GNU coreutils unfortunately doesn't use terminfo to |
| 92 |
decide wether a terminal has colour, but uses it's own configuration |
| 93 |
file. Needless to say, "rxvt-unicode" is not in it's default file |
| 94 |
(among with most other terminals supporting colour). Either add: |
| 95 |
|
| 96 |
TERM rxvt-unicode |
| 97 |
|
| 98 |
to "/etc/DIR_COLORS" or simply add: |
| 99 |
|
| 100 |
alias ls='ls --color=auto' |
| 101 |
|
| 102 |
to your ".profile" or ".bashrc". |
| 103 |
|
| 104 |
Why doesn't vim/emacs etc. use the 88 colour mode? |
| 105 |
Why doesn't vim/emacs etc. make use of italic? |
| 106 |
Why are the secondary screen-related options not working properly? |
| 107 |
Make sure you are using "TERM=rxvt-unicode". Some pre-packaged |
| 108 |
distributions (most notably Debian GNU/Linux) break rxvt-unicode by |
| 109 |
setting "TERM" to "rxvt", which doesn't have these extra features. |
| 110 |
Unfortunately, some of these (most notably, again, Debian GNU/Linux) |
| 111 |
furthermore fail to even install the "rxvt-unicode" terminfo file, |
| 112 |
so you will need to install it on your own (See the question When I |
| 113 |
log-in to another system it tells me about missing terminfo data? on |
| 114 |
how to do this). |
| 115 |
|
| 116 |
My numerical keypad acts weird and generates differing output? |
| 117 |
Some Debian GNUL/Linux users seem to have this problem, although no |
| 118 |
specific details were reported so far. It is possible that this is |
| 119 |
caused by the wrong "TERM" setting, although the details of wether |
| 120 |
and how this can happen are unknown, as "TERM=rxvt" should offer a |
| 121 |
compatible keymap. See the answer to the previous question, and |
| 122 |
please report if that helped. |
| 123 |
|
| 124 |
Rxvt-unicode does not seem to understand the selected encoding? |
| 125 |
Unicode does not seem to work? |
| 126 |
If you encounter strange problems like typing an accented character |
| 127 |
but getting two unrelated other characters or similar, or if program |
| 128 |
output is subtly garbled, then you should check your locale |
| 129 |
settings. |
| 130 |
|
| 131 |
Rxvt-unicode must be started with the same "LC_CTYPE" setting as the |
| 132 |
programs. Often rxvt-unicode is started in the "C" locale, while the |
| 133 |
login script running within the rxvt-unicode window changes the |
| 134 |
locale to something else, e.g. "en_GB.UTF-8". Needless to say, this |
| 135 |
is not going to work. |
| 136 |
|
| 137 |
The best thing is to fix your startup environment, as you will |
| 138 |
likely run into other problems. If nothing works you can try this in |
| 139 |
your .profile. |
| 140 |
|
| 141 |
printf '\e]701;%s\007' "$LC_CTYPE" |
| 142 |
|
| 143 |
If this doesn't work, then maybe you use a "LC_CTYPE" specification |
| 144 |
not supported on your systems. Some systems have a "locale" command |
| 145 |
which displays this (also, "perl -e0" can be used to check locale |
| 146 |
settings, as it will complain loudly if it cannot set the locale). |
| 147 |
If it displays something like: |
| 148 |
|
| 149 |
locale: Cannot set LC_CTYPE to default locale: ... |
| 150 |
|
| 151 |
Then the locale you specified is not supported on your system. |
| 152 |
|
| 153 |
If nothing works and you are sure that everything is set correctly |
| 154 |
then you will need to remember a little known fact: Some programs |
| 155 |
just don't support locales :( |
| 156 |
|
| 157 |
Why do some characters look so much different than others? |
| 158 |
How does rxvt-unicode choose fonts? |
| 159 |
Most fonts do not contain the full range of Unicode, which is fine. |
| 160 |
Chances are that the font you (or the admin/package maintainer of |
| 161 |
your system/os) have specified does not cover all the characters you |
| 162 |
want to display. |
| 163 |
|
| 164 |
rxvt-unicode makes a best-effort try at finding a replacement font. |
| 165 |
Often the result is fine, but sometimes the chosen font looks |
| 166 |
bad/ugly/wrong. Some fonts have totally strange characters that |
| 167 |
don't resemble the correct glyph at all, and rxvt-unicode lacks the |
| 168 |
artificial intelligence to detect that a specific glyph is wrong: it |
| 169 |
has to believe the font that the characters it claims to contain |
| 170 |
indeed look correct. |
| 171 |
|
| 172 |
In that case, select a font of your taste and add it to the font |
| 173 |
list, e.g.: |
| 174 |
|
| 175 |
rxvt -fn basefont,font2,font3... |
| 176 |
|
| 177 |
When rxvt-unicode sees a character, it will first look at the base |
| 178 |
font. If the base font does not contain the character, it will go to |
| 179 |
the next font, and so on. Specifying your own fonts will also speed |
| 180 |
up this search and use less resources within rxvt-unicode and the |
| 181 |
X-server. |
| 182 |
|
| 183 |
The only limitation is that none of the fonts may be larger than the |
| 184 |
base font, as the base font defines the terminal character cell |
| 185 |
size, which must be the same due to the way terminals work. |
| 186 |
|
| 187 |
Why do some chinese characters look so different than others? |
| 188 |
This is because there is a difference between script and language -- |
| 189 |
rxvt-unicode does not know which language the text that is output |
| 190 |
is, as it only knows the unicode character codes. If rxvt-unicode |
| 191 |
first sees a japanese/chinese character, it might choose a japanese |
| 192 |
font for display. Subsequent japanese characters will use that font. |
| 193 |
Now, many chinese characters aren't represented in japanese fonts, |
| 194 |
so when the first non-japanese character comes up, rxvt-unicode will |
| 195 |
look for a chinese font -- unfortunately at this point, it will |
| 196 |
still use the japanese font for chinese characters that are also in |
| 197 |
the japanese font. |
| 198 |
|
| 199 |
The workaround is easy: just tag a chinese font at the end of your |
| 200 |
font list (see the previous question). The key is to view the font |
| 201 |
list as a preference list: If you expect more japanese, list a |
| 202 |
japanese font first. If you expect more chinese, put a chinese font |
| 203 |
first. |
| 204 |
|
| 205 |
In the future it might be possible to switch language preferences at |
| 206 |
runtime (the internal data structure has no problem with using |
| 207 |
different fonts for the same character at the same time, but no |
| 208 |
interface for this has been designed yet). |
| 209 |
|
| 210 |
Until then, you might get away with switching fonts at runtime (see |
| 211 |
"Can I switch the fonts at runtime?" later in this document). |
| 212 |
|
| 213 |
Why does rxvt-unicode sometimes leave pixel droppings? |
| 214 |
Most fonts were not designed for terminal use, which means that |
| 215 |
character size varies a lot. A font that is otherwise fine for |
| 216 |
terminal use might contain some characters that are simply too wide. |
| 217 |
Rxvt-unicode will avoid these characters. For characters that are |
| 218 |
just "a bit" too wide a special "careful" rendering mode is used |
| 219 |
that redraws adjacent characters. |
| 220 |
|
| 221 |
All of this requires that fonts do not lie about character sizes, |
| 222 |
however: Xft fonts often draw glyphs larger than their acclaimed |
| 223 |
bounding box, and rxvt-unicode has no way of detecting this (the |
| 224 |
correct way is to ask for the character bounding box, which |
| 225 |
unfortunately is wrong in these cases). |
| 226 |
|
| 227 |
It's not clear (to me at least), wether this is a bug in Xft, |
| 228 |
freetype, or the respective font. If you encounter this problem you |
| 229 |
might try using the "-lsp" option to give the font more height. If |
| 230 |
that doesn't work, you might be forced to use a different font. |
| 231 |
|
| 232 |
All of this is not a problem when using X11 core fonts, as their |
| 233 |
bounding box data is correct. |
| 234 |
|
| 235 |
On Solaris 9, many line-drawing characters are too wide. |
| 236 |
Seems to be a known bug, read |
| 237 |
<http://nixdoc.net/files/forum/about34198.html>. Some people use the |
| 238 |
following ugly workaround to get non-double-wide-characters working: |
| 239 |
|
| 240 |
#define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x) |
| 241 |
|
| 242 |
My Compose (Multi_key) key is no longer working. |
| 243 |
The most common causes for this are that either your locale is not |
| 244 |
set correctly, or you specified a preeditStyle that is not supported |
| 245 |
by your input method. For example, if you specified OverTheSpot and |
| 246 |
your input method (e.g. the default input method handling Compose |
| 247 |
keys) does not support this (for instance because it is not visual), |
| 248 |
then rxvt-unicode will continue without an input method. |
| 249 |
|
| 250 |
In this case either do not specify a preeditStyle or specify more |
| 251 |
than one pre-edit style, such as OverTheSpot,Root,None. |
| 252 |
|
| 253 |
I cannot type "Ctrl-Shift-2" to get an ASCII NUL character due to ISO |
| 254 |
14755 |
| 255 |
Either try "Ctrl-2" alone (it often is mapped to ASCII NUL even on |
| 256 |
international keyboards) or simply use ISO 14755 support to your |
| 257 |
advantage, typing <Ctrl-Shift-0> to get a ASCII NUL. This works for |
| 258 |
other codes, too, such as "Ctrl-Shift-1-d" to type the default |
| 259 |
telnet escape character and so on. |
| 260 |
|
| 261 |
How can I keep rxvt-unicode from using reverse video so much? |
| 262 |
First of all, make sure you are running with the right terminal |
| 263 |
settings ("TERM=rxvt-unicode"), which will get rid of most of these |
| 264 |
effects. Then make sure you have specified colours for italic and |
| 265 |
bold, as otherwise rxvt-unicode might use reverse video to simulate |
| 266 |
the effect: |
| 267 |
|
| 268 |
URxvt.colorBD: white |
| 269 |
URxvt.colorIT: green |
| 270 |
|
| 271 |
Some programs assume totally weird colours (red instead of blue), how |
| 272 |
can I fix that? |
| 273 |
For some unexplainable reason, some rare programs assume a very |
| 274 |
weird colour palette when confronted with a terminal with more than |
| 275 |
the standard 8 colours (rxvt-unicode supports 88). The right fix is, |
| 276 |
of course, to fix these programs not to assume non-ISO colours |
| 277 |
without very good reasons. |
| 278 |
|
| 279 |
In the meantime, you can either edit your "rxvt-unicode" terminfo |
| 280 |
definition to only claim 8 colour support or use "TERM=rxvt", which |
| 281 |
will fix colours but keep you from using other rxvt-unicode |
| 282 |
features. |
| 283 |
|
| 284 |
I am on FreeBSD and rxvt-unicode does not seem to work at all. |
| 285 |
Rxvt-unicode requires the symbol "__STDC_ISO_10646__" to be defined |
| 286 |
in your compile environment, or an implementation that implements |
| 287 |
it, wether it defines the symbol or not. "__STDC_ISO_10646__" |
| 288 |
requires that wchar_t is represented as unicode. |
| 289 |
|
| 290 |
As you might have guessed, FreeBSD does neither define this symobl |
| 291 |
nor does it support it. Instead, it uses it's own internal |
| 292 |
representation of wchar_t. This is, of course, completely fine with |
| 293 |
respect to standards. |
| 294 |
|
| 295 |
However, that means rxvt-unicode only works in "POSIX", "ISO-8859-1" |
| 296 |
and "UTF-8" locales under FreeBSD (which all use Unicode as wchar_t. |
| 297 |
|
| 298 |
"__STDC_ISO_10646__" is the only sane way to support multi-language |
| 299 |
apps in an OS, as using a locale-dependent (and non-standardized) |
| 300 |
representation of wchar_t makes it impossible to convert between |
| 301 |
wchar_t (as used by X11 and your applications) and any other |
| 302 |
encoding without implementing OS-specific-wrappers for each and |
| 303 |
every locale. There simply are no APIs to convert wchar_t into |
| 304 |
anything except the current locale encoding. |
| 305 |
|
| 306 |
Some applications (such as the formidable mlterm) work around this |
| 307 |
by carrying their own replacement functions for character set |
| 308 |
handling with them, and either implementing OS-dependent hacks or |
| 309 |
doing multiple conversions (which is slow and unreliable in case the |
| 310 |
OS implements encodings slightly different than the terminal |
| 311 |
emulator). |
| 312 |
|
| 313 |
The rxvt-unicode author insists that the right way to fix this is in |
| 314 |
the system libraries once and for all, instead of forcing every app |
| 315 |
to carry complete replacements for them :) |
| 316 |
|
| 317 |
I use Solaris 9 and it doesn't compile/work/etc. |
| 318 |
Try the diff in doc/solaris9.patch as a base. It fixes the worst |
| 319 |
problems with "wcwidth" and a compile problem. |
| 320 |
|
| 321 |
How can I use rxvt-unicode under cygwin? |
| 322 |
rxvt-unicode should compile and run out of the box on cygwin, using |
| 323 |
the X11 libraries that come with cygwin. libW11 emulation is no |
| 324 |
longer supported (and makes no sense, either, as it only supported a |
| 325 |
single font). I recommend starting the X-server in "-multiwindow" or |
| 326 |
"-rootless" mode instead, which will result in similar look&feel as |
| 327 |
the old libW11 emulation. |
| 328 |
|
| 329 |
At the time of this writing, cygwin didn't seem to support any |
| 330 |
multi-byte encodings (you might try "LC_CTYPE=C-UTF-8"), so you are |
| 331 |
likely limited to 8-bit encodings. |
| 332 |
|
| 333 |
How does rxvt-unicode determine the encoding to use? |
| 334 |
Is there an option to switch encodings? |
| 335 |
Unlike some other terminals, rxvt-unicode has no encoding switch, |
| 336 |
and no specific "utf-8" mode, such as xterm. In fact, it doesn't |
| 337 |
even know about UTF-8 or any other encodings with respect to |
| 338 |
terminal I/O. |
| 339 |
|
| 340 |
The reasons is that there exists a perfectly fine mechanism for |
| 341 |
selecting the encoding, doing I/O and (most important) communicating |
| 342 |
this to all applications so everybody agrees on character properties |
| 343 |
such as width and code number. This mechanism is the *locale*. |
| 344 |
Applications not using that info will have problems (for example, |
| 345 |
"xterm" gets the width of characters wrong as it uses it's own, |
| 346 |
locale-independent table under all locales). |
| 347 |
|
| 348 |
Rxvt-unicode uses the "LC_CTYPE" locale category to select encoding. |
| 349 |
All programs doing the same (that is, most) will automatically agree |
| 350 |
in the interpretation of characters. |
| 351 |
|
| 352 |
Unfortunately, there is no system-independent way to select locales, |
| 353 |
nor is there a standard on how locale specifiers will look like. |
| 354 |
|
| 355 |
On most systems, the content of the "LC_CTYPE" environment variable |
| 356 |
contains an arbitrary string which corresponds to an |
| 357 |
already-installed locale. Common names for locales are |
| 358 |
"en_US.UTF-8", "de_DE.ISO-8859-15", "ja_JP.EUC-JP", i.e. |
| 359 |
"language_country.encoding", but other forms (i.e. "de" or "german") |
| 360 |
are also common. |
| 361 |
|
| 362 |
Rxvt-unicode ignores all other locale categories, and except for the |
| 363 |
encoding, ignores country or language-specific settings, i.e. |
| 364 |
"de_DE.UTF-8" and "ja_JP.UTF-8" are the normally same to |
| 365 |
rxvt-unicode. |
| 366 |
|
| 367 |
If you want to use a specific encoding you have to make sure you |
| 368 |
start rxvt-unicode with the correct "LC_CTYPE" category. |
| 369 |
|
| 370 |
Can I switch locales at runtime? |
| 371 |
Yes, using an escape sequence. Try something like this, which sets |
| 372 |
rxvt-unicode's idea of "LC_CTYPE". |
| 373 |
|
| 374 |
printf '\e]701;%s\007' ja_JP.SJIS |
| 375 |
|
| 376 |
See also the previous answer. |
| 377 |
|
| 378 |
Sometimes this capability is rather handy when you want to work in |
| 379 |
one locale (e.g. "de_DE.UTF-8") but some programs don't support it |
| 380 |
(e.g. UTF-8). For example, I use this script to start "xjdic", which |
| 381 |
first switches to a locale supported by xjdic and back later: |
| 382 |
|
| 383 |
printf '\e]701;%s\007' ja_JP.SJIS |
| 384 |
xjdic -js |
| 385 |
printf '\e]701;%s\007' de_DE.UTF-8 |
| 386 |
|
| 387 |
You can also use xterm's "luit" program, which usually works fine, |
| 388 |
except for some locales where character width differs between |
| 389 |
program- and rxvt-unicode-locales. |
| 390 |
|
| 391 |
Can I switch the fonts at runtime? |
| 392 |
Yes, using an escape sequence. Try something like this, which has |
| 393 |
the same effect as using the "-fn" switch, and takes effect |
| 394 |
immediately: |
| 395 |
|
| 396 |
printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic" |
| 397 |
|
| 398 |
This is useful if you e.g. work primarily with japanese (and prefer |
| 399 |
a japanese font), but you have to switch to chinese temporarily, |
| 400 |
where japanese fonts would only be in your way. |
| 401 |
|
| 402 |
You can think of this as a kind of manual ISO-2022 switching. |
| 403 |
|
| 404 |
Why do italic characters look as if clipped? |
| 405 |
Many fonts have difficulties with italic characters and hinting. For |
| 406 |
example, the otherwise very nicely hinted font "xft:Bitstream Vera |
| 407 |
Sans Mono" completely fails in it's italic face. A workaround might |
| 408 |
be to enable freetype autohinting, i.e. like this: |
| 409 |
|
| 410 |
URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true |
| 411 |
URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true |
| 412 |
|
| 413 |
My input method wants <some encoding> but I want UTF-8, what can I do? |
| 414 |
You can specify separate locales for the input method and the rest |
| 415 |
of the terminal, using the resource "imlocale": |
| 416 |
|
| 417 |
URxvt*imlocale: ja_JP.EUC-JP |
| 418 |
|
| 419 |
Now you can start your terminal with "LC_CTYPE=ja_JP.UTF-8" and |
| 420 |
still use your input method. Please note, however, that you will not |
| 421 |
be able to input characters outside "EUC-JP" in a normal way then, |
| 422 |
as your input method limits you. |
| 423 |
|
| 424 |
Rxvt-unicode crashes when the X Input Method changes or exits. |
| 425 |
Unfortunately, this is unavoidable, as the XIM protocol is racy by |
| 426 |
design. Applications can avoid some crashes at the expense of memory |
| 427 |
leaks, and Input Methods can avoid some crashes by careful ordering |
| 428 |
at exit time. kinput2 (and derived input methods) generally |
| 429 |
succeeds, while SCIM (or similar input methods) fails. In the end, |
| 430 |
however, crashes cannot be completely avoided even if both sides |
| 431 |
cooperate. |
| 432 |
|
| 433 |
So the only workaround is not to kill your Input Method Servers. |
| 434 |
|
| 435 |
Rxvt-unicode uses gobs of memory, how can I reduce that? |
| 436 |
Rxvt-unicode tries to obey the rule of not charging you for |
| 437 |
something you don't use. One thing you should try is to configure |
| 438 |
out all settings that you don't need, for example, Xft support is a |
| 439 |
resource hog by design, when used. Compiling it out ensures that no |
| 440 |
Xft font will be loaded accidentally when rxvt-unicode tries to find |
| 441 |
a font for your characters. |
| 442 |
|
| 443 |
Also, many people (me included) like large windows and even larger |
| 444 |
scrollback buffers: Without "--enable-unicode3", rxvt-unicode will |
| 445 |
use 6 bytes per screen cell. For a 160x?? window this amounts to |
| 446 |
almost a kilobyte per line. A scrollback buffer of 10000 lines will |
| 447 |
then (if full) use 10 Megabytes of memory. With "--enable-unicode3" |
| 448 |
it gets worse, as rxvt-unicode then uses 8 bytes per screen cell. |
| 449 |
|
| 450 |
Can I speed up Xft rendering somehow? |
| 451 |
Yes, the most obvious way to speed it up is to avoid Xft entirely, |
| 452 |
as it is simply slow. If you still want Xft fonts you might try to |
| 453 |
disable antialiasing (by appending ":antialias=false"), which saves |
| 454 |
lots of memory and also speeds up rendering considerably. |
| 455 |
|
| 456 |
Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong? |
| 457 |
Rxvt-unicode will use whatever you specify as a font. If it needs to |
| 458 |
fall back to it's default font search list it will prefer X11 core |
| 459 |
fonts, because they are small and fast, and then use Xft fonts. It |
| 460 |
has antialiasing disabled for most of them, because the author |
| 461 |
thinks they look best that way. |
| 462 |
|
| 463 |
If you want antialiasing, you have to specify the fonts manually. |
| 464 |
|
| 465 |
Mouse cut/paste suddenly no longer works. |
| 466 |
Make sure that mouse reporting is actually turned off since killing |
| 467 |
some editors prematurely may leave the mouse in mouse report mode. |
| 468 |
I've heard that tcsh may use mouse reporting unless it otherwise |
| 469 |
specified. A quick check is to see if cut/paste works when the Alt |
| 470 |
or Shift keys are depressed. See rxvt(7) |
| 471 |
|
| 472 |
What's with this bold/blink stuff? |
| 473 |
If no bold colour is set via "colorBD:", bold will invert text using |
| 474 |
the standard foreground colour. |
| 475 |
|
| 476 |
For the standard background colour, blinking will actually make the |
| 477 |
text blink when compiled with "--enable-blinking". with standard |
| 478 |
colours. Without "--enable-blinking", the blink attribute will be |
| 479 |
ignored. |
| 480 |
|
| 481 |
On ANSI colours, bold/blink attributes are used to set |
| 482 |
high-intensity foreground/background colors. |
| 483 |
|
| 484 |
color0-7 are the low-intensity colors. |
| 485 |
|
| 486 |
color8-15 are the corresponding high-intensity colors. |
| 487 |
|
| 488 |
I don't like the screen colors. How do I change them? |
| 489 |
You can change the screen colors at run-time using ~/.Xdefaults |
| 490 |
resources (or as long-options). |
| 491 |
|
| 492 |
Here are values that are supposed to resemble a VGA screen, |
| 493 |
including the murky brown that passes for low-intensity yellow: |
| 494 |
|
| 495 |
URxvt.color0: #000000 |
| 496 |
URxvt.color1: #A80000 |
| 497 |
URxvt.color2: #00A800 |
| 498 |
URxvt.color3: #A8A800 |
| 499 |
URxvt.color4: #0000A8 |
| 500 |
URxvt.color5: #A800A8 |
| 501 |
URxvt.color6: #00A8A8 |
| 502 |
URxvt.color7: #A8A8A8 |
| 503 |
|
| 504 |
URxvt.color8: #000054 |
| 505 |
URxvt.color9: #FF0054 |
| 506 |
URxvt.color10: #00FF54 |
| 507 |
URxvt.color11: #FFFF54 |
| 508 |
URxvt.color12: #0000FF |
| 509 |
URxvt.color13: #FF00FF |
| 510 |
URxvt.color14: #00FFFF |
| 511 |
URxvt.color15: #FFFFFF |
| 512 |
|
| 513 |
And here is a more complete set of non-standard colors described |
| 514 |
(not by me) as "pretty girly". |
| 515 |
|
| 516 |
URxvt.cursorColor: #dc74d1 |
| 517 |
URxvt.pointerColor: #dc74d1 |
| 518 |
URxvt.background: #0e0e0e |
| 519 |
URxvt.foreground: #4ad5e1 |
| 520 |
URxvt.color0: #000000 |
| 521 |
URxvt.color8: #8b8f93 |
| 522 |
URxvt.color1: #dc74d1 |
| 523 |
URxvt.color9: #dc74d1 |
| 524 |
URxvt.color2: #0eb8c7 |
| 525 |
URxvt.color10: #0eb8c7 |
| 526 |
URxvt.color3: #dfe37e |
| 527 |
URxvt.color11: #dfe37e |
| 528 |
URxvt.color5: #9e88f0 |
| 529 |
URxvt.color13: #9e88f0 |
| 530 |
URxvt.color6: #73f7ff |
| 531 |
URxvt.color14: #73f7ff |
| 532 |
URxvt.color7: #e1dddd |
| 533 |
URxvt.color15: #e1dddd |
| 534 |
|
| 535 |
How can I start rxvtd in a race-free way? |
| 536 |
Try "rxvtd -f -o", which tells rxvtd to open the display, create the |
| 537 |
listening socket and then fork. |
| 538 |
|
| 539 |
What's with the strange Backspace/Delete key behaviour? |
| 540 |
Assuming that the physical Backspace key corresponds to the |
| 541 |
BackSpace keysym (not likely for Linux ... see the following |
| 542 |
question) there are two standard values that can be used for |
| 543 |
Backspace: "^H" and "^?". |
| 544 |
|
| 545 |
Historically, either value is correct, but rxvt-unicode adopts the |
| 546 |
debian policy of using "^?" when unsure, because it's the one only |
| 547 |
only correct choice :). |
| 548 |
|
| 549 |
Rxvt-unicode tries to inherit the current stty settings and uses the |
| 550 |
value of `erase' to guess the value for backspace. If rxvt-unicode |
| 551 |
wasn't started from a terminal (say, from a menu or by remote |
| 552 |
shell), then the system value of `erase', which corresponds to |
| 553 |
CERASE in <termios.h>, will be used (which may not be the same as |
| 554 |
your stty setting). |
| 555 |
|
| 556 |
For starting a new rxvt-unicode: |
| 557 |
|
| 558 |
# use Backspace = ^H |
| 559 |
$ stty erase ^H |
| 560 |
$ rxvt |
| 561 |
|
| 562 |
# use Backspace = ^? |
| 563 |
$ stty erase ^? |
| 564 |
$ rxvt |
| 565 |
|
| 566 |
Toggle with "ESC [ 36 h" / "ESC [ 36 l" as documented in rxvt(7). |
| 567 |
|
| 568 |
For an existing rxvt-unicode: |
| 569 |
|
| 570 |
# use Backspace = ^H |
| 571 |
$ stty erase ^H |
| 572 |
$ echo -n "^[[36h" |
| 573 |
|
| 574 |
# use Backspace = ^? |
| 575 |
$ stty erase ^? |
| 576 |
$ echo -n "^[[36l" |
| 577 |
|
| 578 |
This helps satisfy some of the Backspace discrepancies that occur, |
| 579 |
but if you use Backspace = "^H", make sure that the termcap/terminfo |
| 580 |
value properly reflects that. |
| 581 |
|
| 582 |
The Delete key is a another casualty of the ill-defined Backspace |
| 583 |
problem. To avoid confusion between the Backspace and Delete keys, |
| 584 |
the Delete key has been assigned an escape sequence to match the |
| 585 |
vt100 for Execute ("ESC [ 3 ~") and is in the supplied |
| 586 |
termcap/terminfo. |
| 587 |
|
| 588 |
Some other Backspace problems: |
| 589 |
|
| 590 |
some editors use termcap/terminfo, some editors (vim I'm told) |
| 591 |
expect Backspace = ^H, GNU Emacs (and Emacs-like editors) use ^H for |
| 592 |
help. |
| 593 |
|
| 594 |
Perhaps someday this will all be resolved in a consistent manner. |
| 595 |
|
| 596 |
I don't like the key-bindings. How do I change them? |
| 597 |
There are some compile-time selections available via configure. |
| 598 |
Unless you have run "configure" with the "--disable-resources" |
| 599 |
option you can use the `keysym' resource to alter the keystrings |
| 600 |
associated with keysyms. |
| 601 |
|
| 602 |
Here's an example for a URxvt session started using "rxvt -name |
| 603 |
URxvt" |
| 604 |
|
| 605 |
URxvt.keysym.Home: \033[1~ |
| 606 |
URxvt.keysym.End: \033[4~ |
| 607 |
URxvt.keysym.C-apostrophe: \033<C-'> |
| 608 |
URxvt.keysym.C-slash: \033<C-/> |
| 609 |
URxvt.keysym.C-semicolon: \033<C-;> |
| 610 |
URxvt.keysym.C-grave: \033<C-`> |
| 611 |
URxvt.keysym.C-comma: \033<C-,> |
| 612 |
URxvt.keysym.C-period: \033<C-.> |
| 613 |
URxvt.keysym.C-0x60: \033<C-`> |
| 614 |
URxvt.keysym.C-Tab: \033<C-Tab> |
| 615 |
URxvt.keysym.C-Return: \033<C-Return> |
| 616 |
URxvt.keysym.S-Return: \033<S-Return> |
| 617 |
URxvt.keysym.S-space: \033<S-Space> |
| 618 |
URxvt.keysym.M-Up: \033<M-Up> |
| 619 |
URxvt.keysym.M-Down: \033<M-Down> |
| 620 |
URxvt.keysym.M-Left: \033<M-Left> |
| 621 |
URxvt.keysym.M-Right: \033<M-Right> |
| 622 |
URxvt.keysym.M-C-0: list \033<M-C- 0123456789 > |
| 623 |
URxvt.keysym.M-C-a: list \033<M-C- abcdefghijklmnopqrstuvwxyz > |
| 624 |
URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007 |
| 625 |
|
| 626 |
See some more examples in the documentation for the keysym resource. |
| 627 |
|
| 628 |
I'm using keyboard model XXX that has extra Prior/Next/Insert keys. How |
| 629 |
do I make use of them? For example, the Sun Keyboard type 4 has the |
| 630 |
following mappings that rxvt-unicode doesn't recognize. |
| 631 |
KP_Insert == Insert |
| 632 |
F22 == Print |
| 633 |
F27 == Home |
| 634 |
F29 == Prior |
| 635 |
F33 == End |
| 636 |
F35 == Next |
| 637 |
|
| 638 |
Rather than have rxvt-unicode try to accommodate all the various |
| 639 |
possible keyboard mappings, it is better to use `xmodmap' to remap |
| 640 |
the keys as required for your particular machine. |
| 641 |
|
| 642 |
How do I distinguish wether I'm running rxvt-unicode or a regular xterm? |
| 643 |
I need this to decide about setting colors etc. |
| 644 |
rxvt and rxvt-unicode always export the variable "COLORTERM", so you |
| 645 |
can check and see if that is set. Note that several programs, JED, |
| 646 |
slrn, Midnight Commander automatically check this variable to decide |
| 647 |
whether or not to use color. |
| 648 |
|
| 649 |
How do I set the correct, full IP address for the DISPLAY variable? |
| 650 |
If you've compiled rxvt-unicode with DISPLAY_IS_IP and have enabled |
| 651 |
insecure mode then it is possible to use the following shell script |
| 652 |
snippets to correctly set the display. If your version of |
| 653 |
rxvt-unicode wasn't also compiled with ESCZ_ANSWER (as assumed in |
| 654 |
these snippets) then the COLORTERM variable can be used to |
| 655 |
distinguish rxvt-unicode from a regular xterm. |
| 656 |
|
| 657 |
Courtesy of Chuck Blake <cblake@BBN.COM> with the following shell |
| 658 |
script snippets: |
| 659 |
|
| 660 |
# Bourne/Korn/POSIX family of shells: |
| 661 |
[ ${TERM:-foo} = foo ] && TERM=xterm # assume an xterm if we don't know |
| 662 |
if [ ${TERM:-foo} = xterm ]; then |
| 663 |
stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not |
| 664 |
echo -n '^[Z' |
| 665 |
read term_id |
| 666 |
stty icanon echo |
| 667 |
if [ ""${term_id} = '^[[?1;2C' -a ${DISPLAY:-foo} = foo ]; then |
| 668 |
echo -n '^[[7n' # query the rxvt we are in for the DISPLAY string |
| 669 |
read DISPLAY # set it in our local shell |
| 670 |
fi |
| 671 |
fi |
| 672 |
|
| 673 |
How do I compile the manual pages for myself? |
| 674 |
You need to have a recent version of perl installed as |
| 675 |
/usr/bin/perl, one that comes with pod2man, pod2text and pod2html. |
| 676 |
Then go to the doc subdirectory and enter "make alldoc". |
| 677 |
|
| 678 |
My question isn't answered here, can I ask a human? |
| 679 |
Before sending me mail, you could go to IRC: "irc.freenode.net", |
| 680 |
channel "#rxvt-unicode" has some rxvt-unicode enthusiasts that might |
| 681 |
be interested in learning about new and exciting problems (but not |
| 682 |
FAQs :). |
| 683 |
|
