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

Diff Legend

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