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.18 by root, Tue Nov 8 17:35:28 2005 UTC vs.
Revision 1.37 by root, Tue Jan 31 00:58:20 2006 UTC

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

Diff Legend

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