ViewVC Help
View File | Revision Log | Show Annotations | Download File
/cvs/rxvt-unicode/doc/rxvt.7.txt
(Generate patch)

Comparing rxvt-unicode/doc/rxvt.7.txt (file contents):
Revision 1.55 by root, Tue Jan 31 00:56:07 2006 UTC vs.
Revision 1.56 by root, Tue Jan 31 00:57:35 2006 UTC

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

Diff Legend

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