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.29 by root, Mon Jan 16 14:48:39 2006 UTC

1FREQUENTLY ASKED QUESTIONS 1FREQUENTLY ASKED QUESTIONS
2 The new selection selects pieces that are too big, how can I select
3 single words?
4 Yes. For example, if you want to select alphanumeric words, you can
5 use the following resource:
6
7 URxvt.selection.pattern-0: ([[:word:]]+)
8
9 If you click more than twice, the selection will be extended more
10 and more.
11
12 To get a selection that is very similar to the old code, try this
13 pattern:
14
15 URxvt.selection.pattern-0: ([^"&'()*,;<=>?@[\\\\]^`{|})]+)
16
17 Please also note that the *LeftClick Shift-LeftClik* combination
18 also selects words like the old code.
19
20 I don't like the new selection/popups/hotkeys/perl, how do I
21 change/disable it?
22 You can disable the perl extension completely by setting the
23 perl-ext-common resource to the empty string, which also keeps
24 rxvt-unicode from initialising perl, saving memory.
25
26 If you only want to disable specific features, you first have to
27 identify which perl extension is responsible. For this, read the
28 section PREPACKAGED EXTENSIONS in the rxvtperl(3) manpage. For
29 example, to disable the selection-popup and option-popup, specify
30 this perl-ext-common resource:
31
32 URxvt.perl-ext-common: default,-selection-popup,-option-popup
33
34 This will keep the default extensions, but disable the two popup
35 extensions. Some extensions can also be configured, for example,
36 scrollback search mode is triggered by M-s. You can move it to any
37 other combination either by setting the searchable-scrollback
38 resource:
39
40 URxvt.searchable-scrollback: CM-s
41
42 Isn't rxvt supposed to be small? Don't all those features bloat?
43 I often get asked about this, and I think, no, they didn't cause
44 extra bloat. If you compare a minimal rxvt and a minimal urxvt, you
45 can see that the urxvt binary is larger (due to some encoding tables
46 always being compiled in), but it actually uses less memory (RSS)
47 after startup. Even with "--disable-everything", this comparison is
48 a bit unfair, as many features unique to urxvt (locale, encoding
49 conversion, iso14755 etc.) are already in use in this mode.
50
51 text data bss drs rss filename
52 98398 1664 24 15695 1824 rxvt --disable-everything
53 188985 9048 66616 18222 1788 urxvt --disable-everything
54
55 When you "--enable-everything" (which _is_ unfair, as this involves
56 xft and full locale/XIM support which are quite bloaty inside libX11
57 and my libc), the two diverge, but not unreasnobaly so.
58
59 text data bss drs rss filename
60 163431 2152 24 20123 2060 rxvt --enable-everything
61 1035683 49680 66648 29096 3680 urxvt --enable-everything
62
63 The very large size of the text section is explained by the
64 east-asian encoding tables, which, if unused, take up disk space but
65 nothing else and can be compiled out unless you rely on X11 core
66 fonts that use those encodings. The BSS size comes from the 64k
67 emergency buffer that my c++ compiler allocates (but of course
68 doesn't use unless you are out of memory). Also, using an xft font
69 instead of a core font immediately adds a few megabytes of RSS. Xft
70 indeed is responsible for a lot of RSS even when not used.
71
72 Of course, due to every character using two or four bytes instead of
73 one, a large scrollback buffer will ultimately make rxvt-unicode use
74 more memory.
75
76 Compared to e.g. Eterm (5112k), aterm (3132k) and xterm (4680k),
77 this still fares rather well. And compared to some monsters like
78 gnome-terminal (21152k + extra 4204k in separate processes) or
79 konsole (22200k + extra 43180k in daemons that stay around after
80 exit, plus half a minute of startup time, including the hundreds of
81 warnings it spits out), it fares extremely well *g*.
82
83 Why C++, isn't that unportable/bloated/uncool?
84 Is this a question? :) It comes up very often. The simple answer is:
85 I had to write it, and C++ allowed me to write and maintain it in a
86 fraction of the time and effort (which is a scarce resource for me).
87 Put even shorter: It simply wouldn't exist without C++.
88
89 My personal stance on this is that C++ is less portable than C, but
90 in the case of rxvt-unicode this hardly matters, as its portability
91 limits are defined by things like X11, pseudo terminals, locale
92 support and unix domain sockets, which are all less portable than
93 C++ itself.
94
95 Regarding the bloat, see the above question: It's easy to write
96 programs in C that use gobs of memory, an certainly possible to
97 write programs in C++ that don't. C++ also often comes with large
98 libraries, but this is not necessarily the case with GCC. Here is
99 what rxvt links against on my system with a minimal config:
100
101 libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000)
102 libc.so.6 => /lib/libc.so.6 (0x00002aaaaadde000)
103 libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab01d000)
104 /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)
105
106 And here is rxvt-unicode:
107
108 libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000)
109 libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00002aaaaada2000)
110 libc.so.6 => /lib/libc.so.6 (0x00002aaaaaeb0000)
111 libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab0ee000)
112 /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)
113
114 No large bloated libraries (of course, none were linked in
115 statically), except maybe libX11 :)
116
117 Does it support tabs, can I have a tabbed rxvt-unicode?
118 rxvt-unicode does not directly support tabs. It will work fine with
119 tabbing functionality of many window managers or similar tabbing
120 programs, and its embedding-features allow it to be embedded into
121 other programs, as witnessed by doc/rxvt-tabbed or the upcoming
122 "Gtk2::URxvt" perl module, which features a tabbed urxvt (murxvt)
123 terminal as an example embedding application.
124
2 How do I know which rxvt-unicode version I'm using? 125 How do I know which rxvt-unicode version I'm using?
3 The version number is displayed with the usage (-h). Also the escape 126 The version number is displayed with the usage (-h). Also the escape
4 sequence "ESC[8n" sets the window title to the version number. 127 sequence "ESC [ 8 n" sets the window title to the version number.
128 When using the rxvtc client, the version displayed is that of the
129 daemon.
130
131 I am using Debian GNU/Linux and have a problem...
132 The Debian GNU/Linux package of rxvt-unicode in sarge contains large
133 patches that considerably change the behaviour of rxvt-unicode.
134 Before reporting a bug to the original rxvt-unicode author please
135 download and install the genuine version
136 (<http://software.schmorp.de#rxvt-unicode>) and try to reproduce the
137 problem. If you cannot, chances are that the problems are specific
138 to Debian GNU/Linux, in which case it should be reported via the
139 Debian Bug Tracking System (use "reportbug" to report the bug).
140
141 For other problems that also affect the Debian package, you can and
142 probably should use the Debian BTS, too, because, after all, it's
143 also a bug in the Debian version and it serves as a reminder for
144 other users that might encounter the same issue.
145
146 I am maintaining rxvt-unicode for distribution/OS XXX, any
147 recommendation?
148 You should build one binary with the default options. configure now
149 enables most useful options, and the trend goes to making them
150 runtime-switchable, too, so there is usually no drawback to enbaling
151 them, except higher disk and possibly memory usage. The perl
152 interpreter should be enabled, as important functionality (menus,
153 selection, likely more in the future) depends on it.
154
155 You should not overwrite the "perl-ext-common" snd "perl-ext"
156 resources system-wide (except maybe with "defaults"). This will
157 result in useful behaviour. If your distribution aims at low memory,
158 add an empty "perl-ext-common" resource to the app-defaults file.
159 This will keep the perl interpreter disabled until the user enables
160 it.
161
162 If you can/want build more binaries, I recommend building a minimal
163 one with "--disable-everything" (very useful) and a maximal one with
164 "--enable-everything" (less useful, it will be very big due to a lot
165 of encodings built-in that increase download times and are rarely
166 used).
167
168 I need to make it setuid/setgid to support utmp/ptys on my OS, is this
169 safe?
170 Likely not. While I honestly try to make it secure, and am probably
171 not bad at it, I think it is simply unreasonable to expect all of
172 freetype + fontconfig + xft + xlib + perl + ... + rxvt-unicode
173 itself to all be secure. Also, rxvt-unicode disables some options
174 when it detects that it runs setuid or setgid, which is not nice.
175 Besides, with the embedded perl interpreter the possibility for
176 security problems easily multiplies.
177
178 Elevated privileges are only required for utmp and pty operations on
179 some systems (for example, GNU/Linux doesn't need any extra
180 privileges for ptys, but some need it for utmp support). It is
181 planned to mvoe this into a forked handler process, but this is not
182 yet done.
183
184 So, while setuid/setgid operation is supported and not a problem on
185 your typical single-user-no-other-logins unix desktop, always
186 remember that its an awful lot of code, most of which isn't checked
187 for security issues regularly.
5 188
6 When I log-in to another system it tells me about missing terminfo data? 189 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 190 The terminal description used by rxvt-unicode is not as widely
8 available as that for xterm, or even rxvt (for which the same 191 available as that for xterm, or even rxvt (for which the same
9 problem often arises). 192 problem often arises).
… …
21 problems arising, which includes wrong keymapping, less and 204 problems arising, which includes wrong keymapping, less and
22 different colours and some refresh errors in fullscreen 205 different colours and some refresh errors in fullscreen
23 applications. It's a nice quick-and-dirty workaround for rare cases, 206 applications. It's a nice quick-and-dirty workaround for rare cases,
24 though. 207 though.
25 208
26 If you always want to do this you can either recompile rxvt-unicode 209 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: 210 you can either recompile rxvt-unicode with the desired TERM value or
211 use a resource to set it:
28 212
29 URxvt.termName: rxvt 213 URxvt.termName: rxvt
30 214
31 If you don't plan to use rxvt (quite common...) you could also 215 If you don't plan to use rxvt (quite common...) you could also
32 replace the rxvt terminfo file with the rxvt-unicode one. 216 replace the rxvt terminfo file with the rxvt-unicode one.
33 217
218 "tic" outputs some error when compiling the terminfo entry.
219 Most likely it's the empty definition for "enacs=". Just replace it
220 by "enacs=\E[0@" and try again.
221
222 "bash"'s readline does not work correctly under rxvt.
34 I need a termcap file entry. 223 I need a termcap file entry.
224 One reason you might want this is that some distributions or
225 operating systems still compile some programs using the
226 long-obsoleted termcap library (Fedora Core's bash is one example)
227 and rely on a termcap entry for "rxvt-unicode".
228
35 You could use rxvt's termcap entry with resonable results in many 229 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 230 cases. You can also create a termcap entry by using terminfo's
37 infocmp program like this: 231 infocmp program like this:
38 232
39 infocmp -C rxvt-unicode 233 infocmp -C rxvt-unicode
40 234
41 OR you could this termcap entry: 235 Or you could use this termcap entry, generated by the command above:
42 236
43 rxvt-unicode|rxvt-unicode terminal (X Window System):\ 237 rxvt-unicode|rxvt-unicode terminal (X Window System):\
44 :am:bw:eo:km:mi:ms:xn:xo:\ 238 :am:bw:eo:km:mi:ms:xn:xo:\
45 :co#80:it#8:li#24:\ 239 :co#80:it#8:li#24:lm#0:\
46 :AL=\E[%dL:DC=\E[%dP:DL=\E[%dM:DO=\E[%dB:IC=\E[%d@:\ 240 :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:\ 241 :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:\ 242 :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:\ 243 :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:\ 244 :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[@:\ 245 :dl=\E[M:do=^J:ec=\E[%dX:ei=\E[4l:ho=\E[H:\
246 :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:\ 247 :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~:\ 248 :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~:\ 249 :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:\ 250 :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=:\ 251 :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:\ 252 :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:\ 253 :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:\ 254 :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:\ 255 :us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\
61 :vs=\E[?25h: 256 :vs=\E[?25h:
62 257
63 Why does "ls" no longer have coloured output? 258 Why does "ls" no longer have coloured output?
64 The "ls" in the GNU coreutils unfortunately doesn't use terminfo to 259 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 260 decide wether a terminal has colour, but uses it's own configuration
… …
84 furthermore fail to even install the "rxvt-unicode" terminfo file, 279 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 280 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 281 log-in to another system it tells me about missing terminfo data? on
87 how to do this). 282 how to do this).
88 283
284 My numerical keypad acts weird and generates differing output?
285 Some Debian GNUL/Linux users seem to have this problem, although no
286 specific details were reported so far. It is possible that this is
287 caused by the wrong "TERM" setting, although the details of wether
288 and how this can happen are unknown, as "TERM=rxvt" should offer a
289 compatible keymap. See the answer to the previous question, and
290 please report if that helped.
291
89 Rxvt-unicode does not seem to understand the selected encoding? 292 Rxvt-unicode does not seem to understand the selected encoding?
90 Unicode does not seem to work? 293 Unicode does not seem to work?
91 If you encounter strange problems like typing an accented character 294 If you encounter strange problems like typing an accented character
92 but getting two unrelated other characters or similar, or if program 295 but getting two unrelated other characters or similar, or if program
93 output is subtly garbled, then you should check your locale 296 output is subtly garbled, then you should check your locale
94 settings. 297 settings.
95 298
96 Rxvt-unicode must be started with the same "LC_CTYPE" setting as the 299 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 300 programs. Often rxvt-unicode is started in the "C" locale, while the
98 login script running within the rxvt-unicode window changes the 301 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 302 locale to something else, e.g. "en_GB.UTF-8". Needless to say, this
100 not going to work. 303 is not going to work.
101 304
102 The best thing is to fix your startup environment, as you will 305 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 306 likely run into other problems. If nothing works you can try this in
104 your .profile. 307 your .profile.
105 308
106 printf '\e]701;%s\007' "$LC_CTYPE" 309 printf '\e]701;%s\007' "$LC_CTYPE"
107 310
108 If this doesn't work, then maybe you use a "LC_CTYPE" specification 311 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 312 not supported on your systems. Some systems have a "locale" command
110 which displays this. If it displays sth. like: 313 which displays this (also, "perl -e0" can be used to check locale
314 settings, as it will complain loudly if it cannot set the locale).
315 If it displays something like:
111 316
112 locale: Cannot set LC_CTYPE to default locale: ... 317 locale: Cannot set LC_CTYPE to default locale: ...
113 318
114 Then the locale you specified is not supported on your system. 319 Then the locale you specified is not supported on your system.
115 320
… …
123 Chances are that the font you (or the admin/package maintainer of 328 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 329 your system/os) have specified does not cover all the characters you
125 want to display. 330 want to display.
126 331
127 rxvt-unicode makes a best-effort try at finding a replacement font. 332 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. 333 Often the result is fine, but sometimes the chosen font looks
129 Many fonts have totally strange characters that don't resemble the 334 bad/ugly/wrong. Some fonts have totally strange characters that
130 correct glyph at all, and rxvt-unicode lacks the artificial 335 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 336 artificial intelligence to detect that a specific glyph is wrong: it
132 believe the font that the characters it contains indeed look 337 has to believe the font that the characters it claims to contain
133 correct. 338 indeed look correct.
134 339
135 In that case, select a font of your taste and add it to the font 340 In that case, select a font of your taste and add it to the font
136 list, e.g.: 341 list, e.g.:
137 342
138 rxvt -fn basefont,font2,font3... 343 rxvt -fn basefont,font2,font3...
… …
141 font. If the base font does not contain the character, it will go to 346 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 347 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 348 up this search and use less resources within rxvt-unicode and the
144 X-server. 349 X-server.
145 350
146 The only limitation is that all the fonts must not be larger than 351 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, 352 base font, as the base font defines the terminal character cell
148 which must be the same due to the way terminals work. 353 size, which must be the same due to the way terminals work.
149 354
150 Why do some chinese characters look so different than others? 355 Why do some chinese characters look so different than others?
151 This is because there is a difference between script and language -- 356 This is because there is a difference between script and language --
152 rxvt-unicode does not know which language the text that is output 357 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 358 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 359 first sees a japanese/chinese character, it might choose a japanese
155 it. Subsequent japanese characters will take that font. Now, many 360 font for display. Subsequent japanese characters will use that font.
156 chinese characters aren't represented in japanese fonts, so when the 361 Now, many chinese characters aren't represented in japanese fonts,
157 first non-japanese character comes up, rxvt-unicode will look for a 362 so when the first non-japanese character comes up, rxvt-unicode will
158 chinese font -- unfortunately at this point, it will still use the 363 look for a chinese font -- unfortunately at this point, it will
159 japanese font for japanese characters that are also chinese. 364 still use the japanese font for chinese characters that are also in
365 the japanese font.
160 366
161 The workaround is easy: just tag a chinese font at the end of your 367 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 368 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 369 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 370 japanese font first. If you expect more chinese, put a chinese font
165 first. 371 first.
166 372
167 In the future it might be possible to switch preferences at runtime 373 In the future it might be possible to switch language preferences at
168 (the internal data structure has no problem with using different 374 runtime (the internal data structure has no problem with using
169 fonts for the same character at the same time, but no interface for 375 different fonts for the same character at the same time, but no
170 this has been designed yet). 376 interface for this has been designed yet).
377
378 Until then, you might get away with switching fonts at runtime (see
379 "Can I switch the fonts at runtime?" later in this document).
171 380
172 Why does rxvt-unicode sometimes leave pixel droppings? 381 Why does rxvt-unicode sometimes leave pixel droppings?
173 Most fonts were not designed for terminal use, which means that 382 Most fonts were not designed for terminal use, which means that
174 character size varies a lot. A font that is otherwise fine for 383 character size varies a lot. A font that is otherwise fine for
175 terminal use might contain some characters that are simply too wide. 384 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. 398 that doesn't work, you might be forced to use a different font.
190 399
191 All of this is not a problem when using X11 core fonts, as their 400 All of this is not a problem when using X11 core fonts, as their
192 bounding box data is correct. 401 bounding box data is correct.
193 402
403 On Solaris 9, many line-drawing characters are too wide.
404 Seems to be a known bug, read
405 <http://nixdoc.net/files/forum/about34198.html>. Some people use the
406 following ugly workaround to get non-double-wide-characters working:
407
408 #define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x)
409
194 My Compose (Multi_key) key is no longer working. 410 My Compose (Multi_key) key is no longer working.
195 The most common causes for this are that either your locale is not 411 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 412 set correctly, or you specified a preeditStyle that is not supported
197 by your input method. For example, if you specified OverTheSpot and 413 by your input method. For example, if you specified OverTheSpot and
198 your input method (e.g. the default input method handling Compose 414 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 425 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 426 other codes, too, such as "Ctrl-Shift-1-d" to type the default
211 telnet escape character and so on. 427 telnet escape character and so on.
212 428
213 How can I keep rxvt-unicode from using reverse video so much? 429 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 430 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 431 settings ("TERM=rxvt-unicode"), which will get rid of most of these
216 sure you have specified colours for italic and bold, as otherwise 432 effects. Then make sure you have specified colours for italic and
217 rxvt-unicode might use reverse video to simulate the effect: 433 bold, as otherwise rxvt-unicode might use reverse video to simulate
434 the effect:
218 435
219 URxvt*colorBD: white 436 URxvt.colorBD: white
220 URxvt*colorIT: green 437 URxvt.colorIT: green
221 438
222 Some programs assume totally weird colours (red instead of blue), how 439 Some programs assume totally weird colours (red instead of blue), how
223 can I fix that? 440 can I fix that?
224 For some unexplainable reason, some programs (i.e. irssi) assume a 441 For some unexplainable reason, some rare programs assume a very
225 very weird colour palette when confronted with a terminal with more 442 weird colour palette when confronted with a terminal with more than
226 than the standard 8 colours (rxvt-unicode supports 88). The right 443 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 444 of course, to fix these programs not to assume non-ISO colours
228 colours without very good reasons. 445 without very good reasons.
229 446
230 In the meantime, you can either edit your "urxvt" terminfo 447 In the meantime, you can either edit your "rxvt-unicode" terminfo
231 definition to only claim 8 colour support or use "TERM=rxvt", which 448 definition to only claim 8 colour support or use "TERM=rxvt", which
232 will fix colours but keep you from using other rxvt-unicode 449 will fix colours but keep you from using other rxvt-unicode
233 features. 450 features.
234 451
235 I am on FreeBSD and rxvt-unicode does not seem to work at all. 452 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__" 455 it, wether it defines the symbol or not. "__STDC_ISO_10646__"
239 requires that wchar_t is represented as unicode. 456 requires that wchar_t is represented as unicode.
240 457
241 As you might have guessed, FreeBSD does neither define this symobl 458 As you might have guessed, FreeBSD does neither define this symobl
242 nor does it support it. Instead, it uses it's own internal 459 nor does it support it. Instead, it uses it's own internal
243 representation of wchar_t. This is, of course, completely legal. 460 representation of wchar_t. This is, of course, completely fine with
461 respect to standards.
244 462
463 However, that means rxvt-unicode only works in "POSIX", "ISO-8859-1"
464 and "UTF-8" locales under FreeBSD (which all use Unicode as wchar_t.
465
245 However, "__STDC_ISO_10646__" is the only sane way to support 466 "__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 467 apps in an OS, as using a locale-dependent (and non-standardized)
247 non-standardized) representation of wchar_t makes it impossible to 468 representation of wchar_t makes it impossible to convert between
248 convert between wchar_t (as used by X11 and your applications) and 469 wchar_t (as used by X11 and your applications) and any other
249 any other encoding without implementing OS-specific-wrappers for 470 encoding without implementing OS-specific-wrappers for each and
250 each and every locale. There simply are no APIs to convert wchar_t 471 every locale. There simply are no APIs to convert wchar_t into
251 into anything except the current locale encoding. 472 anything except the current locale encoding.
252 473
253 Some applications (such as the formidable mlterm) work around this 474 Some applications (such as the formidable mlterm) work around this
254 by carrying their own replacement functions for character set 475 by carrying their own replacement functions for character set
255 handling with them, and either implementing OS-dependent hacks or 476 handling with them, and either implementing OS-dependent hacks or
256 doing multiple conversions (which is slow and unreliable in case the 477 doing multiple conversions (which is slow and unreliable in case the
257 OS implements encodings slightly different than the terminal 478 OS implements encodings slightly different than the terminal
258 emulator). 479 emulator).
259 480
260 The rxvt-unicode author insists that the right way to fix this is in 481 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 482 the system libraries once and for all, instead of forcing every app
262 to carry complete replacements. 483 to carry complete replacements for them :)
484
485 I use Solaris 9 and it doesn't compile/work/etc.
486 Try the diff in doc/solaris9.patch as a base. It fixes the worst
487 problems with "wcwidth" and a compile problem.
488
489 How can I use rxvt-unicode under cygwin?
490 rxvt-unicode should compile and run out of the box on cygwin, using
491 the X11 libraries that come with cygwin. libW11 emulation is no
492 longer supported (and makes no sense, either, as it only supported a
493 single font). I recommend starting the X-server in "-multiwindow" or
494 "-rootless" mode instead, which will result in similar look&feel as
495 the old libW11 emulation.
496
497 At the time of this writing, cygwin didn't seem to support any
498 multi-byte encodings (you might try "LC_CTYPE=C-UTF-8"), so you are
499 likely limited to 8-bit encodings.
263 500
264 How does rxvt-unicode determine the encoding to use? 501 How does rxvt-unicode determine the encoding to use?
265 Is there an option to switch encodings? 502 Is there an option to switch encodings?
266 Unlike some other terminals, rxvt-unicode has no encoding switch, 503 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 504 and no specific "utf-8" mode, such as xterm. In fact, it doesn't
… …
270 507
271 The reasons is that there exists a perfectly fine mechanism for 508 The reasons is that there exists a perfectly fine mechanism for
272 selecting the encoding, doing I/O and (most important) communicating 509 selecting the encoding, doing I/O and (most important) communicating
273 this to all applications so everybody agrees on character properties 510 this to all applications so everybody agrees on character properties
274 such as width and code number. This mechanism is the *locale*. 511 such as width and code number. This mechanism is the *locale*.
512 Applications not using that info will have problems (for example,
513 "xterm" gets the width of characters wrong as it uses it's own,
514 locale-independent table under all locales).
275 515
276 Rxvt-unicode uses the "LC_CTYPE" locale category to select encoding. 516 Rxvt-unicode uses the "LC_CTYPE" locale category to select encoding.
277 All programs doing the same (that is, most) will automatically agree 517 All programs doing the same (that is, most) will automatically agree
278 in the interpretation of characters. 518 in the interpretation of characters.
279 519
… …
287 "language_country.encoding", but other forms (i.e. "de" or "german") 527 "language_country.encoding", but other forms (i.e. "de" or "german")
288 are also common. 528 are also common.
289 529
290 Rxvt-unicode ignores all other locale categories, and except for the 530 Rxvt-unicode ignores all other locale categories, and except for the
291 encoding, ignores country or language-specific settings, i.e. 531 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. 532 "de_DE.UTF-8" and "ja_JP.UTF-8" are the normally same to
533 rxvt-unicode.
293 534
294 If you want to use a specific encoding you have to make sure you 535 If you want to use a specific encoding you have to make sure you
295 start rxvt-unicode with the correct "LC_CTYPE" category. 536 start rxvt-unicode with the correct "LC_CTYPE" category.
296 537
297 Can I switch locales at runtime? 538 Can I switch locales at runtime?
298 Yes, using an escape sequence. Try sth. like this, which sets 539 Yes, using an escape sequence. Try something like this, which sets
299 rxvt-unicode's idea of "LC_CTYPE". 540 rxvt-unicode's idea of "LC_CTYPE".
300 541
301 printf '\e]701;%s\007' ja_JP.SJIS 542 printf '\e]701;%s\007' ja_JP.SJIS
302 543
303 See also the previous question. 544 See also the previous answer.
304 545
305 Sometimes this capability is rather handy when you want to work in 546 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 547 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 548 (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: 549 first switches to a locale supported by xjdic and back later:
309 550
310 printf '\e]701;%s\007' ja_JP.SJIS 551 printf '\e]701;%s\007' ja_JP.SJIS
311 xjdic -js 552 xjdic -js
312 printf '\e]701;%s\007' de_DE.UTF-8 553 printf '\e]701;%s\007' de_DE.UTF-8
313 554
555 You can also use xterm's "luit" program, which usually works fine,
556 except for some locales where character width differs between
557 program- and rxvt-unicode-locales.
558
314 Can I switch the fonts at runtime? 559 Can I switch the fonts at runtime?
315 Yes, using an escape sequence. Try sth. like this, which has the 560 Yes, using an escape sequence. Try something like this, which has
316 same effect as using the "-fn" switch, and takes effect immediately: 561 the same effect as using the "-fn" switch, and takes effect
562 immediately:
317 563
318 printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic" 564 printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic"
319 565
320 This is useful if you e.g. work primarily with japanese (and prefer 566 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, 567 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. 570 You can think of this as a kind of manual ISO-2022 switching.
325 571
326 Why do italic characters look as if clipped? 572 Why do italic characters look as if clipped?
327 Many fonts have difficulties with italic characters and hinting. For 573 Many fonts have difficulties with italic characters and hinting. For
328 example, the otherwise very nicely hinted font "xft:Bitstream Vera 574 example, the otherwise very nicely hinted font "xft:Bitstream Vera
329 Sans Mono" completely fails in it's italic face. A workaround is to 575 Sans Mono" completely fails in it's italic face. A workaround might
330 enable freetype autohinting, i.e. like this: 576 be to enable freetype autohinting, i.e. like this:
331 577
332 URxvt*italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true 578 URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
333 URxvt*boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true 579 URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true
334 580
335 My input method wants <some encoding> but I want UTF-8, what can I do? 581 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 582 You can specify separate locales for the input method and the rest
337 of the terminal, using the resource "imlocale": 583 of the terminal, using the resource "imlocale":
338 584
… …
341 Now you can start your terminal with "LC_CTYPE=ja_JP.UTF-8" and 587 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 588 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, 589 be able to input characters outside "EUC-JP" in a normal way then,
344 as your input method limits you. 590 as your input method limits you.
345 591
592 Rxvt-unicode crashes when the X Input Method changes or exits.
593 Unfortunately, this is unavoidable, as the XIM protocol is racy by
594 design. Applications can avoid some crashes at the expense of memory
595 leaks, and Input Methods can avoid some crashes by careful ordering
596 at exit time. kinput2 (and derived input methods) generally
597 succeeds, while SCIM (or similar input methods) fails. In the end,
598 however, crashes cannot be completely avoided even if both sides
599 cooperate.
600
601 So the only workaround is not to kill your Input Method Servers.
602
346 Rxvt-unicode uses gobs of memory, how can I reduce that? 603 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 604 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 605 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 606 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 607 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 608 Xft font will be loaded accidentally when rxvt-unicode tries to find
352 characters. 609 a font for your characters.
353 610
354 Also, many people (me included) like large windows and even larger 611 Also, many people (me included) like large windows and even larger
355 scrollback buffers: Without "--enable-unicode3", rxvt-unicode will 612 scrollback buffers: Without "--enable-unicode3", rxvt-unicode will
356 use 6 bytes per screen cell. For a 160x?? window this amounts to 613 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 614 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. 616 it gets worse, as rxvt-unicode then uses 8 bytes per screen cell.
360 617
361 Can I speed up Xft rendering somehow? 618 Can I speed up Xft rendering somehow?
362 Yes, the most obvious way to speed it up is to avoid Xft entirely, 619 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 620 as it is simply slow. If you still want Xft fonts you might try to
364 disable antialiasing (by appending ":antialiasing=false"), which 621 disable antialiasing (by appending ":antialias=false"), which saves
365 saves lots of memory and also speeds up rendering considerably. 622 lots of memory and also speeds up rendering considerably.
366 623
367 Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong? 624 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 625 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 626 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 627 fonts, because they are small and fast, and then use Xft fonts. It
… …
376 Mouse cut/paste suddenly no longer works. 633 Mouse cut/paste suddenly no longer works.
377 Make sure that mouse reporting is actually turned off since killing 634 Make sure that mouse reporting is actually turned off since killing
378 some editors prematurely may leave the mouse in mouse report mode. 635 some editors prematurely may leave the mouse in mouse report mode.
379 I've heard that tcsh may use mouse reporting unless it otherwise 636 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 637 specified. A quick check is to see if cut/paste works when the Alt
381 or Shift keys are depressed. See rxvt(7) 638 or Shift keys are depressed.
382 639
383 What's with this bold/blink stuff? 640 What's with this bold/blink stuff?
384 If no bold colour is set via "colorBD:", bold will invert text using 641 If no bold colour is set via "colorBD:", bold will invert text using
385 the standard foreground colour. 642 the standard foreground colour.
386 643
… …
401 resources (or as long-options). 658 resources (or as long-options).
402 659
403 Here are values that are supposed to resemble a VGA screen, 660 Here are values that are supposed to resemble a VGA screen,
404 including the murky brown that passes for low-intensity yellow: 661 including the murky brown that passes for low-intensity yellow:
405 662
406 URxvt*color0: #000000 663 URxvt.color0: #000000
407 URxvt*color1: #A80000 664 URxvt.color1: #A80000
408 URxvt*color2: #00A800 665 URxvt.color2: #00A800
409 URxvt*color3: #A8A800 666 URxvt.color3: #A8A800
410 URxvt*color4: #0000A8 667 URxvt.color4: #0000A8
411 URxvt*color5: #A800A8 668 URxvt.color5: #A800A8
412 URxvt*color6: #00A8A8 669 URxvt.color6: #00A8A8
413 URxvt*color7: #A8A8A8 670 URxvt.color7: #A8A8A8
414 671
415 URxvt*color8: #000054 672 URxvt.color8: #000054
416 URxvt*color9: #FF0054 673 URxvt.color9: #FF0054
417 URxvt*color10: #00FF54 674 URxvt.color10: #00FF54
418 URxvt*color11: #FFFF54 675 URxvt.color11: #FFFF54
419 URxvt*color12: #0000FF 676 URxvt.color12: #0000FF
420 URxvt*color13: #FF00FF 677 URxvt.color13: #FF00FF
421 URxvt*color14: #00FFFF 678 URxvt.color14: #00FFFF
422 URxvt*color15: #FFFFFF 679 URxvt.color15: #FFFFFF
423 680
424 And here is a more complete set of non-standard colors described as 681 And here is a more complete set of non-standard colors described
425 "pretty girly": 682 (not by me) as "pretty girly".
426 683
427 URxvt.cursorColor: #dc74d1 684 URxvt.cursorColor: #dc74d1
428 URxvt.pointerColor: #dc74d1 685 URxvt.pointerColor: #dc74d1
429 URxvt.background: #0e0e0e 686 URxvt.background: #0e0e0e
430 URxvt.foreground: #4ad5e1 687 URxvt.foreground: #4ad5e1
… …
441 URxvt.color6: #73f7ff 698 URxvt.color6: #73f7ff
442 URxvt.color14: #73f7ff 699 URxvt.color14: #73f7ff
443 URxvt.color7: #e1dddd 700 URxvt.color7: #e1dddd
444 URxvt.color15: #e1dddd 701 URxvt.color15: #e1dddd
445 702
703 How can I start rxvtd in a race-free way?
704 Try "rxvtd -f -o", which tells rxvtd to open the display, create the
705 listening socket and then fork.
706
446 What's with the strange Backspace/Delete key behaviour? 707 What's with the strange Backspace/Delete key behaviour?
447 Assuming that the physical Backspace key corresponds to the 708 Assuming that the physical Backspace key corresponds to the
448 BackSpace keysym (not likely for Linux ... see the following 709 BackSpace keysym (not likely for Linux ... see the following
449 question) there are two standard values that can be used for 710 question) there are two standard values that can be used for
450 Backspace: "^H" and "^?". 711 Backspace: "^H" and "^?".
… …
468 729
469 # use Backspace = ^? 730 # use Backspace = ^?
470 $ stty erase ^? 731 $ stty erase ^?
471 $ rxvt 732 $ rxvt
472 733
473 Toggle with "ESC[36h" / "ESC[36l" as documented in rxvt(7). 734 Toggle with "ESC [ 36 h" / "ESC [ 36 l".
474 735
475 For an existing rxvt-unicode: 736 For an existing rxvt-unicode:
476 737
477 # use Backspace = ^H 738 # use Backspace = ^H
478 $ stty erase ^H 739 $ stty erase ^H
… …
487 value properly reflects that. 748 value properly reflects that.
488 749
489 The Delete key is a another casualty of the ill-defined Backspace 750 The Delete key is a another casualty of the ill-defined Backspace
490 problem. To avoid confusion between the Backspace and Delete keys, 751 problem. To avoid confusion between the Backspace and Delete keys,
491 the Delete key has been assigned an escape sequence to match the 752 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. 753 vt100 for Execute ("ESC [ 3 ~") and is in the supplied
754 termcap/terminfo.
493 755
494 Some other Backspace problems: 756 Some other Backspace problems:
495 757
496 some editors use termcap/terminfo, some editors (vim I'm told) 758 some editors use termcap/terminfo, some editors (vim I'm told)
497 expect Backspace = ^H, GNU Emacs (and Emacs-like editors) use ^H for 759 expect Backspace = ^H, GNU Emacs (and Emacs-like editors) use ^H for
… …
503 There are some compile-time selections available via configure. 765 There are some compile-time selections available via configure.
504 Unless you have run "configure" with the "--disable-resources" 766 Unless you have run "configure" with the "--disable-resources"
505 option you can use the `keysym' resource to alter the keystrings 767 option you can use the `keysym' resource to alter the keystrings
506 associated with keysyms. 768 associated with keysyms.
507 769
508 Here's an example for a URxvt session started using `rxvt -name 770 Here's an example for a URxvt session started using "rxvt -name
509 URxvt' 771 URxvt"
510 772
511 URxvt*keysym.Home: \e[1~ 773 URxvt.keysym.Home: \033[1~
512 URxvt*keysym.End: \e[4~ 774 URxvt.keysym.End: \033[4~
513 URxvt*keysym.C-apostrophe: \e<C-'> 775 URxvt.keysym.C-apostrophe: \033<C-'>
514 URxvt*keysym.C-slash: \e<C-/> 776 URxvt.keysym.C-slash: \033<C-/>
515 URxvt*keysym.C-semicolon: \e<C-;> 777 URxvt.keysym.C-semicolon: \033<C-;>
516 URxvt*keysym.C-grave: \e<C-`> 778 URxvt.keysym.C-grave: \033<C-`>
517 URxvt*keysym.C-comma: \e<C-,> 779 URxvt.keysym.C-comma: \033<C-,>
518 URxvt*keysym.C-period: \e<C-.> 780 URxvt.keysym.C-period: \033<C-.>
519 URxvt*keysym.C-0x60: \e<C-`> 781 URxvt.keysym.C-0x60: \033<C-`>
520 URxvt*keysym.C-Tab: \e<C-Tab> 782 URxvt.keysym.C-Tab: \033<C-Tab>
521 URxvt*keysym.C-Return: \e<C-Return> 783 URxvt.keysym.C-Return: \033<C-Return>
522 URxvt*keysym.S-Return: \e<S-Return> 784 URxvt.keysym.S-Return: \033<S-Return>
523 URxvt*keysym.S-space: \e<S-Space> 785 URxvt.keysym.S-space: \033<S-Space>
524 URxvt*keysym.M-Up: \e<M-Up> 786 URxvt.keysym.M-Up: \033<M-Up>
525 URxvt*keysym.M-Down: \e<M-Down> 787 URxvt.keysym.M-Down: \033<M-Down>
526 URxvt*keysym.M-Left: \e<M-Left> 788 URxvt.keysym.M-Left: \033<M-Left>
527 URxvt*keysym.M-Right: \e<M-Right> 789 URxvt.keysym.M-Right: \033<M-Right>
528 URxvt*keysym.M-C-0: list.0123456789.\e<M-C-.> 790 URxvt.keysym.M-C-0: list \033<M-C- 0123456789 >
529 URxvt*keysym.M-C-a: list.abcdefghijklmnopqrstuvwxyz.\033<M-C-.> 791 URxvt.keysym.M-C-a: list \033<M-C- abcdefghijklmnopqrstuvwxyz >
530 URxvt*keysym.F12: proto:\033]701;zh_CN.GBK\007 792 URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007
793
794 See some more examples in the documentation for the keysym resource.
531 795
532 I'm using keyboard model XXX that has extra Prior/Next/Insert keys. How 796 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 797 do I make use of them? For example, the Sun Keyboard type 4 has the
534 following mappings that rxvt-unicode doesn't recognize. 798 following mappings that rxvt-unicode doesn't recognize.
535 KP_Insert == Insert 799 KP_Insert == Insert
… …
541 805
542 Rather than have rxvt-unicode try to accommodate all the various 806 Rather than have rxvt-unicode try to accommodate all the various
543 possible keyboard mappings, it is better to use `xmodmap' to remap 807 possible keyboard mappings, it is better to use `xmodmap' to remap
544 the keys as required for your particular machine. 808 the keys as required for your particular machine.
545 809
546 How do I distinguish if I'm running rxvt-unicode or a regular xterm? I 810 How do I distinguish wether I'm running rxvt-unicode or a regular xterm?
547 need this to decide about setting colors etc. 811 I need this to decide about setting colors etc.
548 rxvt and rxvt-unicode always export the variable "COLORTERM", so you 812 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, 813 can check and see if that is set. Note that several programs, JED,
550 slrn, Midnight Commander automatically check this variable to decide 814 slrn, Midnight Commander automatically check this variable to decide
551 whether or not to use color. 815 whether or not to use color.
552 816

Diff Legend

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