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.14 by root, Thu Jun 30 14:00:49 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 contains large patches
8 that considerably change the behaviour of rxvt-unicode. Before
9 reporting a bug to the original rxvt-unicode author please download
10 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 "bash"'s readline does not work correctly under rxvt.
34 I need a termcap file entry. 51 I need a termcap file entry.
52 One reason you might want this is that some distributions or
53 operating systems still compile some programs using the
54 long-obsoleted termcap library (Fedora Core's bash is one example)
55 and rely on a termcap entry for "rxvt-unicode".
56
35 You could use rxvt's termcap entry with resonable results in many 57 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 58 cases. You can also create a termcap entry by using terminfo's
37 infocmp program like this: 59 infocmp program like this:
38 60
39 infocmp -C rxvt-unicode 61 infocmp -C rxvt-unicode
40 62
41 OR you could this termcap entry: 63 Or you could use this termcap entry, generated by the command above:
42 64
43 rxvt-unicode|rxvt-unicode terminal (X Window System):\ 65 rxvt-unicode|rxvt-unicode terminal (X Window System):\
44 :am:bw:eo:km:mi:ms:xn:xo:\ 66 :am:bw:eo:km:mi:ms:xn:xo:\
45 :co#80:it#8:li#24:\ 67 :co#80:it#8:li#24:lm#0:\
46 :AL=\E[%dL:DC=\E[%dP:DL=\E[%dM:DO=\E[%dB:IC=\E[%d@:\ 68 :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:\ 69 :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:\ 70 :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:\ 71 :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:\ 72 :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[@:\ 73 :dl=\E[M:do=^J:ec=\E[%dX:ei=\E[4l:ho=\E[H:\
74 :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:\ 75 :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~:\ 76 :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~:\ 77 :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:\ 78 :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=:\ 79 :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:\ 80 :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:\ 81 :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:\ 82 :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:\ 83 :us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\
61 :vs=\E[?25h: 84 :vs=\E[?25h:
62 85
63 Why does "ls" no longer have coloured output? 86 Why does "ls" no longer have coloured output?
64 The "ls" in the GNU coreutils unfortunately doesn't use terminfo to 87 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 88 decide wether a terminal has colour, but uses it's own configuration
… …
84 furthermore fail to even install the "rxvt-unicode" terminfo file, 107 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 108 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 109 log-in to another system it tells me about missing terminfo data? on
87 how to do this). 110 how to do this).
88 111
112 My numerical keypad acts weird and generates differing output?
113 Some Debian GNUL/Linux users seem to have this problem, although no
114 specific details were reported so far. It is possible that this is
115 caused by the wrong "TERM" setting, although the details of wether
116 and how this can happen are unknown, as "TERM=rxvt" should offer a
117 compatible keymap. See the answer to the previous question, and
118 please report if that helped.
119
89 Rxvt-unicode does not seem to understand the selected encoding? 120 Rxvt-unicode does not seem to understand the selected encoding?
90 Unicode does not seem to work? 121 Unicode does not seem to work?
91 If you encounter strange problems like typing an accented character 122 If you encounter strange problems like typing an accented character
92 but getting two unrelated other characters or similar, or if program 123 but getting two unrelated other characters or similar, or if program
93 output is subtly garbled, then you should check your locale 124 output is subtly garbled, then you should check your locale
94 settings. 125 settings.
95 126
96 Rxvt-unicode must be started with the same "LC_CTYPE" setting as the 127 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 128 programs. Often rxvt-unicode is started in the "C" locale, while the
98 login script running within the rxvt-unicode window changes the 129 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 130 locale to something else, e.g. "en_GB.UTF-8". Needless to say, this
100 not going to work. 131 is not going to work.
101 132
102 The best thing is to fix your startup environment, as you will 133 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 134 likely run into other problems. If nothing works you can try this in
104 your .profile. 135 your .profile.
105 136
106 printf '\e]701;%s\007' "$LC_CTYPE" 137 printf '\e]701;%s\007' "$LC_CTYPE"
107 138
108 If this doesn't work, then maybe you use a "LC_CTYPE" specification 139 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 140 not supported on your systems. Some systems have a "locale" command
110 which displays this. If it displays sth. like: 141 which displays this (also, "perl -e0" can be used to check locale
142 settings, as it will complain loudly if it cannot set the locale).
143 If it displays something like:
111 144
112 locale: Cannot set LC_CTYPE to default locale: ... 145 locale: Cannot set LC_CTYPE to default locale: ...
113 146
114 Then the locale you specified is not supported on your system. 147 Then the locale you specified is not supported on your system.
115 148
… …
123 Chances are that the font you (or the admin/package maintainer of 156 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 157 your system/os) have specified does not cover all the characters you
125 want to display. 158 want to display.
126 159
127 rxvt-unicode makes a best-effort try at finding a replacement font. 160 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. 161 Often the result is fine, but sometimes the chosen font looks
129 Many fonts have totally strange characters that don't resemble the 162 bad/ugly/wrong. Some fonts have totally strange characters that
130 correct glyph at all, and rxvt-unicode lacks the artificial 163 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 164 artificial intelligence to detect that a specific glyph is wrong: it
132 believe the font that the characters it contains indeed look 165 has to believe the font that the characters it claims to contain
133 correct. 166 indeed look correct.
134 167
135 In that case, select a font of your taste and add it to the font 168 In that case, select a font of your taste and add it to the font
136 list, e.g.: 169 list, e.g.:
137 170
138 rxvt -fn basefont,font2,font3... 171 rxvt -fn basefont,font2,font3...
… …
141 font. If the base font does not contain the character, it will go to 174 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 175 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 176 up this search and use less resources within rxvt-unicode and the
144 X-server. 177 X-server.
145 178
146 The only limitation is that all the fonts must not be larger than 179 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, 180 base font, as the base font defines the terminal character cell
148 which must be the same due to the way terminals work. 181 size, which must be the same due to the way terminals work.
149 182
150 Why do some chinese characters look so different than others? 183 Why do some chinese characters look so different than others?
151 This is because there is a difference between script and language -- 184 This is because there is a difference between script and language --
152 rxvt-unicode does not know which language the text that is output 185 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 186 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 187 first sees a japanese/chinese character, it might choose a japanese
155 it. Subsequent japanese characters will take that font. Now, many 188 font for display. Subsequent japanese characters will use that font.
156 chinese characters aren't represented in japanese fonts, so when the 189 Now, many chinese characters aren't represented in japanese fonts,
157 first non-japanese character comes up, rxvt-unicode will look for a 190 so when the first non-japanese character comes up, rxvt-unicode will
158 chinese font -- unfortunately at this point, it will still use the 191 look for a chinese font -- unfortunately at this point, it will
159 japanese font for japanese characters that are also chinese. 192 still use the japanese font for chinese characters that are also in
193 the japanese font.
160 194
161 The workaround is easy: just tag a chinese font at the end of your 195 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 196 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 197 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 198 japanese font first. If you expect more chinese, put a chinese font
165 first. 199 first.
166 200
167 In the future it might be possible to switch preferences at runtime 201 In the future it might be possible to switch language preferences at
168 (the internal data structure has no problem with using different 202 runtime (the internal data structure has no problem with using
169 fonts for the same character at the same time, but no interface for 203 different fonts for the same character at the same time, but no
170 this has been designed yet). 204 interface for this has been designed yet).
205
206 Until then, you might get away with switching fonts at runtime (see
207 "Can I switch the fonts at runtime?" later in this document).
171 208
172 Why does rxvt-unicode sometimes leave pixel droppings? 209 Why does rxvt-unicode sometimes leave pixel droppings?
173 Most fonts were not designed for terminal use, which means that 210 Most fonts were not designed for terminal use, which means that
174 character size varies a lot. A font that is otherwise fine for 211 character size varies a lot. A font that is otherwise fine for
175 terminal use might contain some characters that are simply too wide. 212 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. 226 that doesn't work, you might be forced to use a different font.
190 227
191 All of this is not a problem when using X11 core fonts, as their 228 All of this is not a problem when using X11 core fonts, as their
192 bounding box data is correct. 229 bounding box data is correct.
193 230
231 On Solaris 9, many line-drawing characters are too wide.
232 Seems to be a known bug, read
233 <http://nixdoc.net/files/forum/about34198.html>. Some people use the
234 following ugly workaround to get non-double-wide-characters working:
235
236 #define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x)
237
194 My Compose (Multi_key) key is no longer working. 238 My Compose (Multi_key) key is no longer working.
195 The most common causes for this are that either your locale is not 239 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 240 set correctly, or you specified a preeditStyle that is not supported
197 by your input method. For example, if you specified OverTheSpot and 241 by your input method. For example, if you specified OverTheSpot and
198 your input method (e.g. the default input method handling Compose 242 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 253 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 254 other codes, too, such as "Ctrl-Shift-1-d" to type the default
211 telnet escape character and so on. 255 telnet escape character and so on.
212 256
213 How can I keep rxvt-unicode from using reverse video so much? 257 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 258 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 259 settings ("TERM=rxvt-unicode"), which will get rid of most of these
216 sure you have specified colours for italic and bold, as otherwise 260 effects. Then make sure you have specified colours for italic and
217 rxvt-unicode might use reverse video to simulate the effect: 261 bold, as otherwise rxvt-unicode might use reverse video to simulate
262 the effect:
218 263
219 URxvt*colorBD: white 264 URxvt.colorBD: white
220 URxvt*colorIT: green 265 URxvt.colorIT: green
221 266
222 Some programs assume totally weird colours (red instead of blue), how 267 Some programs assume totally weird colours (red instead of blue), how
223 can I fix that? 268 can I fix that?
224 For some unexplainable reason, some programs (i.e. irssi) assume a 269 For some unexplainable reason, some rare programs assume a very
225 very weird colour palette when confronted with a terminal with more 270 weird colour palette when confronted with a terminal with more than
226 than the standard 8 colours (rxvt-unicode supports 88). The right 271 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 272 of course, to fix these programs not to assume non-ISO colours
228 colours without very good reasons. 273 without very good reasons.
229 274
230 In the meantime, you can either edit your "urxvt" terminfo 275 In the meantime, you can either edit your "rxvt-unicode" terminfo
231 definition to only claim 8 colour support or use "TERM=rxvt", which 276 definition to only claim 8 colour support or use "TERM=rxvt", which
232 will fix colours but keep you from using other rxvt-unicode 277 will fix colours but keep you from using other rxvt-unicode
233 features. 278 features.
234 279
235 I am on FreeBSD and rxvt-unicode does not seem to work at all. 280 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__" 283 it, wether it defines the symbol or not. "__STDC_ISO_10646__"
239 requires that wchar_t is represented as unicode. 284 requires that wchar_t is represented as unicode.
240 285
241 As you might have guessed, FreeBSD does neither define this symobl 286 As you might have guessed, FreeBSD does neither define this symobl
242 nor does it support it. Instead, it uses it's own internal 287 nor does it support it. Instead, it uses it's own internal
243 representation of wchar_t. This is, of course, completely legal. 288 representation of wchar_t. This is, of course, completely fine with
289 respect to standards.
244 290
291 However, that means rxvt-unicode only works in "POSIX", "ISO-8859-1"
292 and "UTF-8" locales under FreeBSD (which all use Unicode as wchar_t.
293
245 However, "__STDC_ISO_10646__" is the only sane way to support 294 "__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 295 apps in an OS, as using a locale-dependent (and non-standardized)
247 non-standardized) representation of wchar_t makes it impossible to 296 representation of wchar_t makes it impossible to convert between
248 convert between wchar_t (as used by X11 and your applications) and 297 wchar_t (as used by X11 and your applications) and any other
249 any other encoding without implementing OS-specific-wrappers for 298 encoding without implementing OS-specific-wrappers for each and
250 each and every locale. There simply are no APIs to convert wchar_t 299 every locale. There simply are no APIs to convert wchar_t into
251 into anything except the current locale encoding. 300 anything except the current locale encoding.
252 301
253 Some applications (such as the formidable mlterm) work around this 302 Some applications (such as the formidable mlterm) work around this
254 by carrying their own replacement functions for character set 303 by carrying their own replacement functions for character set
255 handling with them, and either implementing OS-dependent hacks or 304 handling with them, and either implementing OS-dependent hacks or
256 doing multiple conversions (which is slow and unreliable in case the 305 doing multiple conversions (which is slow and unreliable in case the
257 OS implements encodings slightly different than the terminal 306 OS implements encodings slightly different than the terminal
258 emulator). 307 emulator).
259 308
260 The rxvt-unicode author insists that the right way to fix this is in 309 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 310 the system libraries once and for all, instead of forcing every app
262 to carry complete replacements. 311 to carry complete replacements for them :)
312
313 I use Solaris 9 and it doesn't compile/work/etc.
314 Try the diff in doc/solaris9.patch as a base. It fixes the worst
315 problems with "wcwidth" and a compile problem.
263 316
264 How does rxvt-unicode determine the encoding to use? 317 How does rxvt-unicode determine the encoding to use?
265 Is there an option to switch encodings? 318 Is there an option to switch encodings?
266 Unlike some other terminals, rxvt-unicode has no encoding switch, 319 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 320 and no specific "utf-8" mode, such as xterm. In fact, it doesn't
… …
270 323
271 The reasons is that there exists a perfectly fine mechanism for 324 The reasons is that there exists a perfectly fine mechanism for
272 selecting the encoding, doing I/O and (most important) communicating 325 selecting the encoding, doing I/O and (most important) communicating
273 this to all applications so everybody agrees on character properties 326 this to all applications so everybody agrees on character properties
274 such as width and code number. This mechanism is the *locale*. 327 such as width and code number. This mechanism is the *locale*.
328 Applications not using that info will have problems (for example,
329 "xterm" gets the width of characters wrong as it uses it's own,
330 locale-independent table under all locales).
275 331
276 Rxvt-unicode uses the "LC_CTYPE" locale category to select encoding. 332 Rxvt-unicode uses the "LC_CTYPE" locale category to select encoding.
277 All programs doing the same (that is, most) will automatically agree 333 All programs doing the same (that is, most) will automatically agree
278 in the interpretation of characters. 334 in the interpretation of characters.
279 335
… …
287 "language_country.encoding", but other forms (i.e. "de" or "german") 343 "language_country.encoding", but other forms (i.e. "de" or "german")
288 are also common. 344 are also common.
289 345
290 Rxvt-unicode ignores all other locale categories, and except for the 346 Rxvt-unicode ignores all other locale categories, and except for the
291 encoding, ignores country or language-specific settings, i.e. 347 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. 348 "de_DE.UTF-8" and "ja_JP.UTF-8" are the normally same to
349 rxvt-unicode.
293 350
294 If you want to use a specific encoding you have to make sure you 351 If you want to use a specific encoding you have to make sure you
295 start rxvt-unicode with the correct "LC_CTYPE" category. 352 start rxvt-unicode with the correct "LC_CTYPE" category.
296 353
297 Can I switch locales at runtime? 354 Can I switch locales at runtime?
298 Yes, using an escape sequence. Try sth. like this, which sets 355 Yes, using an escape sequence. Try something like this, which sets
299 rxvt-unicode's idea of "LC_CTYPE". 356 rxvt-unicode's idea of "LC_CTYPE".
300 357
301 printf '\e]701;%s\007' ja_JP.SJIS 358 printf '\e]701;%s\007' ja_JP.SJIS
302 359
303 See also the previous question. 360 See also the previous answer.
304 361
305 Sometimes this capability is rather handy when you want to work in 362 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 363 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 364 (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: 365 first switches to a locale supported by xjdic and back later:
309 366
310 printf '\e]701;%s\007' ja_JP.SJIS 367 printf '\e]701;%s\007' ja_JP.SJIS
311 xjdic -js 368 xjdic -js
312 printf '\e]701;%s\007' de_DE.UTF-8 369 printf '\e]701;%s\007' de_DE.UTF-8
313 370
371 You can also use xterm's "luit" program, which usually works fine,
372 except for some locales where character width differs between
373 program- and rxvt-unicode-locales.
374
314 Can I switch the fonts at runtime? 375 Can I switch the fonts at runtime?
315 Yes, using an escape sequence. Try sth. like this, which has the 376 Yes, using an escape sequence. Try something like this, which has
316 same effect as using the "-fn" switch, and takes effect immediately: 377 the same effect as using the "-fn" switch, and takes effect
378 immediately:
317 379
318 printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic" 380 printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic"
319 381
320 This is useful if you e.g. work primarily with japanese (and prefer 382 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, 383 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. 386 You can think of this as a kind of manual ISO-2022 switching.
325 387
326 Why do italic characters look as if clipped? 388 Why do italic characters look as if clipped?
327 Many fonts have difficulties with italic characters and hinting. For 389 Many fonts have difficulties with italic characters and hinting. For
328 example, the otherwise very nicely hinted font "xft:Bitstream Vera 390 example, the otherwise very nicely hinted font "xft:Bitstream Vera
329 Sans Mono" completely fails in it's italic face. A workaround is to 391 Sans Mono" completely fails in it's italic face. A workaround might
330 enable freetype autohinting, i.e. like this: 392 be to enable freetype autohinting, i.e. like this:
331 393
332 URxvt*italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true 394 URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
333 URxvt*boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true 395 URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true
334 396
335 My input method wants <some encoding> but I want UTF-8, what can I do? 397 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 398 You can specify separate locales for the input method and the rest
337 of the terminal, using the resource "imlocale": 399 of the terminal, using the resource "imlocale":
338 400
… …
341 Now you can start your terminal with "LC_CTYPE=ja_JP.UTF-8" and 403 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 404 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, 405 be able to input characters outside "EUC-JP" in a normal way then,
344 as your input method limits you. 406 as your input method limits you.
345 407
408 Rxvt-unicode crashes when the X Input Method changes or exits.
409 Unfortunately, this is unavoidable, as the XIM protocol is racy by
410 design. Applications can avoid some crashes at the expense of memory
411 leaks, and Input Methods can avoid some crashes by careful ordering
412 at exit time. kinput2 (and derived input methods) generally
413 succeeds, while SCIM (or similar input methods) fails. In the end,
414 however, crashes cannot be completely avoided even if both sides
415 cooperate.
416
417 So the only workaround is not to kill your Input Method Servers.
418
346 Rxvt-unicode uses gobs of memory, how can I reduce that? 419 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 420 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 421 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 422 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 423 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 424 Xft font will be loaded accidentally when rxvt-unicode tries to find
352 characters. 425 a font for your characters.
353 426
354 Also, many people (me included) like large windows and even larger 427 Also, many people (me included) like large windows and even larger
355 scrollback buffers: Without "--enable-unicode3", rxvt-unicode will 428 scrollback buffers: Without "--enable-unicode3", rxvt-unicode will
356 use 6 bytes per screen cell. For a 160x?? window this amounts to 429 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 430 almost a kilobyte per line. A scrollback buffer of 10000 lines will
… …
401 resources (or as long-options). 474 resources (or as long-options).
402 475
403 Here are values that are supposed to resemble a VGA screen, 476 Here are values that are supposed to resemble a VGA screen,
404 including the murky brown that passes for low-intensity yellow: 477 including the murky brown that passes for low-intensity yellow:
405 478
406 URxvt*color0: #000000 479 URxvt.color0: #000000
407 URxvt*color1: #A80000 480 URxvt.color1: #A80000
408 URxvt*color2: #00A800 481 URxvt.color2: #00A800
409 URxvt*color3: #A8A800 482 URxvt.color3: #A8A800
410 URxvt*color4: #0000A8 483 URxvt.color4: #0000A8
411 URxvt*color5: #A800A8 484 URxvt.color5: #A800A8
412 URxvt*color6: #00A8A8 485 URxvt.color6: #00A8A8
413 URxvt*color7: #A8A8A8 486 URxvt.color7: #A8A8A8
414 487
415 URxvt*color8: #000054 488 URxvt.color8: #000054
416 URxvt*color9: #FF0054 489 URxvt.color9: #FF0054
417 URxvt*color10: #00FF54 490 URxvt.color10: #00FF54
418 URxvt*color11: #FFFF54 491 URxvt.color11: #FFFF54
419 URxvt*color12: #0000FF 492 URxvt.color12: #0000FF
420 URxvt*color13: #FF00FF 493 URxvt.color13: #FF00FF
421 URxvt*color14: #00FFFF 494 URxvt.color14: #00FFFF
422 URxvt*color15: #FFFFFF 495 URxvt.color15: #FFFFFF
423 496
424 And here is a more complete set of non-standard colors described as 497 And here is a more complete set of non-standard colors described
425 "pretty girly": 498 (not by me) as "pretty girly".
426 499
427 URxvt.cursorColor: #dc74d1 500 URxvt.cursorColor: #dc74d1
428 URxvt.pointerColor: #dc74d1 501 URxvt.pointerColor: #dc74d1
429 URxvt.background: #0e0e0e 502 URxvt.background: #0e0e0e
430 URxvt.foreground: #4ad5e1 503 URxvt.foreground: #4ad5e1
… …
441 URxvt.color6: #73f7ff 514 URxvt.color6: #73f7ff
442 URxvt.color14: #73f7ff 515 URxvt.color14: #73f7ff
443 URxvt.color7: #e1dddd 516 URxvt.color7: #e1dddd
444 URxvt.color15: #e1dddd 517 URxvt.color15: #e1dddd
445 518
519 How can I start rxvtd in a race-free way?
520 Despite it's name, rxvtd is not a real daemon, but more like a
521 server that answers rxvtc's requests, so it doesn't background
522 itself.
523
524 To ensure rxvtd is listening on it's socket, you can use the
525 following method to wait for the startup message before continuing:
526
527 { rxvtd & } | read
528
446 What's with the strange Backspace/Delete key behaviour? 529 What's with the strange Backspace/Delete key behaviour?
447 Assuming that the physical Backspace key corresponds to the 530 Assuming that the physical Backspace key corresponds to the
448 BackSpace keysym (not likely for Linux ... see the following 531 BackSpace keysym (not likely for Linux ... see the following
449 question) there are two standard values that can be used for 532 question) there are two standard values that can be used for
450 Backspace: "^H" and "^?". 533 Backspace: "^H" and "^?".
… …
468 551
469 # use Backspace = ^? 552 # use Backspace = ^?
470 $ stty erase ^? 553 $ stty erase ^?
471 $ rxvt 554 $ rxvt
472 555
473 Toggle with "ESC[36h" / "ESC[36l" as documented in rxvt(7). 556 Toggle with "ESC [ 36 h" / "ESC [ 36 l" as documented in rxvt(7).
474 557
475 For an existing rxvt-unicode: 558 For an existing rxvt-unicode:
476 559
477 # use Backspace = ^H 560 # use Backspace = ^H
478 $ stty erase ^H 561 $ stty erase ^H
… …
487 value properly reflects that. 570 value properly reflects that.
488 571
489 The Delete key is a another casualty of the ill-defined Backspace 572 The Delete key is a another casualty of the ill-defined Backspace
490 problem. To avoid confusion between the Backspace and Delete keys, 573 problem. To avoid confusion between the Backspace and Delete keys,
491 the Delete key has been assigned an escape sequence to match the 574 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. 575 vt100 for Execute ("ESC [ 3 ~") and is in the supplied
576 termcap/terminfo.
493 577
494 Some other Backspace problems: 578 Some other Backspace problems:
495 579
496 some editors use termcap/terminfo, some editors (vim I'm told) 580 some editors use termcap/terminfo, some editors (vim I'm told)
497 expect Backspace = ^H, GNU Emacs (and Emacs-like editors) use ^H for 581 expect Backspace = ^H, GNU Emacs (and Emacs-like editors) use ^H for
… …
503 There are some compile-time selections available via configure. 587 There are some compile-time selections available via configure.
504 Unless you have run "configure" with the "--disable-resources" 588 Unless you have run "configure" with the "--disable-resources"
505 option you can use the `keysym' resource to alter the keystrings 589 option you can use the `keysym' resource to alter the keystrings
506 associated with keysyms. 590 associated with keysyms.
507 591
508 Here's an example for a URxvt session started using `rxvt -name 592 Here's an example for a URxvt session started using "rxvt -name
509 URxvt' 593 URxvt"
510 594
511 URxvt*keysym.Home: \e[1~ 595 URxvt.keysym.Home: \033[1~
512 URxvt*keysym.End: \e[4~ 596 URxvt.keysym.End: \033[4~
513 URxvt*keysym.C-apostrophe: \e<C-'> 597 URxvt.keysym.C-apostrophe: \033<C-'>
514 URxvt*keysym.C-slash: \e<C-/> 598 URxvt.keysym.C-slash: \033<C-/>
515 URxvt*keysym.C-semicolon: \e<C-;> 599 URxvt.keysym.C-semicolon: \033<C-;>
516 URxvt*keysym.C-grave: \e<C-`> 600 URxvt.keysym.C-grave: \033<C-`>
517 URxvt*keysym.C-comma: \e<C-,> 601 URxvt.keysym.C-comma: \033<C-,>
518 URxvt*keysym.C-period: \e<C-.> 602 URxvt.keysym.C-period: \033<C-.>
519 URxvt*keysym.C-0x60: \e<C-`> 603 URxvt.keysym.C-0x60: \033<C-`>
520 URxvt*keysym.C-Tab: \e<C-Tab> 604 URxvt.keysym.C-Tab: \033<C-Tab>
521 URxvt*keysym.C-Return: \e<C-Return> 605 URxvt.keysym.C-Return: \033<C-Return>
522 URxvt*keysym.S-Return: \e<S-Return> 606 URxvt.keysym.S-Return: \033<S-Return>
523 URxvt*keysym.S-space: \e<S-Space> 607 URxvt.keysym.S-space: \033<S-Space>
524 URxvt*keysym.M-Up: \e<M-Up> 608 URxvt.keysym.M-Up: \033<M-Up>
525 URxvt*keysym.M-Down: \e<M-Down> 609 URxvt.keysym.M-Down: \033<M-Down>
526 URxvt*keysym.M-Left: \e<M-Left> 610 URxvt.keysym.M-Left: \033<M-Left>
527 URxvt*keysym.M-Right: \e<M-Right> 611 URxvt.keysym.M-Right: \033<M-Right>
528 URxvt*keysym.M-C-0: list.0123456789.\e<M-C-.> 612 URxvt.keysym.M-C-0: list \033<M-C- 0123456789 >
529 URxvt*keysym.M-C-a: list.abcdefghijklmnopqrstuvwxyz.\033<M-C-.> 613 URxvt.keysym.M-C-a: list \033<M-C- abcdefghijklmnopqrstuvwxyz >
530 URxvt*keysym.F12: proto:\033]701;zh_CN.GBK\007 614 URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007
615
616 See some more examples in the documentation for the keysym resource.
531 617
532 I'm using keyboard model XXX that has extra Prior/Next/Insert keys. How 618 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 619 do I make use of them? For example, the Sun Keyboard type 4 has the
534 following mappings that rxvt-unicode doesn't recognize. 620 following mappings that rxvt-unicode doesn't recognize.
535 KP_Insert == Insert 621 KP_Insert == Insert
… …
541 627
542 Rather than have rxvt-unicode try to accommodate all the various 628 Rather than have rxvt-unicode try to accommodate all the various
543 possible keyboard mappings, it is better to use `xmodmap' to remap 629 possible keyboard mappings, it is better to use `xmodmap' to remap
544 the keys as required for your particular machine. 630 the keys as required for your particular machine.
545 631
546 How do I distinguish if I'm running rxvt-unicode or a regular xterm? I 632 How do I distinguish wether I'm running rxvt-unicode or a regular xterm?
547 need this to decide about setting colors etc. 633 I need this to decide about setting colors etc.
548 rxvt and rxvt-unicode always export the variable "COLORTERM", so you 634 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, 635 can check and see if that is set. Note that several programs, JED,
550 slrn, Midnight Commander automatically check this variable to decide 636 slrn, Midnight Commander automatically check this variable to decide
551 whether or not to use color. 637 whether or not to use color.
552 638

Diff Legend

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