… | |
… | |
90 | fi |
90 | fi |
91 | fi |
91 | fi |
92 | |
92 | |
93 | How do I compile the manual pages on my own? |
93 | How do I compile the manual pages on my own? |
94 | You need to have a recent version of perl installed as /usr/bin/perl, |
94 | You need to have a recent version of perl installed as /usr/bin/perl, |
95 | one that comes with pod2man, pod2text and pod2html. Then go to the doc |
95 | one that comes with pod2man, pod2text and pod2xhtml (from Pod::XHTML). |
96 | subdirectory and enter "make alldoc". |
96 | Then go to the doc subdirectory and enter "make alldoc". |
97 | |
97 | |
98 | Isn't rxvt-unicode supposed to be small? Don't all those features bloat? |
98 | Isn't rxvt-unicode supposed to be small? Don't all those features bloat? |
99 | I often get asked about this, and I think, no, they didn't cause extra |
99 | I often get asked about this, and I think, no, they didn't cause extra |
100 | bloat. If you compare a minimal rxvt and a minimal urxvt, you can see |
100 | bloat. If you compare a minimal rxvt and a minimal urxvt, you can see |
101 | that the urxvt binary is larger (due to some encoding tables always |
101 | that the urxvt binary is larger (due to some encoding tables always |
… | |
… | |
501 | Assuming that the physical Backspace key corresponds to the Backspace |
501 | Assuming that the physical Backspace key corresponds to the Backspace |
502 | keysym (not likely for Linux ... see the following question) there are |
502 | keysym (not likely for Linux ... see the following question) there are |
503 | two standard values that can be used for Backspace: "^H" and "^?". |
503 | two standard values that can be used for Backspace: "^H" and "^?". |
504 | |
504 | |
505 | Historically, either value is correct, but rxvt-unicode adopts the |
505 | Historically, either value is correct, but rxvt-unicode adopts the |
506 | debian policy of using "^?" when unsure, because it's the one only only |
506 | debian policy of using "^?" when unsure, because it's the one and only |
507 | correct choice :). |
507 | correct choice :). |
508 | |
508 | |
509 | Rxvt-unicode tries to inherit the current stty settings and uses the |
509 | Rxvt-unicode tries to inherit the current stty settings and uses the |
510 | value of `erase' to guess the value for backspace. If rxvt-unicode |
510 | value of `erase' to guess the value for backspace. If rxvt-unicode |
511 | wasn't started from a terminal (say, from a menu or by remote shell), |
511 | wasn't started from a terminal (say, from a menu or by remote shell), |
… | |
… | |
880 | If you encounter strange problems like typing an accented character but |
880 | If you encounter strange problems like typing an accented character but |
881 | getting two unrelated other characters or similar, or if program output |
881 | getting two unrelated other characters or similar, or if program output |
882 | is subtly garbled, then you should check your locale settings. |
882 | is subtly garbled, then you should check your locale settings. |
883 | |
883 | |
884 | Rxvt-unicode must be started with the same "LC_CTYPE" setting as the |
884 | Rxvt-unicode must be started with the same "LC_CTYPE" setting as the |
885 | programs. Often rxvt-unicode is started in the "C" locale, while the |
885 | programs running in it. Often rxvt-unicode is started in the "C" locale, |
886 | login script running within the rxvt-unicode window changes the locale |
886 | while the login script running within the rxvt-unicode window changes |
887 | to something else, e.g. "en_GB.UTF-8". Needless to say, this is not |
887 | the locale to something else, e.g. "en_GB.UTF-8". Needless to say, this |
888 | going to work. |
888 | is not going to work, and is the most common cause for problems. |
889 | |
889 | |
890 | The best thing is to fix your startup environment, as you will likely |
890 | The best thing is to fix your startup environment, as you will likely |
891 | run into other problems. If nothing works you can try this in your |
891 | run into other problems. If nothing works you can try this in your |
892 | .profile. |
892 | .profile. |
893 | |
893 | |
894 | printf '\33]701;%s\007' "$LC_CTYPE" |
894 | printf '\33]701;%s\007' "$LC_CTYPE" # $LANG or $LC_ALL are worth a try, too |
895 | |
895 | |
896 | If this doesn't work, then maybe you use a "LC_CTYPE" specification not |
896 | If this doesn't work, then maybe you use a "LC_CTYPE" specification not |
897 | supported on your systems. Some systems have a "locale" command which |
897 | supported on your systems. Some systems have a "locale" command which |
898 | displays this (also, "perl -e0" can be used to check locale settings, as |
898 | displays this (also, "perl -e0" can be used to check locale settings, as |
899 | it will complain loudly if it cannot set the locale). If it displays |
899 | it will complain loudly if it cannot set the locale). If it displays |