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

Diff Legend

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