ViewVC Help
View File | Revision Log | Show Annotations | Download File
/cvs/rxvt-unicode/README.FAQ
(Generate patch)

Comparing rxvt-unicode/README.FAQ (file contents):
Revision 1.2 by root, Sun Jan 16 15:59:45 2005 UTC vs.
Revision 1.18 by root, Tue Nov 8 17:35:28 2005 UTC

1FREQUENTLY ASKED QUESTIONS 1FREQUENTLY ASKED QUESTIONS
2 How do I know which rxvt-unicode version I'm using? 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 3 The version number is displayed with the usage (-h). Also the escape
4 sequence "ESC[8n" sets the window title to the version number. 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.
5 20
6 When I log-in to another system it tells me about missing terminfo data? 21 When I log-in to another system it tells me about missing terminfo data?
7 The terminal description used by rxvt-unicode is not as widely 22 The terminal description used by rxvt-unicode is not as widely
8 available as that for xterm, or even rxvt (for which the same 23 available as that for xterm, or even rxvt (for which the same
9 problem often arises). 24 problem often arises).
… …
21 problems arising, which includes wrong keymapping, less and 36 problems arising, which includes wrong keymapping, less and
22 different colours and some refresh errors in fullscreen 37 different colours and some refresh errors in fullscreen
23 applications. It's a nice quick-and-dirty workaround for rare cases, 38 applications. It's a nice quick-and-dirty workaround for rare cases,
24 though. 39 though.
25 40
26 If you always want to do this you can either recompile rxvt-unicode 41 If you always want to do this (and are fine with the consequences)
27 with the desired TERM value or use a resource to set it: 42 you can either recompile rxvt-unicode with the desired TERM value or
43 use a resource to set it:
28 44
29 URxvt.termName: rxvt 45 URxvt.termName: rxvt
30 46
31 If you don't plan to use rxvt (quite common...) you could also 47 If you don't plan to use rxvt (quite common...) you could also
32 replace the rxvt terminfo file with the rxvt-unicode one. 48 replace the rxvt terminfo file with the rxvt-unicode one.
33 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 urxvt.
34 I need a termcap file entry. 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
35 You could use rxvt's termcap entry with resonable results in many 61 You could use rxvt's termcap entry with resonable results in many
36 cases. You can also create a termcap entry by using terminfo's 62 cases. You can also create a termcap entry by using terminfo's
37 infocmp program like this: 63 infocmp program like this:
38 64
39 infocmp -C rxvt-unicode 65 infocmp -C rxvt-unicode
40 66
41 OR you could this termcap entry: 67 Or you could use this termcap entry, generated by the command above:
42 68
43 rxvt-unicode|rxvt-unicode terminal (X Window System):\ 69 rxvt-unicode|rxvt-unicode terminal (X Window System):\
44 :am:bw:eo:km:mi:ms:xn:xo:\ 70 :am:bw:eo:km:mi:ms:xn:xo:\
45 :co#80:it#8:li#24:\ 71 :co#80:it#8:li#24:lm#0:\
46 :AL=\E[%dL:DC=\E[%dP:DL=\E[%dM:DO=\E[%dB:IC=\E[%d@:\ 72 :AL=\E[%dL:DC=\E[%dP:DL=\E[%dM:DO=\E[%dB:IC=\E[%d@:\
47 :K1=\EOw:K2=\EOu:K3=\EOy:K4=\EOq:K5=\EOs:LE=\E[%dD:\ 73 :K1=\EOw:K2=\EOu:K3=\EOy:K4=\EOq:K5=\EOs:LE=\E[%dD:\
48 :RI=\E[%dC:SF=\E[%dS:SR=\E[%dT:UP=\E[%dA:ae=^O:al=\E[L:\ 74 :RI=\E[%dC:SF=\E[%dS:SR=\E[%dT:UP=\E[%dA:ae=\E(B:al=\E[L:\
49 :as=^N:bl=^G:cd=\E[J:ce=\E[K:cl=\E[H\E[2J:cm=\E[%i%d;%dH:\ 75 :as=\E(0:bl=^G:cd=\E[J:ce=\E[K:cl=\E[H\E[2J:\
50 :cr=^M:cs=\E[%i%d;%dr:ct=\E[3g:dc=\E[P:dl=\E[M:do=^J:\ 76 :cm=\E[%i%d;%dH:cr=^M:cs=\E[%i%d;%dr:ct=\E[3g:dc=\E[P:\
51 :ec=\E[%dX:ei=\E[4l:ho=\E[H:i1=\E[?47l\E=\E[?1l:ic=\E[@:\ 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:\
52 :im=\E[4h:is=\E[r\E[m\E[2J\E[H\E[?7h\E[?1;3;4;6l\E[4l:\ 79 :is=\E[r\E[m\E[2J\E[H\E[?7h\E[?1;3;4;6l\E[4l:\
53 :k0=\E[21~:k1=\E[11~:k2=\E[12~:k3=\E[13~:k4=\E[14~:\ 80 :k1=\E[11~:k2=\E[12~:k3=\E[13~:k4=\E[14~:k5=\E[15~:\
54 :k5=\E[15~:k6=\E[17~:k7=\E[18~:k8=\E[19~:k9=\E[20~:\ 81 :k6=\E[17~:k7=\E[18~:k8=\E[19~:k9=\E[20~:kD=\E[3~:\
55 :kD=\E[3~:kI=\E[2~:kN=\E[6~:kP=\E[5~:kb=\177:kd=\EOB:\ 82 :kI=\E[2~:kN=\E[6~:kP=\E[5~:kb=\177:kd=\EOB:ke=\E[?1l\E>:\
56 :ke=\E[?1l\E>:kh=\E[7~:kl=\EOD:kr=\EOC:ks=\E[?1h\E=:\ 83 :kh=\E[7~:kl=\EOD:kr=\EOC:ks=\E[?1h\E=:ku=\EOA:le=^H:\
57 :ku=\EOA:le=^H:mb=\E[5m:md=\E[1m:me=\E[m\017:mr=\E[7m:\ 84 :mb=\E[5m:md=\E[1m:me=\E[m\017:mr=\E[7m:nd=\E[C:rc=\E8:\
58 :nd=\E[C:rc=\E8:sc=\E7:se=\E[27m:sf=^J:so=\E[7m:sr=\EM:\ 85 :sc=\E7:se=\E[27m:sf=^J:so=\E[7m:sr=\EM:st=\EH:ta=^I:\
59 :st=\EH:ta=^I:te=\E[r\E[?1049l:ti=\E[?1049h:ue=\E[24m:\ 86 :te=\E[r\E[?1049l:ti=\E[?1049h:ue=\E[24m:up=\E[A:\
60 :up=\E[A:us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\ 87 :us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\
61 :vs=\E[?25h: 88 :vs=\E[?25h:
62 89
63 Why does "ls" no longer have coloured output? 90 Why does "ls" no longer have coloured output?
64 The "ls" in the GNU coreutils unfortunately doesn't use terminfo to 91 The "ls" in the GNU coreutils unfortunately doesn't use terminfo to
65 decide wether a terminal has colour, but uses it's own configuration 92 decide wether a terminal has colour, but uses it's own configuration
… …
84 furthermore fail to even install the "rxvt-unicode" terminfo file, 111 furthermore fail to even install the "rxvt-unicode" terminfo file,
85 so you will need to install it on your own (See the question When I 112 so you will need to install it on your own (See the question When I
86 log-in to another system it tells me about missing terminfo data? on 113 log-in to another system it tells me about missing terminfo data? on
87 how to do this). 114 how to do this).
88 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
89 Rxvt-unicode does not seem to understand the selected encoding? 124 Rxvt-unicode does not seem to understand the selected encoding?
90 Unicode does not seem to work? 125 Unicode does not seem to work?
91 If you encounter strange problems like typing an accented character 126 If you encounter strange problems like typing an accented character
92 but getting two unrelated other characters or similar, or if program 127 but getting two unrelated other characters or similar, or if program
93 output is subtly garbled, then you should check your locale 128 output is subtly garbled, then you should check your locale
94 settings. 129 settings.
95 130
96 Rxvt-unicode must be started with the same "LC_CTYPE" setting as the 131 Rxvt-unicode must be started with the same "LC_CTYPE" setting as the
97 programs. Often rxvt-unicode is started in the "C" locale, while the 132 programs. Often rxvt-unicode is started in the "C" locale, while the
98 login script running within the rxvt-unicode window changes the 133 login script running within the rxvt-unicode window changes the
99 locale to sth. else, e.h. "en_GB.UTF-8". Needless to say, this is 134 locale to something else, e.g. "en_GB.UTF-8". Needless to say, this
100 not going to work. 135 is not going to work.
101 136
102 The best thing is to fix your startup environment, as you will 137 The best thing is to fix your startup environment, as you will
103 likely run into other problems. If nothing works you can try this in 138 likely run into other problems. If nothing works you can try this in
104 your .profile. 139 your .profile.
105 140
106 printf '\e]701;%s\007' "$LC_CTYPE" 141 printf '\e]701;%s\007' "$LC_CTYPE"
107 142
108 If this doesn't work, then maybe you use a "LC_CTYPE" specification 143 If this doesn't work, then maybe you use a "LC_CTYPE" specification
109 not supported on your systems. Some systems have a "locale" command 144 not supported on your systems. Some systems have a "locale" command
110 which displays this. If it displays sth. like: 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:
111 148
112 locale: Cannot set LC_CTYPE to default locale: ... 149 locale: Cannot set LC_CTYPE to default locale: ...
113 150
114 Then the locale you specified is not supported on your system. 151 Then the locale you specified is not supported on your system.
115 152
… …
123 Chances are that the font you (or the admin/package maintainer of 160 Chances are that the font you (or the admin/package maintainer of
124 your system/os) have specified does not cover all the characters you 161 your system/os) have specified does not cover all the characters you
125 want to display. 162 want to display.
126 163
127 rxvt-unicode makes a best-effort try at finding a replacement font. 164 rxvt-unicode makes a best-effort try at finding a replacement font.
128 Often the result is fine, but sometimes the chosen font looks bad. 165 Often the result is fine, but sometimes the chosen font looks
129 Many fonts have totally strange characters that don't resemble the 166 bad/ugly/wrong. Some fonts have totally strange characters that
130 correct glyph at all, and rxvt-unicode lacks the artificial 167 don't resemble the correct glyph at all, and rxvt-unicode lacks the
131 intelligence to detect that a specific glyph is wrong: it has to 168 artificial intelligence to detect that a specific glyph is wrong: it
132 believe the font that the characters it contains indeed look 169 has to believe the font that the characters it claims to contain
133 correct. 170 indeed look correct.
134 171
135 In that case, select a font of your taste and add it to the font 172 In that case, select a font of your taste and add it to the font
136 list, e.g.: 173 list, e.g.:
137 174
138 rxvt -fn basefont,font2,font3... 175 urxvt -fn basefont,font2,font3...
139 176
140 When rxvt-unicode sees a character, it will first look at the base 177 When rxvt-unicode sees a character, it will first look at the base
141 font. If the base font does not contain the character, it will go to 178 font. If the base font does not contain the character, it will go to
142 the next font, and so on. Specifying your own fonts will also speed 179 the next font, and so on. Specifying your own fonts will also speed
143 up this search and use less resources within rxvt-unicode and the 180 up this search and use less resources within rxvt-unicode and the
144 X-server. 181 X-server.
145 182
146 The only limitation is that all the fonts must not be larger than 183 The only limitation is that none of the fonts may be larger than the
147 the base font, as the base font defines the principal cell size, 184 base font, as the base font defines the terminal character cell
148 which must be the same due to the way terminals work. 185 size, which must be the same due to the way terminals work.
149 186
150 Why do some chinese characters look so different than others? 187 Why do some chinese characters look so different than others?
151 This is because there is a difference between script and language -- 188 This is because there is a difference between script and language --
152 rxvt-unicode does not know which language the text that is output 189 rxvt-unicode does not know which language the text that is output
153 is, as it only knows the unicode character codes. If rxvt-unicode 190 is, as it only knows the unicode character codes. If rxvt-unicode
154 first sees a japanese character, it might choose a japanese font for 191 first sees a japanese/chinese character, it might choose a japanese
155 it. Subsequent japanese characters will take that font. Now, many 192 font for display. Subsequent japanese characters will use that font.
156 chinese characters aren't represented in japanese fonts, so when the 193 Now, many chinese characters aren't represented in japanese fonts,
157 first non-japanese character comes up, rxvt-unicode will look for a 194 so when the first non-japanese character comes up, rxvt-unicode will
158 chinese font -- unfortunately at this point, it will still use the 195 look for a chinese font -- unfortunately at this point, it will
159 japanese font for japanese characters that are also chinese. 196 still use the japanese font for chinese characters that are also in
197 the japanese font.
160 198
161 The workaround is easy: just tag a chinese font at the end of your 199 The workaround is easy: just tag a chinese font at the end of your
162 font list (see the previous question). The key is to view the font 200 font list (see the previous question). The key is to view the font
163 list as a preference list: If you expect more japanese, list a 201 list as a preference list: If you expect more japanese, list a
164 japanese font first. If you expect more chinese, put a chinese font 202 japanese font first. If you expect more chinese, put a chinese font
165 first. 203 first.
166 204
167 In the future it might be possible to switch preferences at runtime 205 In the future it might be possible to switch language preferences at
168 (the internal data structure has no problem with using different 206 runtime (the internal data structure has no problem with using
169 fonts for the same character at the same time, but no interface for 207 different fonts for the same character at the same time, but no
170 this has been designed yet). 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).
171 212
172 Why does rxvt-unicode sometimes leave pixel droppings? 213 Why does rxvt-unicode sometimes leave pixel droppings?
173 Most fonts were not designed for terminal use, which means that 214 Most fonts were not designed for terminal use, which means that
174 character size varies a lot. A font that is otherwise fine for 215 character size varies a lot. A font that is otherwise fine for
175 terminal use might contain some characters that are simply too wide. 216 terminal use might contain some characters that are simply too wide.
… …
189 that doesn't work, you might be forced to use a different font. 230 that doesn't work, you might be forced to use a different font.
190 231
191 All of this is not a problem when using X11 core fonts, as their 232 All of this is not a problem when using X11 core fonts, as their
192 bounding box data is correct. 233 bounding box data is correct.
193 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
194 My Compose (Multi_key) key is no longer working. 242 My Compose (Multi_key) key is no longer working.
195 The most common causes for this are that either your locale is not 243 The most common causes for this are that either your locale is not
196 set correctly, or you specified a preeditStyle that is not supported 244 set correctly, or you specified a preeditStyle that is not supported
197 by your input method. For example, if you specified OverTheSpot and 245 by your input method. For example, if you specified OverTheSpot and
198 your input method (e.g. the default input method handling Compose 246 your input method (e.g. the default input method handling Compose
… …
209 advantage, typing <Ctrl-Shift-0> to get a ASCII NUL. This works for 257 advantage, typing <Ctrl-Shift-0> to get a ASCII NUL. This works for
210 other codes, too, such as "Ctrl-Shift-1-d" to type the default 258 other codes, too, such as "Ctrl-Shift-1-d" to type the default
211 telnet escape character and so on. 259 telnet escape character and so on.
212 260
213 How can I keep rxvt-unicode from using reverse video so much? 261 How can I keep rxvt-unicode from using reverse video so much?
214 First of all, make sure you are running with the right terminfo 262 First of all, make sure you are running with the right terminal
215 ("urxvt"), which will get rid of most of these effects. Then make 263 settings ("TERM=rxvt-unicode"), which will get rid of most of these
216 sure you have specified colours for italic and bold, as otherwise 264 effects. Then make sure you have specified colours for italic and
217 rxvt-unicode might use reverse video to simulate the effect: 265 bold, as otherwise rxvt-unicode might use reverse video to simulate
266 the effect:
218 267
219 URxvt*colorBD: white 268 URxvt.colorBD: white
220 URxvt*colorIT: green 269 URxvt.colorIT: green
221 270
222 Some programs assume totally weird colours (red instead of blue), how 271 Some programs assume totally weird colours (red instead of blue), how
223 can I fix that? 272 can I fix that?
224 For some unexplainable reason, some programs (i.e. irssi) assume a 273 For some unexplainable reason, some rare programs assume a very
225 very weird colour palette when confronted with a terminal with more 274 weird colour palette when confronted with a terminal with more than
226 than the standard 8 colours (rxvt-unicode supports 88). The right 275 the standard 8 colours (rxvt-unicode supports 88). The right fix is,
227 fix is, of course, to fix these programs not to assume non-ISO 276 of course, to fix these programs not to assume non-ISO colours
228 colours without very good reasons. 277 without very good reasons.
229 278
230 In the meantime, you can either edit your "urxvt" terminfo 279 In the meantime, you can either edit your "rxvt-unicode" terminfo
231 definition to only claim 8 colour support or use "TERM=rxvt", which 280 definition to only claim 8 colour support or use "TERM=rxvt", which
232 will fix colours but keep you from using other rxvt-unicode 281 will fix colours but keep you from using other rxvt-unicode
233 features. 282 features.
234 283
235 I am on FreeBSD and rxvt-unicode does not seem to work at all. 284 I am on FreeBSD and rxvt-unicode does not seem to work at all.
… …
238 it, wether it defines the symbol or not. "__STDC_ISO_10646__" 287 it, wether it defines the symbol or not. "__STDC_ISO_10646__"
239 requires that wchar_t is represented as unicode. 288 requires that wchar_t is represented as unicode.
240 289
241 As you might have guessed, FreeBSD does neither define this symobl 290 As you might have guessed, FreeBSD does neither define this symobl
242 nor does it support it. Instead, it uses it's own internal 291 nor does it support it. Instead, it uses it's own internal
243 representation of wchar_t. This is, of course, completely legal. 292 representation of wchar_t. This is, of course, completely fine with
293 respect to standards.
244 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
245 However, "__STDC_ISO_10646__" is the only sane way to support 298 "__STDC_ISO_10646__" is the only sane way to support multi-language
246 multi-language apps in an OS, as using a locale-dependent (and 299 apps in an OS, as using a locale-dependent (and non-standardized)
247 non-standardized) representation of wchar_t makes it impossible to 300 representation of wchar_t makes it impossible to convert between
248 convert between wchar_t (as used by X11 and your applications) and 301 wchar_t (as used by X11 and your applications) and any other
249 any other encoding without implementing OS-specific-wrappers for 302 encoding without implementing OS-specific-wrappers for each and
250 each and every locale. There simply are no APIs to convert wchar_t 303 every locale. There simply are no APIs to convert wchar_t into
251 into anything except the current locale encoding. 304 anything except the current locale encoding.
252 305
253 Some applications (such as the formidable mlterm) work around this 306 Some applications (such as the formidable mlterm) work around this
254 by carrying their own replacement functions for character set 307 by carrying their own replacement functions for character set
255 handling with them, and either implementing OS-dependent hacks or 308 handling with them, and either implementing OS-dependent hacks or
256 doing multiple conversions (which is slow and unreliable in case the 309 doing multiple conversions (which is slow and unreliable in case the
257 OS implements encodings slightly different than the terminal 310 OS implements encodings slightly different than the terminal
258 emulator). 311 emulator).
259 312
260 The rxvt-unicode author insists that the right way to fix this is in 313 The rxvt-unicode author insists that the right way to fix this is in
261 the system libraries once and for all, instead of forcing every app 314 the system libraries once and for all, instead of forcing every app
262 to carry complete replacements. 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.
263 332
264 How does rxvt-unicode determine the encoding to use? 333 How does rxvt-unicode determine the encoding to use?
265 Is there an option to switch encodings? 334 Is there an option to switch encodings?
266 Unlike some other terminals, rxvt-unicode has no encoding switch, 335 Unlike some other terminals, rxvt-unicode has no encoding switch,
267 and no specific "utf-8" mode, such as xterm. In fact, it doesn't 336 and no specific "utf-8" mode, such as xterm. In fact, it doesn't
… …
270 339
271 The reasons is that there exists a perfectly fine mechanism for 340 The reasons is that there exists a perfectly fine mechanism for
272 selecting the encoding, doing I/O and (most important) communicating 341 selecting the encoding, doing I/O and (most important) communicating
273 this to all applications so everybody agrees on character properties 342 this to all applications so everybody agrees on character properties
274 such as width and code number. This mechanism is the *locale*. 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).
275 347
276 Rxvt-unicode uses the "LC_CTYPE" locale category to select encoding. 348 Rxvt-unicode uses the "LC_CTYPE" locale category to select encoding.
277 All programs doing the same (that is, most) will automatically agree 349 All programs doing the same (that is, most) will automatically agree
278 in the interpretation of characters. 350 in the interpretation of characters.
279 351
… …
287 "language_country.encoding", but other forms (i.e. "de" or "german") 359 "language_country.encoding", but other forms (i.e. "de" or "german")
288 are also common. 360 are also common.
289 361
290 Rxvt-unicode ignores all other locale categories, and except for the 362 Rxvt-unicode ignores all other locale categories, and except for the
291 encoding, ignores country or language-specific settings, i.e. 363 encoding, ignores country or language-specific settings, i.e.
292 "de_DE.UTF-8" and "ja_JP.UTF-8" are the same for rxvt-unicode. 364 "de_DE.UTF-8" and "ja_JP.UTF-8" are the normally same to
365 rxvt-unicode.
293 366
294 If you want to use a specific encoding you have to make sure you 367 If you want to use a specific encoding you have to make sure you
295 start rxvt-unicode with the correct "LC_CTYPE" category. 368 start rxvt-unicode with the correct "LC_CTYPE" category.
296 369
297 Can I switch locales at runtime? 370 Can I switch locales at runtime?
298 Yes, using an escape sequence. Try sth. like this, which sets 371 Yes, using an escape sequence. Try something like this, which sets
299 rxvt-unicode's idea of "LC_CTYPE". 372 rxvt-unicode's idea of "LC_CTYPE".
300 373
301 printf '\e]701;%s\007' ja_JP.SJIS 374 printf '\e]701;%s\007' ja_JP.SJIS
302 375
303 See also the previous question. 376 See also the previous answer.
304 377
305 Sometimes this capability is rather handy when you want to work in 378 Sometimes this capability is rather handy when you want to work in
306 one locale (e.g. "de_DE.UTF-8") but some programs don't support 379 one locale (e.g. "de_DE.UTF-8") but some programs don't support it
307 UTF-8. For example, I use this script to start "xjdic", which first 380 (e.g. UTF-8). For example, I use this script to start "xjdic", which
308 switches to a locale supported by xjdic and back later: 381 first switches to a locale supported by xjdic and back later:
309 382
310 printf '\e]701;%s\007' ja_JP.SJIS 383 printf '\e]701;%s\007' ja_JP.SJIS
311 xjdic -js 384 xjdic -js
312 printf '\e]701;%s\007' de_DE.UTF-8 385 printf '\e]701;%s\007' de_DE.UTF-8
313 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
314 Can I switch the fonts at runtime? 391 Can I switch the fonts at runtime?
315 Yes, using an escape sequence. Try sth. like this, which has the 392 Yes, using an escape sequence. Try something like this, which has
316 same effect as using the "-fn" switch, and takes effect immediately: 393 the same effect as using the "-fn" switch, and takes effect
394 immediately:
317 395
318 printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic" 396 printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic"
319 397
320 This is useful if you e.g. work primarily with japanese (and prefer 398 This is useful if you e.g. work primarily with japanese (and prefer
321 a japanese font), but you have to switch to chinese temporarily, 399 a japanese font), but you have to switch to chinese temporarily,
… …
324 You can think of this as a kind of manual ISO-2022 switching. 402 You can think of this as a kind of manual ISO-2022 switching.
325 403
326 Why do italic characters look as if clipped? 404 Why do italic characters look as if clipped?
327 Many fonts have difficulties with italic characters and hinting. For 405 Many fonts have difficulties with italic characters and hinting. For
328 example, the otherwise very nicely hinted font "xft:Bitstream Vera 406 example, the otherwise very nicely hinted font "xft:Bitstream Vera
329 Sans Mono" completely fails in it's italic face. A workaround is to 407 Sans Mono" completely fails in it's italic face. A workaround might
330 enable freetype autohinting, i.e. like this: 408 be to enable freetype autohinting, i.e. like this:
331 409
332 URxvt*italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true 410 URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
333 URxvt*boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true 411 URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true
334 412
335 My input method wants <some encoding> but I want UTF-8, what can I do? 413 My input method wants <some encoding> but I want UTF-8, what can I do?
336 You can specify separate locales for the input method and the rest 414 You can specify separate locales for the input method and the rest
337 of the terminal, using the resource "imlocale": 415 of the terminal, using the resource "imlocale":
338 416
… …
341 Now you can start your terminal with "LC_CTYPE=ja_JP.UTF-8" and 419 Now you can start your terminal with "LC_CTYPE=ja_JP.UTF-8" and
342 still use your input method. Please note, however, that you will not 420 still use your input method. Please note, however, that you will not
343 be able to input characters outside "EUC-JP" in a normal way then, 421 be able to input characters outside "EUC-JP" in a normal way then,
344 as your input method limits you. 422 as your input method limits you.
345 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
346 Rxvt-unicode uses gobs of memory, how can I reduce that? 435 Rxvt-unicode uses gobs of memory, how can I reduce that?
347 Rxvt-unicode tries to obey the rule of not charging you for sth. you 436 Rxvt-unicode tries to obey the rule of not charging you for
348 don't use. One thing you should try is to configure out all settings 437 something you don't use. One thing you should try is to configure
349 that you don't need, for example, Xft support is a resource hog by 438 out all settings that you don't need, for example, Xft support is a
350 design, when used. Compiling it out ensures that no Xft font will be 439 resource hog by design, when used. Compiling it out ensures that no
351 loaded accidentally when rxvt-unicode tries to find a font for your 440 Xft font will be loaded accidentally when rxvt-unicode tries to find
352 characters. 441 a font for your characters.
353 442
354 Also, many people (me included) like large windows and even larger 443 Also, many people (me included) like large windows and even larger
355 scrollback buffers: Without "--enable-unicode3", rxvt-unicode will 444 scrollback buffers: Without "--enable-unicode3", rxvt-unicode will
356 use 6 bytes per screen cell. For a 160x?? window this amounts to 445 use 6 bytes per screen cell. For a 160x?? window this amounts to
357 almost a kilobyte per line. A scrollback buffer of 10000 lines will 446 almost a kilobyte per line. A scrollback buffer of 10000 lines will
… …
359 it gets worse, as rxvt-unicode then uses 8 bytes per screen cell. 448 it gets worse, as rxvt-unicode then uses 8 bytes per screen cell.
360 449
361 Can I speed up Xft rendering somehow? 450 Can I speed up Xft rendering somehow?
362 Yes, the most obvious way to speed it up is to avoid Xft entirely, 451 Yes, the most obvious way to speed it up is to avoid Xft entirely,
363 as it is simply slow. If you still want Xft fonts you might try to 452 as it is simply slow. If you still want Xft fonts you might try to
364 disable antialiasing (by appending ":antialiasing=false"), which 453 disable antialiasing (by appending ":antialias=false"), which saves
365 saves lots of memory and also speeds up rendering considerably. 454 lots of memory and also speeds up rendering considerably.
366 455
367 Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong? 456 Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?
368 Rxvt-unicode will use whatever you specify as a font. If it needs to 457 Rxvt-unicode will use whatever you specify as a font. If it needs to
369 fall back to it's default font search list it will prefer X11 core 458 fall back to it's default font search list it will prefer X11 core
370 fonts, because they are small and fast, and then use Xft fonts. It 459 fonts, because they are small and fast, and then use Xft fonts. It
… …
376 Mouse cut/paste suddenly no longer works. 465 Mouse cut/paste suddenly no longer works.
377 Make sure that mouse reporting is actually turned off since killing 466 Make sure that mouse reporting is actually turned off since killing
378 some editors prematurely may leave the mouse in mouse report mode. 467 some editors prematurely may leave the mouse in mouse report mode.
379 I've heard that tcsh may use mouse reporting unless it otherwise 468 I've heard that tcsh may use mouse reporting unless it otherwise
380 specified. A quick check is to see if cut/paste works when the Alt 469 specified. A quick check is to see if cut/paste works when the Alt
381 or Shift keys are depressed. See rxvt(7) 470 or Shift keys are depressed. See urxvt(7)
382 471
383 What's with this bold/blink stuff? 472 What's with this bold/blink stuff?
384 If no bold colour is set via "colorBD:", bold will invert text using 473 If no bold colour is set via "colorBD:", bold will invert text using
385 the standard foreground colour. 474 the standard foreground colour.
386 475
… …
401 resources (or as long-options). 490 resources (or as long-options).
402 491
403 Here are values that are supposed to resemble a VGA screen, 492 Here are values that are supposed to resemble a VGA screen,
404 including the murky brown that passes for low-intensity yellow: 493 including the murky brown that passes for low-intensity yellow:
405 494
406 URxvt*color0: #000000 495 URxvt.color0: #000000
407 URxvt*color1: #A80000 496 URxvt.color1: #A80000
408 URxvt*color2: #00A800 497 URxvt.color2: #00A800
409 URxvt*color3: #A8A800 498 URxvt.color3: #A8A800
410 URxvt*color4: #0000A8 499 URxvt.color4: #0000A8
411 URxvt*color5: #A800A8 500 URxvt.color5: #A800A8
412 URxvt*color6: #00A8A8 501 URxvt.color6: #00A8A8
413 URxvt*color7: #A8A8A8 502 URxvt.color7: #A8A8A8
414 503
415 URxvt*color8: #000054 504 URxvt.color8: #000054
416 URxvt*color9: #FF0054 505 URxvt.color9: #FF0054
417 URxvt*color10: #00FF54 506 URxvt.color10: #00FF54
418 URxvt*color11: #FFFF54 507 URxvt.color11: #FFFF54
419 URxvt*color12: #0000FF 508 URxvt.color12: #0000FF
420 URxvt*color13: #FF00FF 509 URxvt.color13: #FF00FF
421 URxvt*color14: #00FFFF 510 URxvt.color14: #00FFFF
422 URxvt*color15: #FFFFFF 511 URxvt.color15: #FFFFFF
423 512
424 And here is a more complete set of non-standard colors described as 513 And here is a more complete set of non-standard colors described
425 "pretty girly": 514 (not by me) as "pretty girly".
426 515
427 URxvt.cursorColor: #dc74d1 516 URxvt.cursorColor: #dc74d1
428 URxvt.pointerColor: #dc74d1 517 URxvt.pointerColor: #dc74d1
429 URxvt.background: #0e0e0e 518 URxvt.background: #0e0e0e
430 URxvt.foreground: #4ad5e1 519 URxvt.foreground: #4ad5e1
… …
441 URxvt.color6: #73f7ff 530 URxvt.color6: #73f7ff
442 URxvt.color14: #73f7ff 531 URxvt.color14: #73f7ff
443 URxvt.color7: #e1dddd 532 URxvt.color7: #e1dddd
444 URxvt.color15: #e1dddd 533 URxvt.color15: #e1dddd
445 534
535 How can I start urxvtd in a race-free way?
536 Try "urxvtd -f -o", which tells urxvtd to open the display, create
537 the listening socket and then fork.
538
446 What's with the strange Backspace/Delete key behaviour? 539 What's with the strange Backspace/Delete key behaviour?
447 Assuming that the physical Backspace key corresponds to the 540 Assuming that the physical Backspace key corresponds to the
448 BackSpace keysym (not likely for Linux ... see the following 541 BackSpace keysym (not likely for Linux ... see the following
449 question) there are two standard values that can be used for 542 question) there are two standard values that can be used for
450 Backspace: "^H" and "^?". 543 Backspace: "^H" and "^?".
… …
462 555
463 For starting a new rxvt-unicode: 556 For starting a new rxvt-unicode:
464 557
465 # use Backspace = ^H 558 # use Backspace = ^H
466 $ stty erase ^H 559 $ stty erase ^H
467 $ rxvt 560 $ urxvt
468 561
469 # use Backspace = ^? 562 # use Backspace = ^?
470 $ stty erase ^? 563 $ stty erase ^?
471 $ rxvt 564 $ urxvt
472 565
473 Toggle with "ESC[36h" / "ESC[36l" as documented in rxvt(7). 566 Toggle with "ESC [ 36 h" / "ESC [ 36 l" as documented in urxvt(7).
474 567
475 For an existing rxvt-unicode: 568 For an existing rxvt-unicode:
476 569
477 # use Backspace = ^H 570 # use Backspace = ^H
478 $ stty erase ^H 571 $ stty erase ^H
… …
487 value properly reflects that. 580 value properly reflects that.
488 581
489 The Delete key is a another casualty of the ill-defined Backspace 582 The Delete key is a another casualty of the ill-defined Backspace
490 problem. To avoid confusion between the Backspace and Delete keys, 583 problem. To avoid confusion between the Backspace and Delete keys,
491 the Delete key has been assigned an escape sequence to match the 584 the Delete key has been assigned an escape sequence to match the
492 vt100 for Execute (ESC[3~) and is in the supplied termcap/terminfo. 585 vt100 for Execute ("ESC [ 3 ~") and is in the supplied
586 termcap/terminfo.
493 587
494 Some other Backspace problems: 588 Some other Backspace problems:
495 589
496 some editors use termcap/terminfo, some editors (vim I'm told) 590 some editors use termcap/terminfo, some editors (vim I'm told)
497 expect Backspace = ^H, GNU Emacs (and Emacs-like editors) use ^H for 591 expect Backspace = ^H, GNU Emacs (and Emacs-like editors) use ^H for
… …
503 There are some compile-time selections available via configure. 597 There are some compile-time selections available via configure.
504 Unless you have run "configure" with the "--disable-resources" 598 Unless you have run "configure" with the "--disable-resources"
505 option you can use the `keysym' resource to alter the keystrings 599 option you can use the `keysym' resource to alter the keystrings
506 associated with keysyms. 600 associated with keysyms.
507 601
508 Here's an example for a URxvt session started using `rxvt -name 602 Here's an example for a URxvt session started using "urxvt -name
509 URxvt' 603 URxvt"
510 604
511 URxvt*keysym.Home: \e[1~ 605 URxvt.keysym.Home: \033[1~
512 URxvt*keysym.End: \e[4~ 606 URxvt.keysym.End: \033[4~
513 URxvt*keysym.C-apostrophe: \e<C-'> 607 URxvt.keysym.C-apostrophe: \033<C-'>
514 URxvt*keysym.C-slash: \e<C-/> 608 URxvt.keysym.C-slash: \033<C-/>
515 URxvt*keysym.C-semicolon: \e<C-;> 609 URxvt.keysym.C-semicolon: \033<C-;>
516 URxvt*keysym.C-grave: \e<C-`> 610 URxvt.keysym.C-grave: \033<C-`>
517 URxvt*keysym.C-comma: \e<C-,> 611 URxvt.keysym.C-comma: \033<C-,>
518 URxvt*keysym.C-period: \e<C-.> 612 URxvt.keysym.C-period: \033<C-.>
519 URxvt*keysym.C-0x60: \e<C-`> 613 URxvt.keysym.C-0x60: \033<C-`>
520 URxvt*keysym.C-Tab: \e<C-Tab> 614 URxvt.keysym.C-Tab: \033<C-Tab>
521 URxvt*keysym.C-Return: \e<C-Return> 615 URxvt.keysym.C-Return: \033<C-Return>
522 URxvt*keysym.S-Return: \e<S-Return> 616 URxvt.keysym.S-Return: \033<S-Return>
523 URxvt*keysym.S-space: \e<S-Space> 617 URxvt.keysym.S-space: \033<S-Space>
524 URxvt*keysym.M-Up: \e<M-Up> 618 URxvt.keysym.M-Up: \033<M-Up>
525 URxvt*keysym.M-Down: \e<M-Down> 619 URxvt.keysym.M-Down: \033<M-Down>
526 URxvt*keysym.M-Left: \e<M-Left> 620 URxvt.keysym.M-Left: \033<M-Left>
527 URxvt*keysym.M-Right: \e<M-Right> 621 URxvt.keysym.M-Right: \033<M-Right>
528 URxvt*keysym.M-C-0: list.0123456789.\e<M-C-.> 622 URxvt.keysym.M-C-0: list \033<M-C- 0123456789 >
529 URxvt*keysym.M-C-a: list.abcdefghijklmnopqrstuvwxyz.\033<M-C-.> 623 URxvt.keysym.M-C-a: list \033<M-C- abcdefghijklmnopqrstuvwxyz >
530 URxvt*keysym.F12: proto:\033]701;zh_CN.GBK\007 624 URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007
625
626 See some more examples in the documentation for the keysym resource.
531 627
532 I'm using keyboard model XXX that has extra Prior/Next/Insert keys. How 628 I'm using keyboard model XXX that has extra Prior/Next/Insert keys. How
533 do I make use of them? For example, the Sun Keyboard type 4 has the 629 do I make use of them? For example, the Sun Keyboard type 4 has the
534 following mappings that rxvt-unicode doesn't recognize. 630 following mappings that rxvt-unicode doesn't recognize.
535 KP_Insert == Insert 631 KP_Insert == Insert
… …
541 637
542 Rather than have rxvt-unicode try to accommodate all the various 638 Rather than have rxvt-unicode try to accommodate all the various
543 possible keyboard mappings, it is better to use `xmodmap' to remap 639 possible keyboard mappings, it is better to use `xmodmap' to remap
544 the keys as required for your particular machine. 640 the keys as required for your particular machine.
545 641
546 How do I distinguish if I'm running rxvt-unicode or a regular xterm? I 642 How do I distinguish wether I'm running rxvt-unicode or a regular xterm?
547 need this to decide about setting colors etc. 643 I need this to decide about setting colors etc.
548 rxvt and rxvt-unicode always export the variable "COLORTERM", so you 644 rxvt and rxvt-unicode always export the variable "COLORTERM", so you
549 can check and see if that is set. Note that several programs, JED, 645 can check and see if that is set. Note that several programs, JED,
550 slrn, Midnight Commander automatically check this variable to decide 646 slrn, Midnight Commander automatically check this variable to decide
551 whether or not to use color. 647 whether or not to use color.
552 648

Diff Legend

– Removed lines
+ Added lines
< Changed lines
> Changed lines