| … | |
… | |
| 42 | |
42 | |
| 43 | How can I start urxvtd in a race-free way? |
43 | How can I start urxvtd in a race-free way? |
| 44 | Try "urxvtd -f -o", which tells urxvtd to open the display, create the |
44 | Try "urxvtd -f -o", which tells urxvtd to open the display, create the |
| 45 | listening socket and then fork. |
45 | listening socket and then fork. |
| 46 | |
46 | |
| 47 | How can I start urxvtd automatically when I run URXVT_NAME@@c? |
47 | How can I start urxvtd automatically when I run urxvtc? |
| 48 | If you want to start urxvtd automatically whenever you run urxvtc and |
48 | If you want to start urxvtd automatically whenever you run urxvtc and |
| 49 | the daemon isn't running yet, use this script: |
49 | the daemon isn't running yet, use this script: |
| 50 | |
50 | |
| 51 | #!/bin/sh |
51 | #!/bin/sh |
| 52 | urxvtc "$@" |
52 | urxvtc "$@" |
| … | |
… | |
| 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 |
