… | |
… | |
16 | =head1 DESCRIPTION |
16 | =head1 DESCRIPTION |
17 | |
17 | |
18 | This document contains the FAQ, the RXVT TECHNICAL REFERENCE documenting |
18 | This document contains the FAQ, the RXVT TECHNICAL REFERENCE documenting |
19 | all escape sequences, and other background information. |
19 | all escape sequences, and other background information. |
20 | |
20 | |
21 | The newest version of this document is |
21 | The newest version of this document is also available on the World Wide Web at |
22 | also available on the World Wide Web at |
|
|
23 | L<http://cvs.schmorp.de/browse/*checkout*/rxvt-unicode/doc/rxvt.7.html>. |
22 | L<http://cvs.schmorp.de/browse/*checkout*/rxvt-unicode/doc/rxvt.7.html>. |
24 | |
23 | |
25 | =head1 FREQUENTLY ASKED QUESTIONS |
24 | =head1 FREQUENTLY ASKED QUESTIONS |
26 | |
25 | |
27 | =over 4 |
|
|
28 | |
|
|
29 | =item The new selection selects pieces that are too big, how can I select |
26 | =head2 The new selection selects pieces that are too big, how can I select single words? |
30 | single words? |
|
|
31 | |
27 | |
32 | Yes. For example, if you want to select alphanumeric words, you can use |
28 | If you want to select e.g. alphanumeric words, you can use the following |
33 | the following resource: |
29 | setting: |
34 | |
30 | |
35 | URxvt.selection.pattern-0: ([[:word:]]+) |
31 | URxvt.selection.pattern-0: ([[:word:]]+) |
36 | |
32 | |
37 | If you click more than twice, the selection will be extended |
33 | If you click more than twice, the selection will be extended |
38 | more and more. |
34 | more and more. |
… | |
… | |
42 | URxvt.selection.pattern-0: ([^"&'()*,;<=>?@[\\\\]^`{|})]+) |
38 | URxvt.selection.pattern-0: ([^"&'()*,;<=>?@[\\\\]^`{|})]+) |
43 | |
39 | |
44 | Please also note that the I<LeftClick Shift-LeftClik> combination also |
40 | Please also note that the I<LeftClick Shift-LeftClik> combination also |
45 | selects words like the old code. |
41 | selects words like the old code. |
46 | |
42 | |
47 | =item I don't like the new selection/popups/hotkeys/perl, how do I |
43 | =head2 I don't like the new selection/popups/hotkeys/perl, how do I change/disable it? |
48 | change/disable it? |
|
|
49 | |
44 | |
50 | You can disable the perl extension completely by setting the |
45 | You can disable the perl extension completely by setting the |
51 | B<perl-ext-common> resource to the empty string, which also keeps |
46 | B<perl-ext-common> resource to the empty string, which also keeps |
52 | rxvt-unicode from initialising perl, saving memory. |
47 | rxvt-unicode from initialising perl, saving memory. |
53 | |
48 | |
… | |
… | |
64 | scrollback search mode is triggered by B<M-s>. You can move it to any |
59 | scrollback search mode is triggered by B<M-s>. You can move it to any |
65 | other combination either by setting the B<searchable-scrollback> resource: |
60 | other combination either by setting the B<searchable-scrollback> resource: |
66 | |
61 | |
67 | URxvt.searchable-scrollback: CM-s |
62 | URxvt.searchable-scrollback: CM-s |
68 | |
63 | |
|
|
64 | =head2 The cursor moves when selecting text in the current input line, how do I switch this off? |
|
|
65 | |
|
|
66 | See next entry. |
|
|
67 | |
|
|
68 | =head2 During rlogin/ssh/telnet/etc. sessions, clicking near the cursor outputs strange escape sequences, how do I fix this? |
|
|
69 | |
|
|
70 | These are caused by the C<readline> perl extension. Under normal |
|
|
71 | circumstances, it will move your cursor around when you click into the |
|
|
72 | line that contains it. It tries hard not to do this at the wrong moment, |
|
|
73 | but when running a program that doesn't parse cursor movements or in some |
|
|
74 | cases during rlogin sessions, it fails to detect this properly. |
|
|
75 | |
|
|
76 | You can permamently switch this feature off by disabling the C<readline> |
|
|
77 | extension: |
|
|
78 | |
|
|
79 | URxvt.perl-ext-common: default,-readline |
|
|
80 | |
|
|
81 | =head2 Why doesn't rxvt-unicode read my resources? |
|
|
82 | |
|
|
83 | Well, why, indeed? It does, in a way very similar to other X |
|
|
84 | applications. Most importantly, this means that if you or your OS loads |
|
|
85 | resources into the X display (the right way to do it), rxvt-unicode will |
|
|
86 | ignore any resource files in your home directory. It will only read |
|
|
87 | F<$HOME/.Xdefaults> when no resources are attached to the display. |
|
|
88 | |
|
|
89 | If you have or use an F<$HOME/.Xresources> file, chances are that |
|
|
90 | resources are loaded into your X-server. In this case, you have to |
|
|
91 | re-login after every change (or run F<xrdb -merge $HOME/.Xresources>). |
|
|
92 | |
|
|
93 | Also consider the form resources have to use: |
|
|
94 | |
|
|
95 | URxvt.resource: value |
|
|
96 | |
|
|
97 | If you want to use another form (there are lots of different ways of |
|
|
98 | specifying resources), make sure you understand wether and why it |
|
|
99 | works. If unsure, use the form above. |
|
|
100 | |
|
|
101 | =head2 I can't get transparency working, what am I doing wrong? |
|
|
102 | |
|
|
103 | First of all, transparency isn't officially supported in rxvt-unicode, so |
|
|
104 | you are mostly on your own. Do not bug the author about it (but you may |
|
|
105 | bug everybody else). Also, if you can't get it working consider it a rite |
|
|
106 | of passage: ... and you failed. |
|
|
107 | |
|
|
108 | Here are four ways to get transparency. B<Do> read the manpage and option |
|
|
109 | descriptions for the programs mentioned and rxvt-unicode. Really, do it! |
|
|
110 | |
|
|
111 | 1. Use inheritPixmap: |
|
|
112 | |
|
|
113 | Esetroot wallpaper.jpg |
|
|
114 | @@RXVT_NAME@@ -ip -tint red -sh 40 |
|
|
115 | |
|
|
116 | That works. If you think it doesn't, you lack transparency and tinting |
|
|
117 | support, or you are unable to read. |
|
|
118 | |
|
|
119 | 2. Use a simple pixmap and emulate pseudo-transparency. This enables you |
|
|
120 | to use effects other than tinting and shading: Just shade/tint/whatever |
|
|
121 | your picture with gimp: |
|
|
122 | |
|
|
123 | convert wallpaper.jpg -blur 20x20 -modulate 30 background.xpm |
|
|
124 | @@RXVT_NAME@@ -pixmap background.xpm -pe automove-background |
|
|
125 | |
|
|
126 | That works. If you think it doesn't, you lack XPM and Perl support, or you |
|
|
127 | are unable to read. |
|
|
128 | |
|
|
129 | 3. Use an ARGB visual: |
|
|
130 | |
|
|
131 | @@RXVT_NAME@@ -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc |
|
|
132 | |
|
|
133 | This requires XFT support, and the support of your X-server. If that |
|
|
134 | doesn't work for you, blame Xorg and Keith Packard. ARGB visuals aren't |
|
|
135 | there yet, no matter what they claim. Rxvt-Unicode contains the neccessary |
|
|
136 | bugfixes and workarounds for Xft and Xlib to make it work, but that |
|
|
137 | doesn't mean that your WM has the required kludges in place. |
|
|
138 | |
|
|
139 | 4. Use xcompmgr and let it do the job: |
|
|
140 | |
|
|
141 | xprop -frame -f _NET_WM_WINDOW_OPACITY 32c \ |
|
|
142 | -set _NET_WM_WINDOW_OPACITY 0xc0000000 |
|
|
143 | |
|
|
144 | Then click on a window you want to make transparent. Replace C<0xc0000000> |
|
|
145 | by other values to change the degree of opacity. If it doesn't work and |
|
|
146 | your server crashes, you got to keep the pieces. |
|
|
147 | |
69 | =item Isn't rxvt supposed to be small? Don't all those features bloat? |
148 | =head2 Isn't rxvt supposed to be small? Don't all those features bloat? |
70 | |
149 | |
71 | I often get asked about this, and I think, no, they didn't cause extra |
150 | I often get asked about this, and I think, no, they didn't cause extra |
72 | bloat. If you compare a minimal rxvt and a minimal urxvt, you can see |
151 | bloat. If you compare a minimal rxvt and a minimal urxvt, you can see |
73 | that the urxvt binary is larger (due to some encoding tables always being |
152 | that the urxvt binary is larger (due to some encoding tables always being |
74 | compiled in), but it actually uses less memory (RSS) after startup. Even |
153 | compiled in), but it actually uses less memory (RSS) after startup. Even |
… | |
… | |
106 | (21152k + extra 4204k in separate processes) or konsole (22200k + extra |
185 | (21152k + extra 4204k in separate processes) or konsole (22200k + extra |
107 | 43180k in daemons that stay around after exit, plus half a minute of |
186 | 43180k in daemons that stay around after exit, plus half a minute of |
108 | startup time, including the hundreds of warnings it spits out), it fares |
187 | startup time, including the hundreds of warnings it spits out), it fares |
109 | extremely well *g*. |
188 | extremely well *g*. |
110 | |
189 | |
111 | =item Why C++, isn't that unportable/bloated/uncool? |
190 | =head2 Why C++, isn't that unportable/bloated/uncool? |
112 | |
191 | |
113 | Is this a question? :) It comes up very often. The simple answer is: I had |
192 | Is this a question? :) It comes up very often. The simple answer is: I had |
114 | to write it, and C++ allowed me to write and maintain it in a fraction |
193 | to write it, and C++ allowed me to write and maintain it in a fraction |
115 | of the time and effort (which is a scarce resource for me). Put even |
194 | of the time and effort (which is a scarce resource for me). Put even |
116 | shorter: It simply wouldn't exist without C++. |
195 | shorter: It simply wouldn't exist without C++. |
… | |
… | |
140 | /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000) |
219 | /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000) |
141 | |
220 | |
142 | No large bloated libraries (of course, none were linked in statically), |
221 | No large bloated libraries (of course, none were linked in statically), |
143 | except maybe libX11 :) |
222 | except maybe libX11 :) |
144 | |
223 | |
145 | =item Does it support tabs, can I have a tabbed rxvt-unicode? |
224 | =head2 Does it support tabs, can I have a tabbed rxvt-unicode? |
146 | |
225 | |
147 | rxvt-unicode does not directly support tabs. It will work fine with |
226 | Beginning with version 7.3, there is a perl extension that implements a |
148 | tabbing functionality of many window managers or similar tabbing programs, |
227 | simple tabbed terminal. It is installed by default, so any of these should |
149 | and its embedding-features allow it to be embedded into other programs, |
228 | give you tabs: |
150 | as witnessed by F<doc/rxvt-tabbed> or the upcoming C<Gtk2::URxvt> perl |
|
|
151 | module, which features a tabbed urxvt (murxvt) terminal as an example |
|
|
152 | embedding application. |
|
|
153 | |
229 | |
|
|
230 | @@RXVT_NAME@@ -pe tabbed |
|
|
231 | |
|
|
232 | URxvt.perl-ext-common: default,tabbed |
|
|
233 | |
|
|
234 | It will also work fine with tabbing functionality of many window managers |
|
|
235 | or similar tabbing programs, and its embedding-features allow it to be |
|
|
236 | embedded into other programs, as witnessed by F<doc/rxvt-tabbed> or |
|
|
237 | the upcoming C<Gtk2::URxvt> perl module, which features a tabbed urxvt |
|
|
238 | (murxvt) terminal as an example embedding application. |
|
|
239 | |
154 | =item How do I know which rxvt-unicode version I'm using? |
240 | =head2 How do I know which rxvt-unicode version I'm using? |
155 | |
241 | |
156 | The version number is displayed with the usage (-h). Also the escape |
242 | The version number is displayed with the usage (-h). Also the escape |
157 | sequence C<ESC [ 8 n> sets the window title to the version number. When |
243 | sequence C<ESC [ 8 n> sets the window title to the version number. When |
158 | using the @@RXVT_NAME@@c client, the version displayed is that of the |
244 | using the @@RXVT_NAME@@c client, the version displayed is that of the |
159 | daemon. |
245 | daemon. |
160 | |
246 | |
161 | =item I am using Debian GNU/Linux and have a problem... |
247 | =head2 I am using Debian GNU/Linux and have a problem... |
162 | |
248 | |
163 | The Debian GNU/Linux package of rxvt-unicode in sarge contains large |
249 | The Debian GNU/Linux package of rxvt-unicode in sarge contains large |
164 | patches that considerably change the behaviour of rxvt-unicode. Before |
250 | patches that considerably change the behaviour of rxvt-unicode (but |
165 | reporting a bug to the original rxvt-unicode author please download and |
251 | unfortunately this notice has been removed). Before reporting a bug to |
166 | install the genuine version (L<http://software.schmorp.de#rxvt-unicode>) |
252 | the original rxvt-unicode author please download and install the genuine |
167 | and try to reproduce the problem. If you cannot, chances are that the |
253 | version (L<http://software.schmorp.de#rxvt-unicode>) and try to reproduce |
168 | problems are specific to Debian GNU/Linux, in which case it should be |
254 | the problem. If you cannot, chances are that the problems are specific to |
169 | reported via the Debian Bug Tracking System (use C<reportbug> to report |
255 | Debian GNU/Linux, in which case it should be reported via the Debian Bug |
170 | the bug). |
256 | Tracking System (use C<reportbug> to report the bug). |
171 | |
257 | |
172 | For other problems that also affect the Debian package, you can and |
258 | For other problems that also affect the Debian package, you can and |
173 | probably should use the Debian BTS, too, because, after all, it's also a |
259 | probably should use the Debian BTS, too, because, after all, it's also a |
174 | bug in the Debian version and it serves as a reminder for other users that |
260 | bug in the Debian version and it serves as a reminder for other users that |
175 | might encounter the same issue. |
261 | might encounter the same issue. |
176 | |
262 | |
177 | =item I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation? |
263 | =head2 I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation? |
178 | |
264 | |
179 | You should build one binary with the default options. F<configure> |
265 | You should build one binary with the default options. F<configure> |
180 | now enables most useful options, and the trend goes to making them |
266 | now enables most useful options, and the trend goes to making them |
181 | runtime-switchable, too, so there is usually no drawback to enbaling them, |
267 | runtime-switchable, too, so there is usually no drawback to enbaling them, |
182 | except higher disk and possibly memory usage. The perl interpreter should |
268 | except higher disk and possibly memory usage. The perl interpreter should |
… | |
… | |
192 | If you can/want build more binaries, I recommend building a minimal |
278 | If you can/want build more binaries, I recommend building a minimal |
193 | one with C<--disable-everything> (very useful) and a maximal one with |
279 | one with C<--disable-everything> (very useful) and a maximal one with |
194 | C<--enable-everything> (less useful, it will be very big due to a lot of |
280 | C<--enable-everything> (less useful, it will be very big due to a lot of |
195 | encodings built-in that increase download times and are rarely used). |
281 | encodings built-in that increase download times and are rarely used). |
196 | |
282 | |
197 | =item I need to make it setuid/setgid to support utmp/ptys on my OS, is this safe? |
283 | =head2 I need to make it setuid/setgid to support utmp/ptys on my OS, is this safe? |
198 | |
284 | |
199 | Likely not. While I honestly try to make it secure, and am probably not |
285 | It should be, starting with release 7.1. You are encouraged to properly |
200 | bad at it, I think it is simply unreasonable to expect all of freetype |
286 | install urxvt with privileges necessary for your OS now. |
201 | + fontconfig + xft + xlib + perl + ... + rxvt-unicode itself to all be |
|
|
202 | secure. Also, rxvt-unicode disables some options when it detects that it |
|
|
203 | runs setuid or setgid, which is not nice. Besides, with the embedded perl |
|
|
204 | interpreter the possibility for security problems easily multiplies. |
|
|
205 | |
287 | |
206 | Elevated privileges are only required for utmp and pty operations on some |
288 | When rxvt-unicode detects that it runs setuid or setgid, it will fork |
207 | systems (for example, GNU/Linux doesn't need any extra privileges for |
289 | into a helper process for privileged operations (pty handling on some |
208 | ptys, but some need it for utmp support). It is planned to mvoe this into |
290 | systems, utmp/wtmp/lastlog handling on others) and drop privileges |
209 | a forked handler process, but this is not yet done. |
291 | immediately. This is much safer than most other terminals that keep |
|
|
292 | privileges while running (but is more relevant to urxvt, as it contains |
|
|
293 | things as perl interpreters, which might be "helpful" to attackers). |
210 | |
294 | |
211 | So, while setuid/setgid operation is supported and not a problem on your |
295 | This forking is done as the very first within main(), which is very early |
212 | typical single-user-no-other-logins unix desktop, always remember that |
296 | and reduces possible bugs to initialisation code run before main(), or |
213 | its an awful lot of code, most of which isn't checked for security issues |
297 | things like the dynamic loader of your system, which should result in very |
214 | regularly. |
298 | little risk. |
215 | |
299 | |
216 | =item When I log-in to another system it tells me about missing terminfo data? |
300 | =head2 When I log-in to another system it tells me about missing terminfo data? |
217 | |
301 | |
218 | The terminal description used by rxvt-unicode is not as widely available |
302 | The terminal description used by rxvt-unicode is not as widely available |
219 | as that for xterm, or even rxvt (for which the same problem often arises). |
303 | as that for xterm, or even rxvt (for which the same problem often arises). |
220 | |
304 | |
221 | The correct solution for this problem is to install the terminfo, this can |
305 | The correct solution for this problem is to install the terminfo, this can |
… | |
… | |
239 | URxvt.termName: rxvt |
323 | URxvt.termName: rxvt |
240 | |
324 | |
241 | If you don't plan to use B<rxvt> (quite common...) you could also replace |
325 | If you don't plan to use B<rxvt> (quite common...) you could also replace |
242 | the rxvt terminfo file with the rxvt-unicode one. |
326 | the rxvt terminfo file with the rxvt-unicode one. |
243 | |
327 | |
244 | =item C<tic> outputs some error when compiling the terminfo entry. |
328 | =head2 C<tic> outputs some error when compiling the terminfo entry. |
245 | |
329 | |
246 | Most likely it's the empty definition for C<enacs=>. Just replace it by |
330 | Most likely it's the empty definition for C<enacs=>. Just replace it by |
247 | C<enacs=\E[0@> and try again. |
331 | C<enacs=\E[0@> and try again. |
248 | |
332 | |
249 | =item C<bash>'s readline does not work correctly under @@RXVT_NAME@@. |
333 | =head2 C<bash>'s readline does not work correctly under @@RXVT_NAME@@. |
250 | |
334 | |
|
|
335 | See next entry. |
|
|
336 | |
251 | =item I need a termcap file entry. |
337 | =head2 I need a termcap file entry. |
252 | |
338 | |
253 | One reason you might want this is that some distributions or operating |
339 | One reason you might want this is that some distributions or operating |
254 | systems still compile some programs using the long-obsoleted termcap |
340 | systems still compile some programs using the long-obsoleted termcap |
255 | library (Fedora Core's bash is one example) and rely on a termcap entry |
341 | library (Fedora Core's bash is one example) and rely on a termcap entry |
256 | for C<rxvt-unicode>. |
342 | for C<rxvt-unicode>. |
… | |
… | |
282 | :sc=\E7:se=\E[27m:sf=^J:so=\E[7m:sr=\EM:st=\EH:ta=^I:\ |
368 | :sc=\E7:se=\E[27m:sf=^J:so=\E[7m:sr=\EM:st=\EH:ta=^I:\ |
283 | :te=\E[r\E[?1049l:ti=\E[?1049h:ue=\E[24m:up=\E[A:\ |
369 | :te=\E[r\E[?1049l:ti=\E[?1049h:ue=\E[24m:up=\E[A:\ |
284 | :us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\ |
370 | :us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\ |
285 | :vs=\E[?25h: |
371 | :vs=\E[?25h: |
286 | |
372 | |
287 | =item Why does C<ls> no longer have coloured output? |
373 | =head2 Why does C<ls> no longer have coloured output? |
288 | |
374 | |
289 | The C<ls> in the GNU coreutils unfortunately doesn't use terminfo to |
375 | The C<ls> in the GNU coreutils unfortunately doesn't use terminfo to |
290 | decide wether a terminal has colour, but uses it's own configuration |
376 | decide wether a terminal has colour, but uses it's own configuration |
291 | file. Needless to say, C<rxvt-unicode> is not in it's default file (among |
377 | file. Needless to say, C<rxvt-unicode> is not in it's default file (among |
292 | with most other terminals supporting colour). Either add: |
378 | with most other terminals supporting colour). Either add: |
… | |
… | |
297 | |
383 | |
298 | alias ls='ls --color=auto' |
384 | alias ls='ls --color=auto' |
299 | |
385 | |
300 | to your C<.profile> or C<.bashrc>. |
386 | to your C<.profile> or C<.bashrc>. |
301 | |
387 | |
302 | =item Why doesn't vim/emacs etc. use the 88 colour mode? |
388 | =head2 Why doesn't vim/emacs etc. use the 88 colour mode? |
303 | |
389 | |
|
|
390 | See next entry. |
|
|
391 | |
304 | =item Why doesn't vim/emacs etc. make use of italic? |
392 | =head2 Why doesn't vim/emacs etc. make use of italic? |
305 | |
393 | |
|
|
394 | See next entry. |
|
|
395 | |
306 | =item Why are the secondary screen-related options not working properly? |
396 | =head2 Why are the secondary screen-related options not working properly? |
307 | |
397 | |
308 | Make sure you are using C<TERM=rxvt-unicode>. Some pre-packaged |
398 | Make sure you are using C<TERM=rxvt-unicode>. Some pre-packaged |
309 | distributions (most notably Debian GNU/Linux) break rxvt-unicode |
399 | distributions (most notably Debian GNU/Linux) break rxvt-unicode |
310 | by setting C<TERM> to C<rxvt>, which doesn't have these extra |
400 | by setting C<TERM> to C<rxvt>, which doesn't have these extra |
311 | features. Unfortunately, some of these (most notably, again, Debian |
401 | features. Unfortunately, some of these (most notably, again, Debian |
312 | GNU/Linux) furthermore fail to even install the C<rxvt-unicode> terminfo |
402 | GNU/Linux) furthermore fail to even install the C<rxvt-unicode> terminfo |
313 | file, so you will need to install it on your own (See the question B<When |
403 | file, so you will need to install it on your own (See the question B<When |
314 | I log-in to another system it tells me about missing terminfo data?> on |
404 | I log-in to another system it tells me about missing terminfo data?> on |
315 | how to do this). |
405 | how to do this). |
316 | |
406 | |
317 | =item My numerical keypad acts weird and generates differing output? |
407 | =head2 My numerical keypad acts weird and generates differing output? |
318 | |
408 | |
319 | Some Debian GNUL/Linux users seem to have this problem, although no |
409 | Some Debian GNUL/Linux users seem to have this problem, although no |
320 | specific details were reported so far. It is possible that this is caused |
410 | specific details were reported so far. It is possible that this is caused |
321 | by the wrong C<TERM> setting, although the details of wether and how |
411 | by the wrong C<TERM> setting, although the details of wether and how |
322 | this can happen are unknown, as C<TERM=rxvt> should offer a compatible |
412 | this can happen are unknown, as C<TERM=rxvt> should offer a compatible |
323 | keymap. See the answer to the previous question, and please report if that |
413 | keymap. See the answer to the previous question, and please report if that |
324 | helped. |
414 | helped. |
325 | |
415 | |
326 | =item Rxvt-unicode does not seem to understand the selected encoding? |
416 | =head2 Rxvt-unicode does not seem to understand the selected encoding? |
327 | |
417 | |
|
|
418 | See next entry. |
|
|
419 | |
328 | =item Unicode does not seem to work? |
420 | =head2 Unicode does not seem to work? |
329 | |
421 | |
330 | If you encounter strange problems like typing an accented character but |
422 | If you encounter strange problems like typing an accented character but |
331 | getting two unrelated other characters or similar, or if program output is |
423 | getting two unrelated other characters or similar, or if program output is |
332 | subtly garbled, then you should check your locale settings. |
424 | subtly garbled, then you should check your locale settings. |
333 | |
425 | |
… | |
… | |
353 | |
445 | |
354 | If nothing works and you are sure that everything is set correctly then |
446 | If nothing works and you are sure that everything is set correctly then |
355 | you will need to remember a little known fact: Some programs just don't |
447 | you will need to remember a little known fact: Some programs just don't |
356 | support locales :( |
448 | support locales :( |
357 | |
449 | |
358 | =item Why do some characters look so much different than others? |
450 | =head2 Why do some characters look so much different than others? |
359 | |
451 | |
|
|
452 | See next entry. |
|
|
453 | |
360 | =item How does rxvt-unicode choose fonts? |
454 | =head2 How does rxvt-unicode choose fonts? |
361 | |
455 | |
362 | Most fonts do not contain the full range of Unicode, which is |
456 | Most fonts do not contain the full range of Unicode, which is |
363 | fine. Chances are that the font you (or the admin/package maintainer of |
457 | fine. Chances are that the font you (or the admin/package maintainer of |
364 | your system/os) have specified does not cover all the characters you want |
458 | your system/os) have specified does not cover all the characters you want |
365 | to display. |
459 | to display. |
… | |
… | |
383 | |
477 | |
384 | The only limitation is that none of the fonts may be larger than the base |
478 | The only limitation is that none of the fonts may be larger than the base |
385 | font, as the base font defines the terminal character cell size, which |
479 | font, as the base font defines the terminal character cell size, which |
386 | must be the same due to the way terminals work. |
480 | must be the same due to the way terminals work. |
387 | |
481 | |
388 | =item Why do some chinese characters look so different than others? |
482 | =head2 Why do some chinese characters look so different than others? |
389 | |
483 | |
390 | This is because there is a difference between script and language -- |
484 | This is because there is a difference between script and language -- |
391 | rxvt-unicode does not know which language the text that is output is, |
485 | rxvt-unicode does not know which language the text that is output is, |
392 | as it only knows the unicode character codes. If rxvt-unicode first |
486 | as it only knows the unicode character codes. If rxvt-unicode first |
393 | sees a japanese/chinese character, it might choose a japanese font for |
487 | sees a japanese/chinese character, it might choose a japanese font for |
… | |
… | |
408 | has been designed yet). |
502 | has been designed yet). |
409 | |
503 | |
410 | Until then, you might get away with switching fonts at runtime (see L<Can |
504 | Until then, you might get away with switching fonts at runtime (see L<Can |
411 | I switch the fonts at runtime?> later in this document). |
505 | I switch the fonts at runtime?> later in this document). |
412 | |
506 | |
413 | =item Why does rxvt-unicode sometimes leave pixel droppings? |
507 | =head2 Why does rxvt-unicode sometimes leave pixel droppings? |
414 | |
508 | |
415 | Most fonts were not designed for terminal use, which means that character |
509 | Most fonts were not designed for terminal use, which means that character |
416 | size varies a lot. A font that is otherwise fine for terminal use might |
510 | size varies a lot. A font that is otherwise fine for terminal use might |
417 | contain some characters that are simply too wide. Rxvt-unicode will avoid |
511 | contain some characters that are simply too wide. Rxvt-unicode will avoid |
418 | these characters. For characters that are just "a bit" too wide a special |
512 | these characters. For characters that are just "a bit" too wide a special |
… | |
… | |
430 | might be forced to use a different font. |
524 | might be forced to use a different font. |
431 | |
525 | |
432 | All of this is not a problem when using X11 core fonts, as their bounding |
526 | All of this is not a problem when using X11 core fonts, as their bounding |
433 | box data is correct. |
527 | box data is correct. |
434 | |
528 | |
435 | =item On Solaris 9, many line-drawing characters are too wide. |
529 | =head2 On Solaris 9, many line-drawing characters are too wide. |
436 | |
530 | |
437 | Seems to be a known bug, read |
531 | Seems to be a known bug, read |
438 | L<http://nixdoc.net/files/forum/about34198.html>. Some people use the |
532 | L<http://nixdoc.net/files/forum/about34198.html>. Some people use the |
439 | following ugly workaround to get non-double-wide-characters working: |
533 | following ugly workaround to get non-double-wide-characters working: |
440 | |
534 | |
441 | #define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x) |
535 | #define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x) |
442 | |
536 | |
443 | =item My Compose (Multi_key) key is no longer working. |
537 | =head2 My Compose (Multi_key) key is no longer working. |
444 | |
538 | |
445 | The most common causes for this are that either your locale is not set |
539 | The most common causes for this are that either your locale is not set |
446 | correctly, or you specified a B<preeditStyle> that is not supported by |
540 | correctly, or you specified a B<preeditStyle> that is not supported by |
447 | your input method. For example, if you specified B<OverTheSpot> and |
541 | your input method. For example, if you specified B<OverTheSpot> and |
448 | your input method (e.g. the default input method handling Compose keys) |
542 | your input method (e.g. the default input method handling Compose keys) |
… | |
… | |
450 | rxvt-unicode will continue without an input method. |
544 | rxvt-unicode will continue without an input method. |
451 | |
545 | |
452 | In this case either do not specify a B<preeditStyle> or specify more than |
546 | In this case either do not specify a B<preeditStyle> or specify more than |
453 | one pre-edit style, such as B<OverTheSpot,Root,None>. |
547 | one pre-edit style, such as B<OverTheSpot,Root,None>. |
454 | |
548 | |
455 | =item I cannot type C<Ctrl-Shift-2> to get an ASCII NUL character due to ISO 14755 |
549 | =head2 I cannot type C<Ctrl-Shift-2> to get an ASCII NUL character due to ISO 14755 |
456 | |
550 | |
457 | Either try C<Ctrl-2> alone (it often is mapped to ASCII NUL even on |
551 | Either try C<Ctrl-2> alone (it often is mapped to ASCII NUL even on |
458 | international keyboards) or simply use ISO 14755 support to your |
552 | international keyboards) or simply use ISO 14755 support to your |
459 | advantage, typing <Ctrl-Shift-0> to get a ASCII NUL. This works for other |
553 | advantage, typing <Ctrl-Shift-0> to get a ASCII NUL. This works for other |
460 | codes, too, such as C<Ctrl-Shift-1-d> to type the default telnet escape |
554 | codes, too, such as C<Ctrl-Shift-1-d> to type the default telnet escape |
461 | character and so on. |
555 | character and so on. |
462 | |
556 | |
463 | =item How can I keep rxvt-unicode from using reverse video so much? |
557 | =head2 How can I keep rxvt-unicode from using reverse video so much? |
464 | |
558 | |
465 | First of all, make sure you are running with the right terminal settings |
559 | First of all, make sure you are running with the right terminal settings |
466 | (C<TERM=rxvt-unicode>), which will get rid of most of these effects. Then |
560 | (C<TERM=rxvt-unicode>), which will get rid of most of these effects. Then |
467 | make sure you have specified colours for italic and bold, as otherwise |
561 | make sure you have specified colours for italic and bold, as otherwise |
468 | rxvt-unicode might use reverse video to simulate the effect: |
562 | rxvt-unicode might use reverse video to simulate the effect: |
469 | |
563 | |
470 | URxvt.colorBD: white |
564 | URxvt.colorBD: white |
471 | URxvt.colorIT: green |
565 | URxvt.colorIT: green |
472 | |
566 | |
473 | =item Some programs assume totally weird colours (red instead of blue), how can I fix that? |
567 | =head2 Some programs assume totally weird colours (red instead of blue), how can I fix that? |
474 | |
568 | |
475 | For some unexplainable reason, some rare programs assume a very weird |
569 | For some unexplainable reason, some rare programs assume a very weird |
476 | colour palette when confronted with a terminal with more than the standard |
570 | colour palette when confronted with a terminal with more than the standard |
477 | 8 colours (rxvt-unicode supports 88). The right fix is, of course, to fix |
571 | 8 colours (rxvt-unicode supports 88). The right fix is, of course, to fix |
478 | these programs not to assume non-ISO colours without very good reasons. |
572 | these programs not to assume non-ISO colours without very good reasons. |
479 | |
573 | |
480 | In the meantime, you can either edit your C<rxvt-unicode> terminfo |
574 | In the meantime, you can either edit your C<rxvt-unicode> terminfo |
481 | definition to only claim 8 colour support or use C<TERM=rxvt>, which will |
575 | definition to only claim 8 colour support or use C<TERM=rxvt>, which will |
482 | fix colours but keep you from using other rxvt-unicode features. |
576 | fix colours but keep you from using other rxvt-unicode features. |
483 | |
577 | |
484 | =item I am on FreeBSD and rxvt-unicode does not seem to work at all. |
578 | =head2 I am on FreeBSD and rxvt-unicode does not seem to work at all. |
485 | |
579 | |
486 | Rxvt-unicode requires the symbol C<__STDC_ISO_10646__> to be defined |
580 | Rxvt-unicode requires the symbol C<__STDC_ISO_10646__> to be defined |
487 | in your compile environment, or an implementation that implements it, |
581 | in your compile environment, or an implementation that implements it, |
488 | wether it defines the symbol or not. C<__STDC_ISO_10646__> requires that |
582 | wether it defines the symbol or not. C<__STDC_ISO_10646__> requires that |
489 | B<wchar_t> is represented as unicode. |
583 | B<wchar_t> is represented as unicode. |
… | |
… | |
511 | |
605 | |
512 | The rxvt-unicode author insists that the right way to fix this is in the |
606 | The rxvt-unicode author insists that the right way to fix this is in the |
513 | system libraries once and for all, instead of forcing every app to carry |
607 | system libraries once and for all, instead of forcing every app to carry |
514 | complete replacements for them :) |
608 | complete replacements for them :) |
515 | |
609 | |
516 | =item I use Solaris 9 and it doesn't compile/work/etc. |
610 | =head2 I use Solaris 9 and it doesn't compile/work/etc. |
517 | |
611 | |
518 | Try the diff in F<doc/solaris9.patch> as a base. It fixes the worst |
612 | Try the diff in F<doc/solaris9.patch> as a base. It fixes the worst |
519 | problems with C<wcwidth> and a compile problem. |
613 | problems with C<wcwidth> and a compile problem. |
520 | |
614 | |
521 | =item How can I use rxvt-unicode under cygwin? |
615 | =head2 How can I use rxvt-unicode under cygwin? |
522 | |
616 | |
523 | rxvt-unicode should compile and run out of the box on cygwin, using |
617 | rxvt-unicode should compile and run out of the box on cygwin, using |
524 | the X11 libraries that come with cygwin. libW11 emulation is no |
618 | the X11 libraries that come with cygwin. libW11 emulation is no |
525 | longer supported (and makes no sense, either, as it only supported a |
619 | longer supported (and makes no sense, either, as it only supported a |
526 | single font). I recommend starting the X-server in C<-multiwindow> or |
620 | single font). I recommend starting the X-server in C<-multiwindow> or |
… | |
… | |
529 | |
623 | |
530 | At the time of this writing, cygwin didn't seem to support any multi-byte |
624 | At the time of this writing, cygwin didn't seem to support any multi-byte |
531 | encodings (you might try C<LC_CTYPE=C-UTF-8>), so you are likely limited |
625 | encodings (you might try C<LC_CTYPE=C-UTF-8>), so you are likely limited |
532 | to 8-bit encodings. |
626 | to 8-bit encodings. |
533 | |
627 | |
534 | =item How does rxvt-unicode determine the encoding to use? |
628 | =head2 How does rxvt-unicode determine the encoding to use? |
535 | |
629 | |
|
|
630 | See next entry. |
|
|
631 | |
536 | =item Is there an option to switch encodings? |
632 | =head2 Is there an option to switch encodings? |
537 | |
633 | |
538 | Unlike some other terminals, rxvt-unicode has no encoding switch, and no |
634 | Unlike some other terminals, rxvt-unicode has no encoding switch, and no |
539 | specific "utf-8" mode, such as xterm. In fact, it doesn't even know about |
635 | specific "utf-8" mode, such as xterm. In fact, it doesn't even know about |
540 | UTF-8 or any other encodings with respect to terminal I/O. |
636 | UTF-8 or any other encodings with respect to terminal I/O. |
541 | |
637 | |
… | |
… | |
566 | rxvt-unicode. |
662 | rxvt-unicode. |
567 | |
663 | |
568 | If you want to use a specific encoding you have to make sure you start |
664 | If you want to use a specific encoding you have to make sure you start |
569 | rxvt-unicode with the correct C<LC_CTYPE> category. |
665 | rxvt-unicode with the correct C<LC_CTYPE> category. |
570 | |
666 | |
571 | =item Can I switch locales at runtime? |
667 | =head2 Can I switch locales at runtime? |
572 | |
668 | |
573 | Yes, using an escape sequence. Try something like this, which sets |
669 | Yes, using an escape sequence. Try something like this, which sets |
574 | rxvt-unicode's idea of C<LC_CTYPE>. |
670 | rxvt-unicode's idea of C<LC_CTYPE>. |
575 | |
671 | |
576 | printf '\e]701;%s\007' ja_JP.SJIS |
672 | printf '\e]701;%s\007' ja_JP.SJIS |
… | |
… | |
588 | |
684 | |
589 | You can also use xterm's C<luit> program, which usually works fine, except |
685 | You can also use xterm's C<luit> program, which usually works fine, except |
590 | for some locales where character width differs between program- and |
686 | for some locales where character width differs between program- and |
591 | rxvt-unicode-locales. |
687 | rxvt-unicode-locales. |
592 | |
688 | |
593 | =item Can I switch the fonts at runtime? |
689 | =head2 Can I switch the fonts at runtime? |
594 | |
690 | |
595 | Yes, using an escape sequence. Try something like this, which has the same |
691 | Yes, using an escape sequence. Try something like this, which has the same |
596 | effect as using the C<-fn> switch, and takes effect immediately: |
692 | effect as using the C<-fn> switch, and takes effect immediately: |
597 | |
693 | |
598 | printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic" |
694 | printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic" |
… | |
… | |
601 | japanese font), but you have to switch to chinese temporarily, where |
697 | japanese font), but you have to switch to chinese temporarily, where |
602 | japanese fonts would only be in your way. |
698 | japanese fonts would only be in your way. |
603 | |
699 | |
604 | You can think of this as a kind of manual ISO-2022 switching. |
700 | You can think of this as a kind of manual ISO-2022 switching. |
605 | |
701 | |
606 | =item Why do italic characters look as if clipped? |
702 | =head2 Why do italic characters look as if clipped? |
607 | |
703 | |
608 | Many fonts have difficulties with italic characters and hinting. For |
704 | Many fonts have difficulties with italic characters and hinting. For |
609 | example, the otherwise very nicely hinted font C<xft:Bitstream Vera Sans |
705 | example, the otherwise very nicely hinted font C<xft:Bitstream Vera Sans |
610 | Mono> completely fails in it's italic face. A workaround might be to |
706 | Mono> completely fails in it's italic face. A workaround might be to |
611 | enable freetype autohinting, i.e. like this: |
707 | enable freetype autohinting, i.e. like this: |
612 | |
708 | |
613 | URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true |
709 | URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true |
614 | URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true |
710 | URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true |
615 | |
711 | |
616 | =item My input method wants <some encoding> but I want UTF-8, what can I do? |
712 | =head2 My input method wants <some encoding> but I want UTF-8, what can I do? |
617 | |
713 | |
618 | You can specify separate locales for the input method and the rest of the |
714 | You can specify separate locales for the input method and the rest of the |
619 | terminal, using the resource C<imlocale>: |
715 | terminal, using the resource C<imlocale>: |
620 | |
716 | |
621 | URxvt.imlocale: ja_JP.EUC-JP |
717 | URxvt.imlocale: ja_JP.EUC-JP |
… | |
… | |
623 | Now you can start your terminal with C<LC_CTYPE=ja_JP.UTF-8> and still |
719 | Now you can start your terminal with C<LC_CTYPE=ja_JP.UTF-8> and still |
624 | use your input method. Please note, however, that you will not be able to |
720 | use your input method. Please note, however, that you will not be able to |
625 | input characters outside C<EUC-JP> in a normal way then, as your input |
721 | input characters outside C<EUC-JP> in a normal way then, as your input |
626 | method limits you. |
722 | method limits you. |
627 | |
723 | |
628 | =item Rxvt-unicode crashes when the X Input Method changes or exits. |
724 | =head2 Rxvt-unicode crashes when the X Input Method changes or exits. |
629 | |
725 | |
630 | Unfortunately, this is unavoidable, as the XIM protocol is racy by |
726 | Unfortunately, this is unavoidable, as the XIM protocol is racy by |
631 | design. Applications can avoid some crashes at the expense of memory |
727 | design. Applications can avoid some crashes at the expense of memory |
632 | leaks, and Input Methods can avoid some crashes by careful ordering at |
728 | leaks, and Input Methods can avoid some crashes by careful ordering at |
633 | exit time. B<kinput2> (and derived input methods) generally succeeds, |
729 | exit time. B<kinput2> (and derived input methods) generally succeeds, |
634 | while B<SCIM> (or similar input methods) fails. In the end, however, |
730 | while B<SCIM> (or similar input methods) fails. In the end, however, |
635 | crashes cannot be completely avoided even if both sides cooperate. |
731 | crashes cannot be completely avoided even if both sides cooperate. |
636 | |
732 | |
637 | So the only workaround is not to kill your Input Method Servers. |
733 | So the only workaround is not to kill your Input Method Servers. |
638 | |
734 | |
639 | =item Rxvt-unicode uses gobs of memory, how can I reduce that? |
735 | =head2 Rxvt-unicode uses gobs of memory, how can I reduce that? |
640 | |
736 | |
641 | Rxvt-unicode tries to obey the rule of not charging you for something you |
737 | Rxvt-unicode tries to obey the rule of not charging you for something you |
642 | don't use. One thing you should try is to configure out all settings that |
738 | don't use. One thing you should try is to configure out all settings that |
643 | you don't need, for example, Xft support is a resource hog by design, |
739 | you don't need, for example, Xft support is a resource hog by design, |
644 | when used. Compiling it out ensures that no Xft font will be loaded |
740 | when used. Compiling it out ensures that no Xft font will be loaded |
… | |
… | |
649 | 6 bytes per screen cell. For a 160x?? window this amounts to almost a |
745 | 6 bytes per screen cell. For a 160x?? window this amounts to almost a |
650 | kilobyte per line. A scrollback buffer of 10000 lines will then (if full) |
746 | kilobyte per line. A scrollback buffer of 10000 lines will then (if full) |
651 | use 10 Megabytes of memory. With C<--enable-unicode3> it gets worse, as |
747 | use 10 Megabytes of memory. With C<--enable-unicode3> it gets worse, as |
652 | rxvt-unicode then uses 8 bytes per screen cell. |
748 | rxvt-unicode then uses 8 bytes per screen cell. |
653 | |
749 | |
654 | =item Can I speed up Xft rendering somehow? |
750 | =head2 Can I speed up Xft rendering somehow? |
655 | |
751 | |
656 | Yes, the most obvious way to speed it up is to avoid Xft entirely, as |
752 | Yes, the most obvious way to speed it up is to avoid Xft entirely, as |
657 | it is simply slow. If you still want Xft fonts you might try to disable |
753 | it is simply slow. If you still want Xft fonts you might try to disable |
658 | antialiasing (by appending C<:antialias=false>), which saves lots of |
754 | antialiasing (by appending C<:antialias=false>), which saves lots of |
659 | memory and also speeds up rendering considerably. |
755 | memory and also speeds up rendering considerably. |
660 | |
756 | |
661 | =item Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong? |
757 | =head2 Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong? |
662 | |
758 | |
663 | Rxvt-unicode will use whatever you specify as a font. If it needs to |
759 | Rxvt-unicode will use whatever you specify as a font. If it needs to |
664 | fall back to it's default font search list it will prefer X11 core |
760 | fall back to it's default font search list it will prefer X11 core |
665 | fonts, because they are small and fast, and then use Xft fonts. It has |
761 | fonts, because they are small and fast, and then use Xft fonts. It has |
666 | antialiasing disabled for most of them, because the author thinks they |
762 | antialiasing disabled for most of them, because the author thinks they |
667 | look best that way. |
763 | look best that way. |
668 | |
764 | |
669 | If you want antialiasing, you have to specify the fonts manually. |
765 | If you want antialiasing, you have to specify the fonts manually. |
670 | |
766 | |
671 | =item Mouse cut/paste suddenly no longer works. |
767 | =head2 Mouse cut/paste suddenly no longer works. |
672 | |
768 | |
673 | Make sure that mouse reporting is actually turned off since killing |
769 | Make sure that mouse reporting is actually turned off since killing |
674 | some editors prematurely may leave the mouse in mouse report mode. I've |
770 | some editors prematurely may leave the mouse in mouse report mode. I've |
675 | heard that tcsh may use mouse reporting unless it otherwise specified. A |
771 | heard that tcsh may use mouse reporting unless it otherwise specified. A |
676 | quick check is to see if cut/paste works when the Alt or Shift keys are |
772 | quick check is to see if cut/paste works when the Alt or Shift keys are |
677 | depressed. |
773 | depressed. |
678 | |
774 | |
679 | =item What's with this bold/blink stuff? |
775 | =head2 What's with this bold/blink stuff? |
680 | |
776 | |
681 | If no bold colour is set via C<colorBD:>, bold will invert text using the |
777 | If no bold colour is set via C<colorBD:>, bold will invert text using the |
682 | standard foreground colour. |
778 | standard foreground colour. |
683 | |
779 | |
684 | For the standard background colour, blinking will actually make the |
780 | For the standard background colour, blinking will actually make the |
… | |
… | |
691 | |
787 | |
692 | color0-7 are the low-intensity colors. |
788 | color0-7 are the low-intensity colors. |
693 | |
789 | |
694 | color8-15 are the corresponding high-intensity colors. |
790 | color8-15 are the corresponding high-intensity colors. |
695 | |
791 | |
696 | =item I don't like the screen colors. How do I change them? |
792 | =head2 I don't like the screen colors. How do I change them? |
697 | |
793 | |
698 | You can change the screen colors at run-time using F<~/.Xdefaults> |
794 | You can change the screen colors at run-time using F<~/.Xdefaults> |
699 | resources (or as long-options). |
795 | resources (or as long-options). |
700 | |
796 | |
701 | Here are values that are supposed to resemble a VGA screen, |
797 | Here are values that are supposed to resemble a VGA screen, |
… | |
… | |
739 | URxvt.color6: #73f7ff |
835 | URxvt.color6: #73f7ff |
740 | URxvt.color14: #73f7ff |
836 | URxvt.color14: #73f7ff |
741 | URxvt.color7: #e1dddd |
837 | URxvt.color7: #e1dddd |
742 | URxvt.color15: #e1dddd |
838 | URxvt.color15: #e1dddd |
743 | |
839 | |
744 | =item How can I start @@RXVT_NAME@@d in a race-free way? |
840 | =head2 How can I start @@RXVT_NAME@@d in a race-free way? |
745 | |
841 | |
746 | Try C<@@RXVT_NAME@@d -f -o>, which tells @@RXVT_NAME@@d to open the |
842 | Try C<@@RXVT_NAME@@d -f -o>, which tells @@RXVT_NAME@@d to open the |
747 | display, create the listening socket and then fork. |
843 | display, create the listening socket and then fork. |
748 | |
844 | |
749 | =item What's with the strange Backspace/Delete key behaviour? |
845 | =head2 What's with the strange Backspace/Delete key behaviour? |
750 | |
846 | |
751 | Assuming that the physical Backspace key corresponds to the |
847 | Assuming that the physical Backspace key corresponds to the |
752 | BackSpace keysym (not likely for Linux ... see the following |
848 | BackSpace keysym (not likely for Linux ... see the following |
753 | question) there are two standard values that can be used for |
849 | question) there are two standard values that can be used for |
754 | Backspace: C<^H> and C<^?>. |
850 | Backspace: C<^H> and C<^?>. |
… | |
… | |
800 | some editors (vim I'm told) expect Backspace = ^H, |
896 | some editors (vim I'm told) expect Backspace = ^H, |
801 | GNU Emacs (and Emacs-like editors) use ^H for help. |
897 | GNU Emacs (and Emacs-like editors) use ^H for help. |
802 | |
898 | |
803 | Perhaps someday this will all be resolved in a consistent manner. |
899 | Perhaps someday this will all be resolved in a consistent manner. |
804 | |
900 | |
805 | =item I don't like the key-bindings. How do I change them? |
901 | =head2 I don't like the key-bindings. How do I change them? |
806 | |
902 | |
807 | There are some compile-time selections available via configure. Unless |
903 | There are some compile-time selections available via configure. Unless |
808 | you have run "configure" with the C<--disable-resources> option you can |
904 | you have run "configure" with the C<--disable-resources> option you can |
809 | use the `keysym' resource to alter the keystrings associated with keysyms. |
905 | use the `keysym' resource to alter the keystrings associated with keysyms. |
810 | |
906 | |
… | |
… | |
831 | URxvt.keysym.M-C-a: list \033<M-C- abcdefghijklmnopqrstuvwxyz > |
927 | URxvt.keysym.M-C-a: list \033<M-C- abcdefghijklmnopqrstuvwxyz > |
832 | URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007 |
928 | URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007 |
833 | |
929 | |
834 | See some more examples in the documentation for the B<keysym> resource. |
930 | See some more examples in the documentation for the B<keysym> resource. |
835 | |
931 | |
836 | =item I'm using keyboard model XXX that has extra Prior/Next/Insert keys. |
932 | =head2 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. |
837 | How do I make use of them? For example, the Sun Keyboard type 4 |
|
|
838 | has the following mappings that rxvt-unicode doesn't recognize. |
|
|
839 | |
933 | |
840 | KP_Insert == Insert |
934 | KP_Insert == Insert |
841 | F22 == Print |
935 | F22 == Print |
842 | F27 == Home |
936 | F27 == Home |
843 | F29 == Prior |
937 | F29 == Prior |
… | |
… | |
846 | |
940 | |
847 | Rather than have rxvt-unicode try to accommodate all the various possible |
941 | Rather than have rxvt-unicode try to accommodate all the various possible |
848 | keyboard mappings, it is better to use `xmodmap' to remap the keys as |
942 | keyboard mappings, it is better to use `xmodmap' to remap the keys as |
849 | required for your particular machine. |
943 | required for your particular machine. |
850 | |
944 | |
851 | =item How do I distinguish wether I'm running rxvt-unicode or a regular xterm? |
945 | =head2 How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc. |
852 | I need this to decide about setting colors etc. |
|
|
853 | |
946 | |
854 | rxvt and rxvt-unicode always export the variable "COLORTERM", so you can |
947 | rxvt and rxvt-unicode always export the variable "COLORTERM", so you can |
855 | check and see if that is set. Note that several programs, JED, slrn, |
948 | check and see if that is set. Note that several programs, JED, slrn, |
856 | Midnight Commander automatically check this variable to decide whether or |
949 | Midnight Commander automatically check this variable to decide whether or |
857 | not to use color. |
950 | not to use color. |
858 | |
951 | |
859 | =item How do I set the correct, full IP address for the DISPLAY variable? |
952 | =head2 How do I set the correct, full IP address for the DISPLAY variable? |
860 | |
953 | |
861 | If you've compiled rxvt-unicode with DISPLAY_IS_IP and have enabled |
954 | If you've compiled rxvt-unicode with DISPLAY_IS_IP and have enabled |
862 | insecure mode then it is possible to use the following shell script |
955 | insecure mode then it is possible to use the following shell script |
863 | snippets to correctly set the display. If your version of rxvt-unicode |
956 | snippets to correctly set the display. If your version of rxvt-unicode |
864 | wasn't also compiled with ESCZ_ANSWER (as assumed in these snippets) then |
957 | wasn't also compiled with ESCZ_ANSWER (as assumed in these snippets) then |
… | |
… | |
879 | echo -n '^[[7n' # query the rxvt we are in for the DISPLAY string |
972 | echo -n '^[[7n' # query the rxvt we are in for the DISPLAY string |
880 | read DISPLAY # set it in our local shell |
973 | read DISPLAY # set it in our local shell |
881 | fi |
974 | fi |
882 | fi |
975 | fi |
883 | |
976 | |
884 | =item How do I compile the manual pages for myself? |
977 | =head2 How do I compile the manual pages for myself? |
885 | |
978 | |
886 | You need to have a recent version of perl installed as F</usr/bin/perl>, |
979 | You need to have a recent version of perl installed as F</usr/bin/perl>, |
887 | one that comes with F<pod2man>, F<pod2text> and F<pod2html>. Then go to |
980 | one that comes with F<pod2man>, F<pod2text> and F<pod2html>. Then go to |
888 | the doc subdirectory and enter C<make alldoc>. |
981 | the doc subdirectory and enter C<make alldoc>. |
889 | |
982 | |
890 | =item My question isn't answered here, can I ask a human? |
983 | =head2 My question isn't answered here, can I ask a human? |
891 | |
984 | |
892 | Before sending me mail, you could go to IRC: C<irc.freenode.net>, |
985 | Before sending me mail, you could go to IRC: C<irc.freenode.net>, |
893 | channel C<#rxvt-unicode> has some rxvt-unicode enthusiasts that might be |
986 | channel C<#rxvt-unicode> has some rxvt-unicode enthusiasts that might be |
894 | interested in learning about new and exciting problems (but not FAQs :). |
987 | interested in learning about new and exciting problems (but not FAQs :). |
895 | |
|
|
896 | =back |
|
|
897 | |
988 | |
898 | =head1 RXVT TECHNICAL REFERENCE |
989 | =head1 RXVT TECHNICAL REFERENCE |
899 | |
990 | |
900 | =head1 DESCRIPTION |
991 | =head1 DESCRIPTION |
901 | |
992 | |
… | |
… | |
1669 | B<< C<Ps = 12> >> Change colour of text cursor foreground to B<< C<Pt> >> |
1760 | B<< C<Ps = 12> >> Change colour of text cursor foreground to B<< C<Pt> >> |
1670 | B<< C<Ps = 13> >> Change colour of mouse foreground to B<< C<Pt> >> |
1761 | B<< C<Ps = 13> >> Change colour of mouse foreground to B<< C<Pt> >> |
1671 | B<< C<Ps = 17> >> Change colour of highlight characters to B<< C<Pt> >> |
1762 | B<< C<Ps = 17> >> Change colour of highlight characters to B<< C<Pt> >> |
1672 | B<< C<Ps = 18> >> Change colour of bold characters to B<< C<Pt> >> [deprecated, see 706] |
1763 | B<< C<Ps = 18> >> Change colour of bold characters to B<< C<Pt> >> [deprecated, see 706] |
1673 | B<< C<Ps = 19> >> Change colour of underlined characters to B<< C<Pt> >> [deprecated, see 707] |
1764 | B<< C<Ps = 19> >> Change colour of underlined characters to B<< C<Pt> >> [deprecated, see 707] |
1674 | B<< C<Ps = 20> >> Change default background to B<< C<Pt> >> |
1765 | B<< C<Ps = 20> >> Change background pixmap parameters (see section XPM) (Compile XPM). |
1675 | B<< C<Ps = 39> >> Change default foreground colour to B<< C<Pt> >>. |
1766 | B<< C<Ps = 39> >> Change default foreground colour to B<< C<Pt> >>. |
1676 | B<< C<Ps = 46> >> Change Log File to B<< C<Pt> >> I<unimplemented> |
1767 | B<< C<Ps = 46> >> Change Log File to B<< C<Pt> >> I<unimplemented> |
1677 | B<< C<Ps = 49> >> Change default background colour to B<< C<Pt> >>. |
1768 | B<< C<Ps = 49> >> Change default background colour to B<< C<Pt> >>. |
1678 | B<< C<Ps = 50> >> Set fontset to B<< C<Pt> >>, with the following special values of B<< C<Pt> >> (B<rxvt>) B<< C<#+n> >> change up B<< C<n> >> B<< C<#-n> >> change down B<< C<n> >> if B<< C<n> >> is missing of 0, a value of 1 is used I<empty> change to font0 B<< C<n> >> change to font B<< C<n> >> |
1769 | B<< C<Ps = 50> >> Set fontset to B<< C<Pt> >>, with the following special values of B<< C<Pt> >> (B<rxvt>) B<< C<#+n> >> change up B<< C<n> >> B<< C<#-n> >> change down B<< C<n> >> if B<< C<n> >> is missing of 0, a value of 1 is used I<empty> change to font0 B<< C<n> >> change to font B<< C<n> >> |
1679 | B<< C<Ps = 55> >> Log all scrollback buffer and all of screen to B<< C<Pt> >> |
1770 | B<< C<Ps = 55> >> Log all scrollback buffer and all of screen to B<< C<Pt> >> |
1680 | B<< C<Ps = 701> >> Change current locale to B<< C<Pt> >>, or, if B<< C<Pt> >> is B<< C<?> >>, return the current locale (Compile frills). |
1771 | B<< C<Ps = 701> >> Change current locale to B<< C<Pt> >>, or, if B<< C<Pt> >> is B<< C<?> >>, return the current locale (Compile frills). |
|
|
1772 | B<< C<Ps = 702> >> Request version if B<< C<Pt> >> is B<< C<?> >>, returning C<rxvt-unicode>, the resource name, the major and minor version numbers, e.g. C<ESC ] 702 ; rxvt-unicode ; urxvt ; 7 ; 4 ST>. |
1681 | B<< C<Ps = 704> >> Change colour of italic characters to B<< C<Pt> >> |
1773 | B<< C<Ps = 704> >> Change colour of italic characters to B<< C<Pt> >> |
1682 | B<< C<Ps = 705> >> Change background pixmap tint colour to B<< C<Pt> >> (Compile transparency). |
1774 | B<< C<Ps = 705> >> Change background pixmap tint colour to B<< C<Pt> >> (Compile transparency). |
1683 | B<< C<Ps = 706> >> Change colour of bold characters to B<< C<Pt> >> |
1775 | B<< C<Ps = 706> >> Change colour of bold characters to B<< C<Pt> >> |
1684 | B<< C<Ps = 707> >> Change colour of underlined characters to B<< C<Pt> >> |
1776 | B<< C<Ps = 707> >> Change colour of underlined characters to B<< C<Pt> >> |
1685 | B<< C<Ps = 710> >> Set normal fontset to B<< C<Pt> >>. Same as C<Ps = 50>. |
1777 | B<< C<Ps = 710> >> Set normal fontset to B<< C<Pt> >>. Same as C<Ps = 50>. |
… | |
… | |
1948 | alternative input methods (e.g. kinput2) and will also correctly |
2040 | alternative input methods (e.g. kinput2) and will also correctly |
1949 | set up the input for people using dead keys or compose keys. |
2041 | set up the input for people using dead keys or compose keys. |
1950 | |
2042 | |
1951 | =item --enable-unicode3 (default: off) |
2043 | =item --enable-unicode3 (default: off) |
1952 | |
2044 | |
|
|
2045 | Recommended to stay off unless you really need non-BMP characters. |
|
|
2046 | |
1953 | Enable direct support for displaying unicode codepoints above |
2047 | Enable direct support for displaying unicode codepoints above |
1954 | 65535 (the basic multilingual page). This increases storage |
2048 | 65535 (the basic multilingual page). This increases storage |
1955 | requirements per character from 2 to 4 bytes. X11 fonts do not yet |
2049 | requirements per character from 2 to 4 bytes. X11 fonts do not yet |
1956 | support these extra characters, but Xft does. |
2050 | support these extra characters, but Xft does. |
1957 | |
2051 | |
… | |
… | |
1967 | composite characters. This is required for proper viewing of text |
2061 | composite characters. This is required for proper viewing of text |
1968 | where accents are encoded as seperate unicode characters. This is |
2062 | where accents are encoded as seperate unicode characters. This is |
1969 | done by using precomposited characters when available or creating |
2063 | done by using precomposited characters when available or creating |
1970 | new pseudo-characters when no precomposed form exists. |
2064 | new pseudo-characters when no precomposed form exists. |
1971 | |
2065 | |
1972 | Without --enable-unicode3, the number of additional precomposed characters |
2066 | Without --enable-unicode3, the number of additional precomposed |
1973 | is rather limited (2048, if this is full, rxvt-unicode will use the |
2067 | characters is somewhat limited (the 6400 private use characters will be |
1974 | private use area, extending the number of combinations to 8448). With |
|
|
1975 | --enable-unicode3, no practical limit exists. |
2068 | (ab-)used). With --enable-unicode3, no practical limit exists. |
1976 | |
2069 | |
1977 | This option will also enable storage (but not display) of characters |
2070 | This option will also enable storage (but not display) of characters |
1978 | beyond plane 0 (>65535) when --enable-unicode3 was not specified. |
2071 | beyond plane 0 (>65535) when --enable-unicode3 was not specified. |
1979 | |
2072 | |
1980 | The combining table also contains entries for arabic presentation forms, |
2073 | The combining table also contains entries for arabic presentation forms, |
1981 | but these are not currently used. Bug me if you want these to be used (and |
2074 | but these are not currently used. Bug me if you want these to be used (and |
1982 | tell me how these are to be used...). |
2075 | tell me how these are to be used...). |
1983 | |
2076 | |
1984 | =item --enable-fallback(=CLASS) (default: Rxvt) |
2077 | =item --enable-fallback(=CLASS) (default: Rxvt) |
1985 | |
2078 | |
1986 | When reading resource settings, also read settings for class CLASS. To disable resource fallback use --disable-fallback. |
2079 | When reading resource settings, also read settings for class CLASS. To |
|
|
2080 | disable resource fallback use --disable-fallback. |
1987 | |
2081 | |
1988 | =item --with-res-name=NAME (default: urxvt) |
2082 | =item --with-res-name=NAME (default: urxvt) |
1989 | |
2083 | |
1990 | Use the given name as default application name when |
2084 | Use the given name as default application name when |
1991 | reading resources. Specify --with-res-name=rxvt to replace rxvt. |
2085 | reading resources. Specify --with-res-name=rxvt to replace rxvt. |
… | |
… | |
2045 | =item --enable-plain-scroll (default: on) |
2139 | =item --enable-plain-scroll (default: on) |
2046 | |
2140 | |
2047 | Add support for a very unobtrusive, plain-looking scrollbar that |
2141 | Add support for a very unobtrusive, plain-looking scrollbar that |
2048 | is the favourite of the rxvt-unicode author, having used it for |
2142 | is the favourite of the rxvt-unicode author, having used it for |
2049 | many years. |
2143 | many years. |
2050 | |
|
|
2051 | =item --enable-half-shadow (default: off) |
|
|
2052 | |
|
|
2053 | Make shadows on the scrollbar only half the normal width & height. |
|
|
2054 | only applicable to rxvt scrollbars. |
|
|
2055 | |
2144 | |
2056 | =item --enable-ttygid (default: off) |
2145 | =item --enable-ttygid (default: off) |
2057 | |
2146 | |
2058 | Change tty device setting to group "tty" - only use this if |
2147 | Change tty device setting to group "tty" - only use this if |
2059 | your system uses this type of security. |
2148 | your system uses this type of security. |
… | |
… | |
2086 | |
2175 | |
2087 | MWM-hints |
2176 | MWM-hints |
2088 | EWMH-hints (pid, utf8 names) and protocols (ping) |
2177 | EWMH-hints (pid, utf8 names) and protocols (ping) |
2089 | seperate underline colour (-underlineColor) |
2178 | seperate underline colour (-underlineColor) |
2090 | settable border widths and borderless switch (-w, -b, -bl) |
2179 | settable border widths and borderless switch (-w, -b, -bl) |
|
|
2180 | visual depth selection (-depth) |
2091 | settable extra linespacing /-lsp) |
2181 | settable extra linespacing /-lsp) |
2092 | iso-14755-2 and -3, and visual feedback |
2182 | iso-14755-2 and -3, and visual feedback |
2093 | backindex and forwardindex escape sequence |
|
|
2094 | window op and some xterm/OSC escape sequences |
|
|
2095 | tripleclickwords (-tcw) |
2183 | tripleclickwords (-tcw) |
2096 | settable insecure mode (-insecure) |
2184 | settable insecure mode (-insecure) |
2097 | keysym remapping support |
2185 | keysym remapping support |
2098 | cursor blinking and underline cursor (-cb, -uc) |
2186 | cursor blinking and underline cursor (-cb, -uc) |
2099 | XEmbed support (-embed) |
2187 | XEmbed support (-embed) |
2100 | user-pty (-pty-fd) |
2188 | user-pty (-pty-fd) |
2101 | hold on exit (-hold) |
2189 | hold on exit (-hold) |
2102 | skip builtin block graphics (-sbg) |
2190 | skip builtin block graphics (-sbg) |
|
|
2191 | |
|
|
2192 | It also enabled some non-essential features otherwise disabled, such as: |
|
|
2193 | |
|
|
2194 | some round-trip time optimisations |
|
|
2195 | nearest color allocation on pseudocolor screens |
|
|
2196 | UTF8_STRING supporr for selection |
2103 | sgr modes 90..97 and 100..107 |
2197 | sgr modes 90..97 and 100..107 |
|
|
2198 | backindex and forwardindex escape sequences |
|
|
2199 | view change/zero scorllback esacpe sequences |
|
|
2200 | locale switching escape sequence |
|
|
2201 | window op and some xterm/OSC escape sequences |
|
|
2202 | rectangular selections |
|
|
2203 | trailing space removal for selections |
|
|
2204 | verbose X error handling |
2104 | |
2205 | |
2105 | =item --enable-iso14755 (default: on) |
2206 | =item --enable-iso14755 (default: on) |
2106 | |
2207 | |
2107 | Enable extended ISO 14755 support (see @@RXVT_NAME@@(1), or |
2208 | Enable extended ISO 14755 support (see @@RXVT_NAME@@(1), or |
2108 | F<doc/rxvt.1.txt>). Basic support (section 5.1) is enabled by |
2209 | F<doc/rxvt.1.txt>). Basic support (section 5.1) is enabled by |
… | |
… | |
2151 | |
2252 | |
2152 | =item --enable-pointer-blank (default: on) |
2253 | =item --enable-pointer-blank (default: on) |
2153 | |
2254 | |
2154 | Add support to have the pointer disappear when typing or inactive. |
2255 | Add support to have the pointer disappear when typing or inactive. |
2155 | |
2256 | |
2156 | =item --enable-perl (default: off) |
2257 | =item --enable-perl (default: on) |
2157 | |
2258 | |
2158 | Enable an embedded perl interpreter. See the B<@@RXVT_NAME@@perl(3)> |
2259 | Enable an embedded perl interpreter. See the B<@@RXVT_NAME@@perl(3)> |
2159 | manpage (F<doc/rxvtperl.txt>) for more info on this feature, or the files |
2260 | manpage (F<doc/rxvtperl.txt>) for more info on this feature, or the files |
2160 | in F<src/perl-ext/> for the extensions that are installed by default. The |
2261 | in F<src/perl-ext/> for the extensions that are installed by default. The |
2161 | perl interpreter that is used can be specified via the C<PERL> environment |
2262 | perl interpreter that is used can be specified via the C<PERL> environment |