… | |
… | |
21 | The newest version of this document is also available on the World Wide Web at |
21 | The newest version of this document is also available on the World Wide Web at |
22 | 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>. |
23 | |
23 | |
24 | =head1 FREQUENTLY ASKED QUESTIONS |
24 | =head1 FREQUENTLY ASKED QUESTIONS |
25 | |
25 | |
26 | =over 4 |
|
|
27 | |
|
|
28 | =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 |
29 | single words? |
27 | single words? |
30 | |
28 | |
31 | Yes. For example, if you want to select alphanumeric words, you can use |
29 | If you want to select e.g. alphanumeric words, you can use the following |
32 | the following resource: |
30 | setting: |
33 | |
31 | |
34 | URxvt.selection.pattern-0: ([[:word:]]+) |
32 | URxvt.selection.pattern-0: ([[:word:]]+) |
35 | |
33 | |
36 | If you click more than twice, the selection will be extended |
34 | If you click more than twice, the selection will be extended |
37 | more and more. |
35 | more and more. |
… | |
… | |
41 | URxvt.selection.pattern-0: ([^"&'()*,;<=>?@[\\\\]^`{|})]+) |
39 | URxvt.selection.pattern-0: ([^"&'()*,;<=>?@[\\\\]^`{|})]+) |
42 | |
40 | |
43 | Please also note that the I<LeftClick Shift-LeftClik> combination also |
41 | Please also note that the I<LeftClick Shift-LeftClik> combination also |
44 | selects words like the old code. |
42 | selects words like the old code. |
45 | |
43 | |
46 | =item I don't like the new selection/popups/hotkeys/perl, how do I |
44 | =head2 I don't like the new selection/popups/hotkeys/perl, how do I |
47 | change/disable it? |
45 | change/disable it? |
48 | |
46 | |
49 | You can disable the perl extension completely by setting the |
47 | You can disable the perl extension completely by setting the |
50 | B<perl-ext-common> resource to the empty string, which also keeps |
48 | B<perl-ext-common> resource to the empty string, which also keeps |
51 | rxvt-unicode from initialising perl, saving memory. |
49 | rxvt-unicode from initialising perl, saving memory. |
… | |
… | |
63 | scrollback search mode is triggered by B<M-s>. You can move it to any |
61 | scrollback search mode is triggered by B<M-s>. You can move it to any |
64 | other combination either by setting the B<searchable-scrollback> resource: |
62 | other combination either by setting the B<searchable-scrollback> resource: |
65 | |
63 | |
66 | URxvt.searchable-scrollback: CM-s |
64 | URxvt.searchable-scrollback: CM-s |
67 | |
65 | |
|
|
66 | =head2 The cursor moves when selecting text in the current input line, how |
|
|
67 | do I switch this off? |
|
|
68 | |
|
|
69 | =head2 During rlogin/ssh/telnet/etc. sessions, clicking near the cursor |
|
|
70 | outputs strange escape sequences, how do I fix this? |
|
|
71 | |
|
|
72 | These are caused by the C<readline> perl extension. Under normal |
|
|
73 | circumstances, it will move your cursor around when you click into the |
|
|
74 | line that contains it. It tries hard not to do this at the wrong moment, |
|
|
75 | but when running a program that doesn't parse cursor movements or in some |
|
|
76 | cases during rlogin sessions, it fails to detect this properly. |
|
|
77 | |
|
|
78 | You can permamently switch this feature off by disabling the C<readline> |
|
|
79 | extension: |
|
|
80 | |
|
|
81 | URxvt.perl-ext-common: default,-readline |
|
|
82 | |
68 | =item Why doesn't rxvt-unicode read my resources? |
83 | =head2 Why doesn't rxvt-unicode read my resources? |
69 | |
84 | |
70 | Well, why, indeed? It does, in a way very similar to other X |
85 | Well, why, indeed? It does, in a way very similar to other X |
71 | applications. Most importantly, this means that if you or your OS loads |
86 | applications. Most importantly, this means that if you or your OS loads |
72 | resources into the X display (the right way to do it), rxvt-unicode will |
87 | resources into the X display (the right way to do it), rxvt-unicode will |
73 | ignore any resource files in your home directory. It will only read |
88 | ignore any resource files in your home directory. It will only read |
… | |
… | |
83 | |
98 | |
84 | If you want to use another form (there are lots of different ways of |
99 | If you want to use another form (there are lots of different ways of |
85 | specifying resources), make sure you understand wether and why it |
100 | specifying resources), make sure you understand wether and why it |
86 | works. If unsure, use the form above. |
101 | works. If unsure, use the form above. |
87 | |
102 | |
88 | =item I can't get transparency working, what am I doing wrong? |
103 | =head2 I can't get transparency working, what am I doing wrong? |
89 | |
104 | |
90 | First of all, transparency isn't officially supported in rxvt-unicode, so |
105 | First of all, transparency isn't officially supported in rxvt-unicode, so |
91 | you are mostly on your own. Do not bug the author about it (but you may |
106 | you are mostly on your own. Do not bug the author about it (but you may |
92 | bug everybody else). Also, if you can't get it working consider it a rite |
107 | bug everybody else). Also, if you can't get it working consider it a rite |
93 | of passage: ... and you failed. |
108 | of passage: ... and you failed. |
… | |
… | |
130 | |
145 | |
131 | Then click on a window you want to make transparent. Replace C<0xc0000000> |
146 | Then click on a window you want to make transparent. Replace C<0xc0000000> |
132 | by other values to change the degree of opacity. If it doesn't work and |
147 | by other values to change the degree of opacity. If it doesn't work and |
133 | your server crashes, you got to keep the pieces. |
148 | your server crashes, you got to keep the pieces. |
134 | |
149 | |
135 | =item Isn't rxvt supposed to be small? Don't all those features bloat? |
150 | =head2 Isn't rxvt supposed to be small? Don't all those features bloat? |
136 | |
151 | |
137 | I often get asked about this, and I think, no, they didn't cause extra |
152 | I often get asked about this, and I think, no, they didn't cause extra |
138 | bloat. If you compare a minimal rxvt and a minimal urxvt, you can see |
153 | bloat. If you compare a minimal rxvt and a minimal urxvt, you can see |
139 | that the urxvt binary is larger (due to some encoding tables always being |
154 | that the urxvt binary is larger (due to some encoding tables always being |
140 | compiled in), but it actually uses less memory (RSS) after startup. Even |
155 | compiled in), but it actually uses less memory (RSS) after startup. Even |
… | |
… | |
172 | (21152k + extra 4204k in separate processes) or konsole (22200k + extra |
187 | (21152k + extra 4204k in separate processes) or konsole (22200k + extra |
173 | 43180k in daemons that stay around after exit, plus half a minute of |
188 | 43180k in daemons that stay around after exit, plus half a minute of |
174 | startup time, including the hundreds of warnings it spits out), it fares |
189 | startup time, including the hundreds of warnings it spits out), it fares |
175 | extremely well *g*. |
190 | extremely well *g*. |
176 | |
191 | |
177 | =item Why C++, isn't that unportable/bloated/uncool? |
192 | =head2 Why C++, isn't that unportable/bloated/uncool? |
178 | |
193 | |
179 | Is this a question? :) It comes up very often. The simple answer is: I had |
194 | Is this a question? :) It comes up very often. The simple answer is: I had |
180 | to write it, and C++ allowed me to write and maintain it in a fraction |
195 | to write it, and C++ allowed me to write and maintain it in a fraction |
181 | of the time and effort (which is a scarce resource for me). Put even |
196 | of the time and effort (which is a scarce resource for me). Put even |
182 | shorter: It simply wouldn't exist without C++. |
197 | shorter: It simply wouldn't exist without C++. |
… | |
… | |
206 | /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000) |
221 | /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000) |
207 | |
222 | |
208 | No large bloated libraries (of course, none were linked in statically), |
223 | No large bloated libraries (of course, none were linked in statically), |
209 | except maybe libX11 :) |
224 | except maybe libX11 :) |
210 | |
225 | |
211 | =item Does it support tabs, can I have a tabbed rxvt-unicode? |
226 | =head2 Does it support tabs, can I have a tabbed rxvt-unicode? |
212 | |
227 | |
213 | Beginning with version 7.3, there is a perl extension that implements a |
228 | Beginning with version 7.3, there is a perl extension that implements a |
214 | simple tabbed terminal. It is installed by default, so any of these should |
229 | simple tabbed terminal. It is installed by default, so any of these should |
215 | give you tabs: |
230 | give you tabs: |
216 | |
231 | |
… | |
… | |
222 | or similar tabbing programs, and its embedding-features allow it to be |
237 | or similar tabbing programs, and its embedding-features allow it to be |
223 | embedded into other programs, as witnessed by F<doc/rxvt-tabbed> or |
238 | embedded into other programs, as witnessed by F<doc/rxvt-tabbed> or |
224 | the upcoming C<Gtk2::URxvt> perl module, which features a tabbed urxvt |
239 | the upcoming C<Gtk2::URxvt> perl module, which features a tabbed urxvt |
225 | (murxvt) terminal as an example embedding application. |
240 | (murxvt) terminal as an example embedding application. |
226 | |
241 | |
227 | =item How do I know which rxvt-unicode version I'm using? |
242 | =head2 How do I know which rxvt-unicode version I'm using? |
228 | |
243 | |
229 | The version number is displayed with the usage (-h). Also the escape |
244 | The version number is displayed with the usage (-h). Also the escape |
230 | sequence C<ESC [ 8 n> sets the window title to the version number. When |
245 | sequence C<ESC [ 8 n> sets the window title to the version number. When |
231 | using the @@RXVT_NAME@@c client, the version displayed is that of the |
246 | using the @@RXVT_NAME@@c client, the version displayed is that of the |
232 | daemon. |
247 | daemon. |
233 | |
248 | |
234 | =item I am using Debian GNU/Linux and have a problem... |
249 | =head2 I am using Debian GNU/Linux and have a problem... |
235 | |
250 | |
236 | The Debian GNU/Linux package of rxvt-unicode in sarge contains large |
251 | The Debian GNU/Linux package of rxvt-unicode in sarge contains large |
237 | patches that considerably change the behaviour of rxvt-unicode (but |
252 | patches that considerably change the behaviour of rxvt-unicode (but |
238 | unfortunately this notice has been removed). Before reporting a bug to |
253 | unfortunately this notice has been removed). Before reporting a bug to |
239 | the original rxvt-unicode author please download and install the genuine |
254 | the original rxvt-unicode author please download and install the genuine |
… | |
… | |
245 | For other problems that also affect the Debian package, you can and |
260 | For other problems that also affect the Debian package, you can and |
246 | probably should use the Debian BTS, too, because, after all, it's also a |
261 | probably should use the Debian BTS, too, because, after all, it's also a |
247 | bug in the Debian version and it serves as a reminder for other users that |
262 | bug in the Debian version and it serves as a reminder for other users that |
248 | might encounter the same issue. |
263 | might encounter the same issue. |
249 | |
264 | |
250 | =item I am maintaining rxvt-unicode for distribution/OS XXX, any |
265 | =head2 I am maintaining rxvt-unicode for distribution/OS XXX, any |
251 | recommendation? |
266 | recommendation? |
252 | |
267 | |
253 | You should build one binary with the default options. F<configure> |
268 | You should build one binary with the default options. F<configure> |
254 | now enables most useful options, and the trend goes to making them |
269 | now enables most useful options, and the trend goes to making them |
255 | runtime-switchable, too, so there is usually no drawback to enbaling them, |
270 | runtime-switchable, too, so there is usually no drawback to enbaling them, |
… | |
… | |
266 | If you can/want build more binaries, I recommend building a minimal |
281 | If you can/want build more binaries, I recommend building a minimal |
267 | one with C<--disable-everything> (very useful) and a maximal one with |
282 | one with C<--disable-everything> (very useful) and a maximal one with |
268 | C<--enable-everything> (less useful, it will be very big due to a lot of |
283 | C<--enable-everything> (less useful, it will be very big due to a lot of |
269 | encodings built-in that increase download times and are rarely used). |
284 | encodings built-in that increase download times and are rarely used). |
270 | |
285 | |
271 | =item I need to make it setuid/setgid to support utmp/ptys on my OS, is this safe? |
286 | =head2 I need to make it setuid/setgid to support utmp/ptys on my OS, is this safe? |
272 | |
287 | |
273 | It should be, starting with release 7.1. You are encouraged to properly |
288 | It should be, starting with release 7.1. You are encouraged to properly |
274 | install urxvt with privileges necessary for your OS now. |
289 | install urxvt with privileges necessary for your OS now. |
275 | |
290 | |
276 | When rxvt-unicode detects that it runs setuid or setgid, it will fork |
291 | When rxvt-unicode detects that it runs setuid or setgid, it will fork |
… | |
… | |
283 | This forking is done as the very first within main(), which is very early |
298 | This forking is done as the very first within main(), which is very early |
284 | and reduces possible bugs to initialisation code run before main(), or |
299 | and reduces possible bugs to initialisation code run before main(), or |
285 | things like the dynamic loader of your system, which should result in very |
300 | things like the dynamic loader of your system, which should result in very |
286 | little risk. |
301 | little risk. |
287 | |
302 | |
288 | =item When I log-in to another system it tells me about missing terminfo data? |
303 | =head2 When I log-in to another system it tells me about missing terminfo data? |
289 | |
304 | |
290 | The terminal description used by rxvt-unicode is not as widely available |
305 | The terminal description used by rxvt-unicode is not as widely available |
291 | as that for xterm, or even rxvt (for which the same problem often arises). |
306 | as that for xterm, or even rxvt (for which the same problem often arises). |
292 | |
307 | |
293 | The correct solution for this problem is to install the terminfo, this can |
308 | The correct solution for this problem is to install the terminfo, this can |
… | |
… | |
311 | URxvt.termName: rxvt |
326 | URxvt.termName: rxvt |
312 | |
327 | |
313 | If you don't plan to use B<rxvt> (quite common...) you could also replace |
328 | If you don't plan to use B<rxvt> (quite common...) you could also replace |
314 | the rxvt terminfo file with the rxvt-unicode one. |
329 | the rxvt terminfo file with the rxvt-unicode one. |
315 | |
330 | |
316 | =item C<tic> outputs some error when compiling the terminfo entry. |
331 | =head2 C<tic> outputs some error when compiling the terminfo entry. |
317 | |
332 | |
318 | Most likely it's the empty definition for C<enacs=>. Just replace it by |
333 | Most likely it's the empty definition for C<enacs=>. Just replace it by |
319 | C<enacs=\E[0@> and try again. |
334 | C<enacs=\E[0@> and try again. |
320 | |
335 | |
321 | =item C<bash>'s readline does not work correctly under @@RXVT_NAME@@. |
336 | =head2 C<bash>'s readline does not work correctly under @@RXVT_NAME@@. |
322 | |
337 | |
323 | =item I need a termcap file entry. |
338 | =head2 I need a termcap file entry. |
324 | |
339 | |
325 | One reason you might want this is that some distributions or operating |
340 | One reason you might want this is that some distributions or operating |
326 | systems still compile some programs using the long-obsoleted termcap |
341 | systems still compile some programs using the long-obsoleted termcap |
327 | library (Fedora Core's bash is one example) and rely on a termcap entry |
342 | library (Fedora Core's bash is one example) and rely on a termcap entry |
328 | for C<rxvt-unicode>. |
343 | for C<rxvt-unicode>. |
… | |
… | |
354 | :sc=\E7:se=\E[27m:sf=^J:so=\E[7m:sr=\EM:st=\EH:ta=^I:\ |
369 | :sc=\E7:se=\E[27m:sf=^J:so=\E[7m:sr=\EM:st=\EH:ta=^I:\ |
355 | :te=\E[r\E[?1049l:ti=\E[?1049h:ue=\E[24m:up=\E[A:\ |
370 | :te=\E[r\E[?1049l:ti=\E[?1049h:ue=\E[24m:up=\E[A:\ |
356 | :us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\ |
371 | :us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\ |
357 | :vs=\E[?25h: |
372 | :vs=\E[?25h: |
358 | |
373 | |
359 | =item Why does C<ls> no longer have coloured output? |
374 | =head2 Why does C<ls> no longer have coloured output? |
360 | |
375 | |
361 | The C<ls> in the GNU coreutils unfortunately doesn't use terminfo to |
376 | The C<ls> in the GNU coreutils unfortunately doesn't use terminfo to |
362 | decide wether a terminal has colour, but uses it's own configuration |
377 | decide wether a terminal has colour, but uses it's own configuration |
363 | file. Needless to say, C<rxvt-unicode> is not in it's default file (among |
378 | file. Needless to say, C<rxvt-unicode> is not in it's default file (among |
364 | with most other terminals supporting colour). Either add: |
379 | with most other terminals supporting colour). Either add: |
… | |
… | |
369 | |
384 | |
370 | alias ls='ls --color=auto' |
385 | alias ls='ls --color=auto' |
371 | |
386 | |
372 | to your C<.profile> or C<.bashrc>. |
387 | to your C<.profile> or C<.bashrc>. |
373 | |
388 | |
374 | =item Why doesn't vim/emacs etc. use the 88 colour mode? |
389 | =head2 Why doesn't vim/emacs etc. use the 88 colour mode? |
375 | |
390 | |
376 | =item Why doesn't vim/emacs etc. make use of italic? |
391 | =head2 Why doesn't vim/emacs etc. make use of italic? |
377 | |
392 | |
378 | =item Why are the secondary screen-related options not working properly? |
393 | =head2 Why are the secondary screen-related options not working properly? |
379 | |
394 | |
380 | Make sure you are using C<TERM=rxvt-unicode>. Some pre-packaged |
395 | Make sure you are using C<TERM=rxvt-unicode>. Some pre-packaged |
381 | distributions (most notably Debian GNU/Linux) break rxvt-unicode |
396 | distributions (most notably Debian GNU/Linux) break rxvt-unicode |
382 | by setting C<TERM> to C<rxvt>, which doesn't have these extra |
397 | by setting C<TERM> to C<rxvt>, which doesn't have these extra |
383 | features. Unfortunately, some of these (most notably, again, Debian |
398 | features. Unfortunately, some of these (most notably, again, Debian |
384 | GNU/Linux) furthermore fail to even install the C<rxvt-unicode> terminfo |
399 | GNU/Linux) furthermore fail to even install the C<rxvt-unicode> terminfo |
385 | file, so you will need to install it on your own (See the question B<When |
400 | file, so you will need to install it on your own (See the question B<When |
386 | I log-in to another system it tells me about missing terminfo data?> on |
401 | I log-in to another system it tells me about missing terminfo data?> on |
387 | how to do this). |
402 | how to do this). |
388 | |
403 | |
389 | =item My numerical keypad acts weird and generates differing output? |
404 | =head2 My numerical keypad acts weird and generates differing output? |
390 | |
405 | |
391 | Some Debian GNUL/Linux users seem to have this problem, although no |
406 | Some Debian GNUL/Linux users seem to have this problem, although no |
392 | specific details were reported so far. It is possible that this is caused |
407 | specific details were reported so far. It is possible that this is caused |
393 | by the wrong C<TERM> setting, although the details of wether and how |
408 | by the wrong C<TERM> setting, although the details of wether and how |
394 | this can happen are unknown, as C<TERM=rxvt> should offer a compatible |
409 | this can happen are unknown, as C<TERM=rxvt> should offer a compatible |
395 | keymap. See the answer to the previous question, and please report if that |
410 | keymap. See the answer to the previous question, and please report if that |
396 | helped. |
411 | helped. |
397 | |
412 | |
398 | =item Rxvt-unicode does not seem to understand the selected encoding? |
413 | =head2 Rxvt-unicode does not seem to understand the selected encoding? |
399 | |
414 | |
400 | =item Unicode does not seem to work? |
415 | =head2 Unicode does not seem to work? |
401 | |
416 | |
402 | If you encounter strange problems like typing an accented character but |
417 | If you encounter strange problems like typing an accented character but |
403 | getting two unrelated other characters or similar, or if program output is |
418 | getting two unrelated other characters or similar, or if program output is |
404 | subtly garbled, then you should check your locale settings. |
419 | subtly garbled, then you should check your locale settings. |
405 | |
420 | |
… | |
… | |
425 | |
440 | |
426 | If nothing works and you are sure that everything is set correctly then |
441 | If nothing works and you are sure that everything is set correctly then |
427 | you will need to remember a little known fact: Some programs just don't |
442 | you will need to remember a little known fact: Some programs just don't |
428 | support locales :( |
443 | support locales :( |
429 | |
444 | |
430 | =item Why do some characters look so much different than others? |
445 | =head2 Why do some characters look so much different than others? |
431 | |
446 | |
432 | =item How does rxvt-unicode choose fonts? |
447 | =head2 How does rxvt-unicode choose fonts? |
433 | |
448 | |
434 | Most fonts do not contain the full range of Unicode, which is |
449 | Most fonts do not contain the full range of Unicode, which is |
435 | fine. Chances are that the font you (or the admin/package maintainer of |
450 | fine. Chances are that the font you (or the admin/package maintainer of |
436 | your system/os) have specified does not cover all the characters you want |
451 | your system/os) have specified does not cover all the characters you want |
437 | to display. |
452 | to display. |
… | |
… | |
455 | |
470 | |
456 | The only limitation is that none of the fonts may be larger than the base |
471 | The only limitation is that none of the fonts may be larger than the base |
457 | font, as the base font defines the terminal character cell size, which |
472 | font, as the base font defines the terminal character cell size, which |
458 | must be the same due to the way terminals work. |
473 | must be the same due to the way terminals work. |
459 | |
474 | |
460 | =item Why do some chinese characters look so different than others? |
475 | =head2 Why do some chinese characters look so different than others? |
461 | |
476 | |
462 | This is because there is a difference between script and language -- |
477 | This is because there is a difference between script and language -- |
463 | rxvt-unicode does not know which language the text that is output is, |
478 | rxvt-unicode does not know which language the text that is output is, |
464 | as it only knows the unicode character codes. If rxvt-unicode first |
479 | as it only knows the unicode character codes. If rxvt-unicode first |
465 | sees a japanese/chinese character, it might choose a japanese font for |
480 | sees a japanese/chinese character, it might choose a japanese font for |
… | |
… | |
480 | has been designed yet). |
495 | has been designed yet). |
481 | |
496 | |
482 | Until then, you might get away with switching fonts at runtime (see L<Can |
497 | Until then, you might get away with switching fonts at runtime (see L<Can |
483 | I switch the fonts at runtime?> later in this document). |
498 | I switch the fonts at runtime?> later in this document). |
484 | |
499 | |
485 | =item Why does rxvt-unicode sometimes leave pixel droppings? |
500 | =head2 Why does rxvt-unicode sometimes leave pixel droppings? |
486 | |
501 | |
487 | Most fonts were not designed for terminal use, which means that character |
502 | Most fonts were not designed for terminal use, which means that character |
488 | size varies a lot. A font that is otherwise fine for terminal use might |
503 | size varies a lot. A font that is otherwise fine for terminal use might |
489 | contain some characters that are simply too wide. Rxvt-unicode will avoid |
504 | contain some characters that are simply too wide. Rxvt-unicode will avoid |
490 | these characters. For characters that are just "a bit" too wide a special |
505 | these characters. For characters that are just "a bit" too wide a special |
… | |
… | |
502 | might be forced to use a different font. |
517 | might be forced to use a different font. |
503 | |
518 | |
504 | All of this is not a problem when using X11 core fonts, as their bounding |
519 | All of this is not a problem when using X11 core fonts, as their bounding |
505 | box data is correct. |
520 | box data is correct. |
506 | |
521 | |
507 | =item On Solaris 9, many line-drawing characters are too wide. |
522 | =head2 On Solaris 9, many line-drawing characters are too wide. |
508 | |
523 | |
509 | Seems to be a known bug, read |
524 | Seems to be a known bug, read |
510 | L<http://nixdoc.net/files/forum/about34198.html>. Some people use the |
525 | L<http://nixdoc.net/files/forum/about34198.html>. Some people use the |
511 | following ugly workaround to get non-double-wide-characters working: |
526 | following ugly workaround to get non-double-wide-characters working: |
512 | |
527 | |
513 | #define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x) |
528 | #define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x) |
514 | |
529 | |
515 | =item My Compose (Multi_key) key is no longer working. |
530 | =head2 My Compose (Multi_key) key is no longer working. |
516 | |
531 | |
517 | The most common causes for this are that either your locale is not set |
532 | The most common causes for this are that either your locale is not set |
518 | correctly, or you specified a B<preeditStyle> that is not supported by |
533 | correctly, or you specified a B<preeditStyle> that is not supported by |
519 | your input method. For example, if you specified B<OverTheSpot> and |
534 | your input method. For example, if you specified B<OverTheSpot> and |
520 | your input method (e.g. the default input method handling Compose keys) |
535 | your input method (e.g. the default input method handling Compose keys) |
… | |
… | |
522 | rxvt-unicode will continue without an input method. |
537 | rxvt-unicode will continue without an input method. |
523 | |
538 | |
524 | In this case either do not specify a B<preeditStyle> or specify more than |
539 | In this case either do not specify a B<preeditStyle> or specify more than |
525 | one pre-edit style, such as B<OverTheSpot,Root,None>. |
540 | one pre-edit style, such as B<OverTheSpot,Root,None>. |
526 | |
541 | |
527 | =item I cannot type C<Ctrl-Shift-2> to get an ASCII NUL character due to ISO 14755 |
542 | =head2 I cannot type C<Ctrl-Shift-2> to get an ASCII NUL character due to ISO 14755 |
528 | |
543 | |
529 | Either try C<Ctrl-2> alone (it often is mapped to ASCII NUL even on |
544 | Either try C<Ctrl-2> alone (it often is mapped to ASCII NUL even on |
530 | international keyboards) or simply use ISO 14755 support to your |
545 | international keyboards) or simply use ISO 14755 support to your |
531 | advantage, typing <Ctrl-Shift-0> to get a ASCII NUL. This works for other |
546 | advantage, typing <Ctrl-Shift-0> to get a ASCII NUL. This works for other |
532 | codes, too, such as C<Ctrl-Shift-1-d> to type the default telnet escape |
547 | codes, too, such as C<Ctrl-Shift-1-d> to type the default telnet escape |
533 | character and so on. |
548 | character and so on. |
534 | |
549 | |
535 | =item How can I keep rxvt-unicode from using reverse video so much? |
550 | =head2 How can I keep rxvt-unicode from using reverse video so much? |
536 | |
551 | |
537 | First of all, make sure you are running with the right terminal settings |
552 | First of all, make sure you are running with the right terminal settings |
538 | (C<TERM=rxvt-unicode>), which will get rid of most of these effects. Then |
553 | (C<TERM=rxvt-unicode>), which will get rid of most of these effects. Then |
539 | make sure you have specified colours for italic and bold, as otherwise |
554 | make sure you have specified colours for italic and bold, as otherwise |
540 | rxvt-unicode might use reverse video to simulate the effect: |
555 | rxvt-unicode might use reverse video to simulate the effect: |
541 | |
556 | |
542 | URxvt.colorBD: white |
557 | URxvt.colorBD: white |
543 | URxvt.colorIT: green |
558 | URxvt.colorIT: green |
544 | |
559 | |
545 | =item Some programs assume totally weird colours (red instead of blue), how can I fix that? |
560 | =head2 Some programs assume totally weird colours (red instead of blue), how can I fix that? |
546 | |
561 | |
547 | For some unexplainable reason, some rare programs assume a very weird |
562 | For some unexplainable reason, some rare programs assume a very weird |
548 | colour palette when confronted with a terminal with more than the standard |
563 | colour palette when confronted with a terminal with more than the standard |
549 | 8 colours (rxvt-unicode supports 88). The right fix is, of course, to fix |
564 | 8 colours (rxvt-unicode supports 88). The right fix is, of course, to fix |
550 | these programs not to assume non-ISO colours without very good reasons. |
565 | these programs not to assume non-ISO colours without very good reasons. |
551 | |
566 | |
552 | In the meantime, you can either edit your C<rxvt-unicode> terminfo |
567 | In the meantime, you can either edit your C<rxvt-unicode> terminfo |
553 | definition to only claim 8 colour support or use C<TERM=rxvt>, which will |
568 | definition to only claim 8 colour support or use C<TERM=rxvt>, which will |
554 | fix colours but keep you from using other rxvt-unicode features. |
569 | fix colours but keep you from using other rxvt-unicode features. |
555 | |
570 | |
556 | =item I am on FreeBSD and rxvt-unicode does not seem to work at all. |
571 | =head2 I am on FreeBSD and rxvt-unicode does not seem to work at all. |
557 | |
572 | |
558 | Rxvt-unicode requires the symbol C<__STDC_ISO_10646__> to be defined |
573 | Rxvt-unicode requires the symbol C<__STDC_ISO_10646__> to be defined |
559 | in your compile environment, or an implementation that implements it, |
574 | in your compile environment, or an implementation that implements it, |
560 | wether it defines the symbol or not. C<__STDC_ISO_10646__> requires that |
575 | wether it defines the symbol or not. C<__STDC_ISO_10646__> requires that |
561 | B<wchar_t> is represented as unicode. |
576 | B<wchar_t> is represented as unicode. |
… | |
… | |
583 | |
598 | |
584 | The rxvt-unicode author insists that the right way to fix this is in the |
599 | The rxvt-unicode author insists that the right way to fix this is in the |
585 | system libraries once and for all, instead of forcing every app to carry |
600 | system libraries once and for all, instead of forcing every app to carry |
586 | complete replacements for them :) |
601 | complete replacements for them :) |
587 | |
602 | |
588 | =item I use Solaris 9 and it doesn't compile/work/etc. |
603 | =head2 I use Solaris 9 and it doesn't compile/work/etc. |
589 | |
604 | |
590 | Try the diff in F<doc/solaris9.patch> as a base. It fixes the worst |
605 | Try the diff in F<doc/solaris9.patch> as a base. It fixes the worst |
591 | problems with C<wcwidth> and a compile problem. |
606 | problems with C<wcwidth> and a compile problem. |
592 | |
607 | |
593 | =item How can I use rxvt-unicode under cygwin? |
608 | =head2 How can I use rxvt-unicode under cygwin? |
594 | |
609 | |
595 | rxvt-unicode should compile and run out of the box on cygwin, using |
610 | rxvt-unicode should compile and run out of the box on cygwin, using |
596 | the X11 libraries that come with cygwin. libW11 emulation is no |
611 | the X11 libraries that come with cygwin. libW11 emulation is no |
597 | longer supported (and makes no sense, either, as it only supported a |
612 | longer supported (and makes no sense, either, as it only supported a |
598 | single font). I recommend starting the X-server in C<-multiwindow> or |
613 | single font). I recommend starting the X-server in C<-multiwindow> or |
… | |
… | |
601 | |
616 | |
602 | At the time of this writing, cygwin didn't seem to support any multi-byte |
617 | At the time of this writing, cygwin didn't seem to support any multi-byte |
603 | encodings (you might try C<LC_CTYPE=C-UTF-8>), so you are likely limited |
618 | encodings (you might try C<LC_CTYPE=C-UTF-8>), so you are likely limited |
604 | to 8-bit encodings. |
619 | to 8-bit encodings. |
605 | |
620 | |
606 | =item How does rxvt-unicode determine the encoding to use? |
621 | =head2 How does rxvt-unicode determine the encoding to use? |
607 | |
622 | |
608 | =item Is there an option to switch encodings? |
623 | =head2 Is there an option to switch encodings? |
609 | |
624 | |
610 | Unlike some other terminals, rxvt-unicode has no encoding switch, and no |
625 | Unlike some other terminals, rxvt-unicode has no encoding switch, and no |
611 | specific "utf-8" mode, such as xterm. In fact, it doesn't even know about |
626 | specific "utf-8" mode, such as xterm. In fact, it doesn't even know about |
612 | UTF-8 or any other encodings with respect to terminal I/O. |
627 | UTF-8 or any other encodings with respect to terminal I/O. |
613 | |
628 | |
… | |
… | |
638 | rxvt-unicode. |
653 | rxvt-unicode. |
639 | |
654 | |
640 | If you want to use a specific encoding you have to make sure you start |
655 | If you want to use a specific encoding you have to make sure you start |
641 | rxvt-unicode with the correct C<LC_CTYPE> category. |
656 | rxvt-unicode with the correct C<LC_CTYPE> category. |
642 | |
657 | |
643 | =item Can I switch locales at runtime? |
658 | =head2 Can I switch locales at runtime? |
644 | |
659 | |
645 | Yes, using an escape sequence. Try something like this, which sets |
660 | Yes, using an escape sequence. Try something like this, which sets |
646 | rxvt-unicode's idea of C<LC_CTYPE>. |
661 | rxvt-unicode's idea of C<LC_CTYPE>. |
647 | |
662 | |
648 | printf '\e]701;%s\007' ja_JP.SJIS |
663 | printf '\e]701;%s\007' ja_JP.SJIS |
… | |
… | |
660 | |
675 | |
661 | You can also use xterm's C<luit> program, which usually works fine, except |
676 | You can also use xterm's C<luit> program, which usually works fine, except |
662 | for some locales where character width differs between program- and |
677 | for some locales where character width differs between program- and |
663 | rxvt-unicode-locales. |
678 | rxvt-unicode-locales. |
664 | |
679 | |
665 | =item Can I switch the fonts at runtime? |
680 | =head2 Can I switch the fonts at runtime? |
666 | |
681 | |
667 | Yes, using an escape sequence. Try something like this, which has the same |
682 | Yes, using an escape sequence. Try something like this, which has the same |
668 | effect as using the C<-fn> switch, and takes effect immediately: |
683 | effect as using the C<-fn> switch, and takes effect immediately: |
669 | |
684 | |
670 | printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic" |
685 | printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic" |
… | |
… | |
673 | japanese font), but you have to switch to chinese temporarily, where |
688 | japanese font), but you have to switch to chinese temporarily, where |
674 | japanese fonts would only be in your way. |
689 | japanese fonts would only be in your way. |
675 | |
690 | |
676 | You can think of this as a kind of manual ISO-2022 switching. |
691 | You can think of this as a kind of manual ISO-2022 switching. |
677 | |
692 | |
678 | =item Why do italic characters look as if clipped? |
693 | =head2 Why do italic characters look as if clipped? |
679 | |
694 | |
680 | Many fonts have difficulties with italic characters and hinting. For |
695 | Many fonts have difficulties with italic characters and hinting. For |
681 | example, the otherwise very nicely hinted font C<xft:Bitstream Vera Sans |
696 | example, the otherwise very nicely hinted font C<xft:Bitstream Vera Sans |
682 | Mono> completely fails in it's italic face. A workaround might be to |
697 | Mono> completely fails in it's italic face. A workaround might be to |
683 | enable freetype autohinting, i.e. like this: |
698 | enable freetype autohinting, i.e. like this: |
684 | |
699 | |
685 | URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true |
700 | URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true |
686 | URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true |
701 | URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true |
687 | |
702 | |
688 | =item My input method wants <some encoding> but I want UTF-8, what can I do? |
703 | =head2 My input method wants <some encoding> but I want UTF-8, what can I do? |
689 | |
704 | |
690 | You can specify separate locales for the input method and the rest of the |
705 | You can specify separate locales for the input method and the rest of the |
691 | terminal, using the resource C<imlocale>: |
706 | terminal, using the resource C<imlocale>: |
692 | |
707 | |
693 | URxvt.imlocale: ja_JP.EUC-JP |
708 | URxvt.imlocale: ja_JP.EUC-JP |
… | |
… | |
695 | Now you can start your terminal with C<LC_CTYPE=ja_JP.UTF-8> and still |
710 | Now you can start your terminal with C<LC_CTYPE=ja_JP.UTF-8> and still |
696 | use your input method. Please note, however, that you will not be able to |
711 | use your input method. Please note, however, that you will not be able to |
697 | input characters outside C<EUC-JP> in a normal way then, as your input |
712 | input characters outside C<EUC-JP> in a normal way then, as your input |
698 | method limits you. |
713 | method limits you. |
699 | |
714 | |
700 | =item Rxvt-unicode crashes when the X Input Method changes or exits. |
715 | =head2 Rxvt-unicode crashes when the X Input Method changes or exits. |
701 | |
716 | |
702 | Unfortunately, this is unavoidable, as the XIM protocol is racy by |
717 | Unfortunately, this is unavoidable, as the XIM protocol is racy by |
703 | design. Applications can avoid some crashes at the expense of memory |
718 | design. Applications can avoid some crashes at the expense of memory |
704 | leaks, and Input Methods can avoid some crashes by careful ordering at |
719 | leaks, and Input Methods can avoid some crashes by careful ordering at |
705 | exit time. B<kinput2> (and derived input methods) generally succeeds, |
720 | exit time. B<kinput2> (and derived input methods) generally succeeds, |
706 | while B<SCIM> (or similar input methods) fails. In the end, however, |
721 | while B<SCIM> (or similar input methods) fails. In the end, however, |
707 | crashes cannot be completely avoided even if both sides cooperate. |
722 | crashes cannot be completely avoided even if both sides cooperate. |
708 | |
723 | |
709 | So the only workaround is not to kill your Input Method Servers. |
724 | So the only workaround is not to kill your Input Method Servers. |
710 | |
725 | |
711 | =item Rxvt-unicode uses gobs of memory, how can I reduce that? |
726 | =head2 Rxvt-unicode uses gobs of memory, how can I reduce that? |
712 | |
727 | |
713 | Rxvt-unicode tries to obey the rule of not charging you for something you |
728 | Rxvt-unicode tries to obey the rule of not charging you for something you |
714 | don't use. One thing you should try is to configure out all settings that |
729 | don't use. One thing you should try is to configure out all settings that |
715 | you don't need, for example, Xft support is a resource hog by design, |
730 | you don't need, for example, Xft support is a resource hog by design, |
716 | when used. Compiling it out ensures that no Xft font will be loaded |
731 | when used. Compiling it out ensures that no Xft font will be loaded |
… | |
… | |
721 | 6 bytes per screen cell. For a 160x?? window this amounts to almost a |
736 | 6 bytes per screen cell. For a 160x?? window this amounts to almost a |
722 | kilobyte per line. A scrollback buffer of 10000 lines will then (if full) |
737 | kilobyte per line. A scrollback buffer of 10000 lines will then (if full) |
723 | use 10 Megabytes of memory. With C<--enable-unicode3> it gets worse, as |
738 | use 10 Megabytes of memory. With C<--enable-unicode3> it gets worse, as |
724 | rxvt-unicode then uses 8 bytes per screen cell. |
739 | rxvt-unicode then uses 8 bytes per screen cell. |
725 | |
740 | |
726 | =item Can I speed up Xft rendering somehow? |
741 | =head2 Can I speed up Xft rendering somehow? |
727 | |
742 | |
728 | Yes, the most obvious way to speed it up is to avoid Xft entirely, as |
743 | Yes, the most obvious way to speed it up is to avoid Xft entirely, as |
729 | it is simply slow. If you still want Xft fonts you might try to disable |
744 | it is simply slow. If you still want Xft fonts you might try to disable |
730 | antialiasing (by appending C<:antialias=false>), which saves lots of |
745 | antialiasing (by appending C<:antialias=false>), which saves lots of |
731 | memory and also speeds up rendering considerably. |
746 | memory and also speeds up rendering considerably. |
732 | |
747 | |
733 | =item Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong? |
748 | =head2 Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong? |
734 | |
749 | |
735 | Rxvt-unicode will use whatever you specify as a font. If it needs to |
750 | Rxvt-unicode will use whatever you specify as a font. If it needs to |
736 | fall back to it's default font search list it will prefer X11 core |
751 | fall back to it's default font search list it will prefer X11 core |
737 | fonts, because they are small and fast, and then use Xft fonts. It has |
752 | fonts, because they are small and fast, and then use Xft fonts. It has |
738 | antialiasing disabled for most of them, because the author thinks they |
753 | antialiasing disabled for most of them, because the author thinks they |
739 | look best that way. |
754 | look best that way. |
740 | |
755 | |
741 | If you want antialiasing, you have to specify the fonts manually. |
756 | If you want antialiasing, you have to specify the fonts manually. |
742 | |
757 | |
743 | =item Mouse cut/paste suddenly no longer works. |
758 | =head2 Mouse cut/paste suddenly no longer works. |
744 | |
759 | |
745 | Make sure that mouse reporting is actually turned off since killing |
760 | Make sure that mouse reporting is actually turned off since killing |
746 | some editors prematurely may leave the mouse in mouse report mode. I've |
761 | some editors prematurely may leave the mouse in mouse report mode. I've |
747 | heard that tcsh may use mouse reporting unless it otherwise specified. A |
762 | heard that tcsh may use mouse reporting unless it otherwise specified. A |
748 | quick check is to see if cut/paste works when the Alt or Shift keys are |
763 | quick check is to see if cut/paste works when the Alt or Shift keys are |
749 | depressed. |
764 | depressed. |
750 | |
765 | |
751 | =item What's with this bold/blink stuff? |
766 | =head2 What's with this bold/blink stuff? |
752 | |
767 | |
753 | If no bold colour is set via C<colorBD:>, bold will invert text using the |
768 | If no bold colour is set via C<colorBD:>, bold will invert text using the |
754 | standard foreground colour. |
769 | standard foreground colour. |
755 | |
770 | |
756 | For the standard background colour, blinking will actually make the |
771 | For the standard background colour, blinking will actually make the |
… | |
… | |
763 | |
778 | |
764 | color0-7 are the low-intensity colors. |
779 | color0-7 are the low-intensity colors. |
765 | |
780 | |
766 | color8-15 are the corresponding high-intensity colors. |
781 | color8-15 are the corresponding high-intensity colors. |
767 | |
782 | |
768 | =item I don't like the screen colors. How do I change them? |
783 | =head2 I don't like the screen colors. How do I change them? |
769 | |
784 | |
770 | You can change the screen colors at run-time using F<~/.Xdefaults> |
785 | You can change the screen colors at run-time using F<~/.Xdefaults> |
771 | resources (or as long-options). |
786 | resources (or as long-options). |
772 | |
787 | |
773 | Here are values that are supposed to resemble a VGA screen, |
788 | Here are values that are supposed to resemble a VGA screen, |
… | |
… | |
811 | URxvt.color6: #73f7ff |
826 | URxvt.color6: #73f7ff |
812 | URxvt.color14: #73f7ff |
827 | URxvt.color14: #73f7ff |
813 | URxvt.color7: #e1dddd |
828 | URxvt.color7: #e1dddd |
814 | URxvt.color15: #e1dddd |
829 | URxvt.color15: #e1dddd |
815 | |
830 | |
816 | =item How can I start @@RXVT_NAME@@d in a race-free way? |
831 | =head2 How can I start @@RXVT_NAME@@d in a race-free way? |
817 | |
832 | |
818 | Try C<@@RXVT_NAME@@d -f -o>, which tells @@RXVT_NAME@@d to open the |
833 | Try C<@@RXVT_NAME@@d -f -o>, which tells @@RXVT_NAME@@d to open the |
819 | display, create the listening socket and then fork. |
834 | display, create the listening socket and then fork. |
820 | |
835 | |
821 | =item What's with the strange Backspace/Delete key behaviour? |
836 | =head2 What's with the strange Backspace/Delete key behaviour? |
822 | |
837 | |
823 | Assuming that the physical Backspace key corresponds to the |
838 | Assuming that the physical Backspace key corresponds to the |
824 | BackSpace keysym (not likely for Linux ... see the following |
839 | BackSpace keysym (not likely for Linux ... see the following |
825 | question) there are two standard values that can be used for |
840 | question) there are two standard values that can be used for |
826 | Backspace: C<^H> and C<^?>. |
841 | Backspace: C<^H> and C<^?>. |
… | |
… | |
872 | some editors (vim I'm told) expect Backspace = ^H, |
887 | some editors (vim I'm told) expect Backspace = ^H, |
873 | GNU Emacs (and Emacs-like editors) use ^H for help. |
888 | GNU Emacs (and Emacs-like editors) use ^H for help. |
874 | |
889 | |
875 | Perhaps someday this will all be resolved in a consistent manner. |
890 | Perhaps someday this will all be resolved in a consistent manner. |
876 | |
891 | |
877 | =item I don't like the key-bindings. How do I change them? |
892 | =head2 I don't like the key-bindings. How do I change them? |
878 | |
893 | |
879 | There are some compile-time selections available via configure. Unless |
894 | There are some compile-time selections available via configure. Unless |
880 | you have run "configure" with the C<--disable-resources> option you can |
895 | you have run "configure" with the C<--disable-resources> option you can |
881 | use the `keysym' resource to alter the keystrings associated with keysyms. |
896 | use the `keysym' resource to alter the keystrings associated with keysyms. |
882 | |
897 | |
… | |
… | |
903 | URxvt.keysym.M-C-a: list \033<M-C- abcdefghijklmnopqrstuvwxyz > |
918 | URxvt.keysym.M-C-a: list \033<M-C- abcdefghijklmnopqrstuvwxyz > |
904 | URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007 |
919 | URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007 |
905 | |
920 | |
906 | See some more examples in the documentation for the B<keysym> resource. |
921 | See some more examples in the documentation for the B<keysym> resource. |
907 | |
922 | |
908 | =item I'm using keyboard model XXX that has extra Prior/Next/Insert keys. |
923 | =head2 I'm using keyboard model XXX that has extra Prior/Next/Insert keys. |
909 | How do I make use of them? For example, the Sun Keyboard type 4 |
924 | How do I make use of them? For example, the Sun Keyboard type 4 |
910 | has the following mappings that rxvt-unicode doesn't recognize. |
925 | has the following mappings that rxvt-unicode doesn't recognize. |
911 | |
926 | |
912 | KP_Insert == Insert |
927 | KP_Insert == Insert |
913 | F22 == Print |
928 | F22 == Print |
… | |
… | |
918 | |
933 | |
919 | Rather than have rxvt-unicode try to accommodate all the various possible |
934 | Rather than have rxvt-unicode try to accommodate all the various possible |
920 | keyboard mappings, it is better to use `xmodmap' to remap the keys as |
935 | keyboard mappings, it is better to use `xmodmap' to remap the keys as |
921 | required for your particular machine. |
936 | required for your particular machine. |
922 | |
937 | |
923 | =item How do I distinguish wether I'm running rxvt-unicode or a regular xterm? |
938 | =head2 How do I distinguish wether I'm running rxvt-unicode or a regular xterm? |
924 | I need this to decide about setting colors etc. |
939 | I need this to decide about setting colors etc. |
925 | |
940 | |
926 | rxvt and rxvt-unicode always export the variable "COLORTERM", so you can |
941 | rxvt and rxvt-unicode always export the variable "COLORTERM", so you can |
927 | check and see if that is set. Note that several programs, JED, slrn, |
942 | check and see if that is set. Note that several programs, JED, slrn, |
928 | Midnight Commander automatically check this variable to decide whether or |
943 | Midnight Commander automatically check this variable to decide whether or |
929 | not to use color. |
944 | not to use color. |
930 | |
945 | |
931 | =item How do I set the correct, full IP address for the DISPLAY variable? |
946 | =head2 How do I set the correct, full IP address for the DISPLAY variable? |
932 | |
947 | |
933 | If you've compiled rxvt-unicode with DISPLAY_IS_IP and have enabled |
948 | If you've compiled rxvt-unicode with DISPLAY_IS_IP and have enabled |
934 | insecure mode then it is possible to use the following shell script |
949 | insecure mode then it is possible to use the following shell script |
935 | snippets to correctly set the display. If your version of rxvt-unicode |
950 | snippets to correctly set the display. If your version of rxvt-unicode |
936 | wasn't also compiled with ESCZ_ANSWER (as assumed in these snippets) then |
951 | wasn't also compiled with ESCZ_ANSWER (as assumed in these snippets) then |
… | |
… | |
951 | echo -n '^[[7n' # query the rxvt we are in for the DISPLAY string |
966 | echo -n '^[[7n' # query the rxvt we are in for the DISPLAY string |
952 | read DISPLAY # set it in our local shell |
967 | read DISPLAY # set it in our local shell |
953 | fi |
968 | fi |
954 | fi |
969 | fi |
955 | |
970 | |
956 | =item How do I compile the manual pages for myself? |
971 | =head2 How do I compile the manual pages for myself? |
957 | |
972 | |
958 | You need to have a recent version of perl installed as F</usr/bin/perl>, |
973 | You need to have a recent version of perl installed as F</usr/bin/perl>, |
959 | one that comes with F<pod2man>, F<pod2text> and F<pod2html>. Then go to |
974 | one that comes with F<pod2man>, F<pod2text> and F<pod2html>. Then go to |
960 | the doc subdirectory and enter C<make alldoc>. |
975 | the doc subdirectory and enter C<make alldoc>. |
961 | |
976 | |
962 | =item My question isn't answered here, can I ask a human? |
977 | =head2 My question isn't answered here, can I ask a human? |
963 | |
978 | |
964 | Before sending me mail, you could go to IRC: C<irc.freenode.net>, |
979 | Before sending me mail, you could go to IRC: C<irc.freenode.net>, |
965 | channel C<#rxvt-unicode> has some rxvt-unicode enthusiasts that might be |
980 | channel C<#rxvt-unicode> has some rxvt-unicode enthusiasts that might be |
966 | interested in learning about new and exciting problems (but not FAQs :). |
981 | interested in learning about new and exciting problems (but not FAQs :). |
967 | |
|
|
968 | =back |
|
|
969 | |
982 | |
970 | =head1 RXVT TECHNICAL REFERENCE |
983 | =head1 RXVT TECHNICAL REFERENCE |
971 | |
984 | |
972 | =head1 DESCRIPTION |
985 | =head1 DESCRIPTION |
973 | |
986 | |