… | |
… | |
72 | |
72 | |
73 | =head3 How can I start @@URXVT_NAME@@d in a race-free way? |
73 | =head3 How can I start @@URXVT_NAME@@d in a race-free way? |
74 | |
74 | |
75 | Try C<@@URXVT_NAME@@d -f -o>, which tells @@URXVT_NAME@@d to open the |
75 | Try C<@@URXVT_NAME@@d -f -o>, which tells @@URXVT_NAME@@d to open the |
76 | display, create the listening socket and then fork. |
76 | display, create the listening socket and then fork. |
|
|
77 | |
|
|
78 | =head3 How can I start @@URXVT_NAME@@d automatically when I run URXVT_NAME@@c? |
|
|
79 | |
|
|
80 | If you want to start @@URXVT_NAME@@d automatically whenever you run |
|
|
81 | @@URXVT_NAME@@c and the daemon isn't running yet, use this script: |
|
|
82 | |
|
|
83 | #!/bin/sh |
|
|
84 | @@URXVT_NAME@@c "$@" |
|
|
85 | if [ $? -eq 2 ]; then |
|
|
86 | @@URXVT_NAME@@d -q -o -f |
|
|
87 | @@URXVT_NAME@@c "$@" |
|
|
88 | fi |
|
|
89 | |
|
|
90 | This tries to create a new terminal, and if fails with exit status 2, |
|
|
91 | meaning it couldn't connect to the daemon, it will start the daemon and |
|
|
92 | re-run the command. Subsequent invocations of the script will re-use the |
|
|
93 | existing daemon. |
77 | |
94 | |
78 | =head3 How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc. |
95 | =head3 How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc. |
79 | |
96 | |
80 | The original rxvt and rxvt-unicode always export the variable "COLORTERM", |
97 | The original rxvt and rxvt-unicode always export the variable "COLORTERM", |
81 | so you can check and see if that is set. Note that several programs, JED, |
98 | so you can check and see if that is set. Note that several programs, JED, |
… | |
… | |
866 | |
883 | |
867 | You can also use xterm's C<luit> program, which usually works fine, except |
884 | You can also use xterm's C<luit> program, which usually works fine, except |
868 | for some locales where character width differs between program- and |
885 | for some locales where character width differs between program- and |
869 | rxvt-unicode-locales. |
886 | rxvt-unicode-locales. |
870 | |
887 | |
|
|
888 | =head3 I have problems getting my input method working. |
|
|
889 | |
|
|
890 | Try a search engine, as this is slightly different for every input method server. |
|
|
891 | |
|
|
892 | Here is a checklist: |
|
|
893 | |
|
|
894 | =over 4 |
|
|
895 | |
|
|
896 | =item - Make sure your locale I<and> the imLocale are supported on your OS. |
|
|
897 | |
|
|
898 | Try C<locale -a> or check the documentation for your OS. |
|
|
899 | |
|
|
900 | =item - Make sure your locale or imLocale matches a locale supported by your XIM. |
|
|
901 | |
|
|
902 | For example, B<kinput2> does not support UTF-8 locales, you should use |
|
|
903 | C<ja_JP.EUC-JP> or equivalent. |
|
|
904 | |
|
|
905 | =item - Make sure your XIM server is actually running. |
|
|
906 | |
|
|
907 | =item - Make sure the C<XMODIFIERS> environment variable is set correctly when I<starting> rxvt-unicode. |
|
|
908 | |
|
|
909 | When you want to use e.g. B<kinput2>, it must be set to |
|
|
910 | C<@im=kinput2>. For B<scim>, use C<@im=SCIM>. Youc an see what input |
|
|
911 | method servers are running with this command: |
|
|
912 | |
|
|
913 | xprop -root XIM_SERVERS |
|
|
914 | |
|
|
915 | =item |
|
|
916 | |
|
|
917 | =back |
|
|
918 | |
871 | =head3 My input method wants <some encoding> but I want UTF-8, what can I do? |
919 | =head3 My input method wants <some encoding> but I want UTF-8, what can I do? |
872 | |
920 | |
873 | You can specify separate locales for the input method and the rest of the |
921 | You can specify separate locales for the input method and the rest of the |
874 | terminal, using the resource C<imlocale>: |
922 | terminal, using the resource C<imlocale>: |
875 | |
923 | |
876 | URxvt.imlocale: ja_JP.EUC-JP |
924 | URxvt.imlocale: ja_JP.EUC-JP |
877 | |
925 | |
878 | Now you can start your terminal with C<LC_CTYPE=ja_JP.UTF-8> and still |
926 | Now you can start your terminal with C<LC_CTYPE=ja_JP.UTF-8> and still |
879 | use your input method. Please note, however, that you will not be able to |
927 | use your input method. Please note, however, that, depending on your Xlib |
880 | input characters outside C<EUC-JP> in a normal way then, as your input |
928 | version, you may not be able to input characters outside C<EUC-JP> in a |
881 | method limits you. |
929 | normal way then, as your input method limits you. |
882 | |
930 | |
883 | =head3 Rxvt-unicode crashes when the X Input Method changes or exits. |
931 | =head3 Rxvt-unicode crashes when the X Input Method changes or exits. |
884 | |
932 | |
885 | Unfortunately, this is unavoidable, as the XIM protocol is racy by |
933 | Unfortunately, this is unavoidable, as the XIM protocol is racy by |
886 | design. Applications can avoid some crashes at the expense of memory |
934 | design. Applications can avoid some crashes at the expense of memory |
… | |
… | |
2245 | Remove support for mouse selection style like that of xterm. |
2293 | Remove support for mouse selection style like that of xterm. |
2246 | |
2294 | |
2247 | =item --enable-dmalloc (default: off) |
2295 | =item --enable-dmalloc (default: off) |
2248 | |
2296 | |
2249 | Use Gray Watson's malloc - which is good for debugging See |
2297 | Use Gray Watson's malloc - which is good for debugging See |
2250 | http://www.letters.com/dmalloc/ for details If you use either this or the |
2298 | L<http://www.letters.com/dmalloc/> for details If you use either this or the |
2251 | next option, you may need to edit src/Makefile after compiling to point |
2299 | next option, you may need to edit src/Makefile after compiling to point |
2252 | DINCLUDE and DLIB to the right places. |
2300 | DINCLUDE and DLIB to the right places. |
2253 | |
2301 | |
2254 | You can only use either this option and the following (should |
2302 | You can only use either this option and the following (should |
2255 | you use either) . |
2303 | you use either) . |