… | |
… | |
31 | The version number is displayed with the usage (-h). Also the escape |
31 | The version number is displayed with the usage (-h). Also the escape |
32 | sequence C<ESC [ 8 n> sets the window title to the version number. |
32 | sequence C<ESC [ 8 n> sets the window title to the version number. |
33 | |
33 | |
34 | =item I am using Debian GNU/Linux and have a problem... |
34 | =item I am using Debian GNU/Linux and have a problem... |
35 | |
35 | |
36 | The Debian GNU/Linux package of rxvt-unicode contains large patches that |
36 | The Debian GNU/Linux package of rxvt-unicode in sarge contains large |
37 | considerably change the behaviour of rxvt-unicode. Before reporting a |
37 | patches that considerably change the behaviour of rxvt-unicode. Before |
38 | bug to the original rxvt-unicode author please download and install the |
38 | reporting a bug to the original rxvt-unicode author please download and |
39 | genuine version (L<http://software.schmorp.de#rxvt-unicode>) and try to |
39 | install the genuine version (L<http://software.schmorp.de#rxvt-unicode>) |
40 | reproduce the problem. If you cannot, chances are that the problems are |
40 | and try to reproduce the problem. If you cannot, chances are that the |
41 | specific to Debian GNU/Linux, in which case it should be reported via the |
41 | problems are specific to Debian GNU/Linux, in which case it should be |
42 | Debian Bug Tracking System (use C<reportbug> to report the bug). |
42 | reported via the Debian Bug Tracking System (use C<reportbug> to report |
|
|
43 | the bug). |
43 | |
44 | |
44 | For other problems that also affect the Debian package, you can and |
45 | For other problems that also affect the Debian package, you can and |
45 | probably should use the Debian BTS, too, because, after all, it's also a |
46 | probably should use the Debian BTS, too, because, after all, it's also a |
46 | bug in the Debian version and it serves as a reminder for other users that |
47 | bug in the Debian version and it serves as a reminder for other users that |
47 | might encounter the same issue. |
48 | might encounter the same issue. |
… | |
… | |
71 | |
72 | |
72 | URxvt.termName: rxvt |
73 | URxvt.termName: rxvt |
73 | |
74 | |
74 | If you don't plan to use B<rxvt> (quite common...) you could also replace |
75 | If you don't plan to use B<rxvt> (quite common...) you could also replace |
75 | the rxvt terminfo file with the rxvt-unicode one. |
76 | the rxvt terminfo file with the rxvt-unicode one. |
|
|
77 | |
|
|
78 | =item C<tic> outputs some error when compiling the terminfo entry. |
|
|
79 | |
|
|
80 | Most likely it's the empty definition for C<enacs=>. Just replace it by |
|
|
81 | C<enacs=\E[0@> and try again. |
76 | |
82 | |
77 | =item C<bash>'s readline does not work correctly under @@RXVT_NAME@@. |
83 | =item C<bash>'s readline does not work correctly under @@RXVT_NAME@@. |
78 | |
84 | |
79 | =item I need a termcap file entry. |
85 | =item I need a termcap file entry. |
80 | |
86 | |
… | |
… | |
481 | |
487 | |
482 | =item Can I speed up Xft rendering somehow? |
488 | =item Can I speed up Xft rendering somehow? |
483 | |
489 | |
484 | Yes, the most obvious way to speed it up is to avoid Xft entirely, as |
490 | Yes, the most obvious way to speed it up is to avoid Xft entirely, as |
485 | it is simply slow. If you still want Xft fonts you might try to disable |
491 | it is simply slow. If you still want Xft fonts you might try to disable |
486 | antialiasing (by appending C<:antialiasing=false>), which saves lots of |
492 | antialiasing (by appending C<:antialias=false>), which saves lots of |
487 | memory and also speeds up rendering considerably. |
493 | memory and also speeds up rendering considerably. |
488 | |
494 | |
489 | =item Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong? |
495 | =item Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong? |
490 | |
496 | |
491 | Rxvt-unicode will use whatever you specify as a font. If it needs to |
497 | Rxvt-unicode will use whatever you specify as a font. If it needs to |
… | |
… | |
569 | URxvt.color7: #e1dddd |
575 | URxvt.color7: #e1dddd |
570 | URxvt.color15: #e1dddd |
576 | URxvt.color15: #e1dddd |
571 | |
577 | |
572 | =item How can I start @@RXVT_NAME@@d in a race-free way? |
578 | =item How can I start @@RXVT_NAME@@d in a race-free way? |
573 | |
579 | |
574 | Despite it's name, @@RXVT_NAME@@d is not a real daemon, but more like a |
580 | Try C<@@RXVT_NAME@@d -f -o>, which tells @@RXVT_NAME@@d to open the |
575 | server that answers @@RXVT_NAME@@c's requests, so it doesn't background |
581 | display, create the listening socket and then fork. |
576 | itself. |
|
|
577 | |
|
|
578 | To ensure @@RXVT_NAME@@d is listening on it's socket, you can use the |
|
|
579 | following method to wait for the startup message before continuing: |
|
|
580 | |
|
|
581 | { @@RXVT_NAME@@d & } | read |
|
|
582 | |
582 | |
583 | =item What's with the strange Backspace/Delete key behaviour? |
583 | =item What's with the strange Backspace/Delete key behaviour? |
584 | |
584 | |
585 | Assuming that the physical Backspace key corresponds to the |
585 | Assuming that the physical Backspace key corresponds to the |
586 | BackSpace keysym (not likely for Linux ... see the following |
586 | BackSpace keysym (not likely for Linux ... see the following |