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

Diff Legend

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