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

Diff Legend

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