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

Diff Legend

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