ViewVC Help
View File | Revision Log | Show Annotations | Download File
/cvs/rxvt-unicode/doc/rxvt.7.pod
(Generate patch)

Comparing rxvt-unicode/doc/rxvt.7.pod (file contents):
Revision 1.110 by root, Tue Jan 31 21:10:44 2006 UTC vs.
Revision 1.113 by root, Thu Feb 2 18:04:45 2006 UTC

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
75Try C<@@URXVT_NAME@@d -f -o>, which tells @@URXVT_NAME@@d to open the 75Try C<@@URXVT_NAME@@d -f -o>, which tells @@URXVT_NAME@@d to open the
76display, create the listening socket and then fork. 76display, 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
80If 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
90This tries to create a new terminal, and if fails with exit status 2,
91meaning it couldn't connect to the daemon, it will start the daemon and
92re-run the command. Subsequent invocations of the script will re-use the
93existing 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
80The original rxvt and rxvt-unicode always export the variable "COLORTERM", 97The original rxvt and rxvt-unicode always export the variable "COLORTERM",
81so you can check and see if that is set. Note that several programs, JED, 98so you can check and see if that is set. Note that several programs, JED,
866 883
867You can also use xterm's C<luit> program, which usually works fine, except 884You can also use xterm's C<luit> program, which usually works fine, except
868for some locales where character width differs between program- and 885for some locales where character width differs between program- and
869rxvt-unicode-locales. 886rxvt-unicode-locales.
870 887
888=head3 I have problems getting my input method working.
889
890Try a search engine, as this is slightly different for every input method server.
891
892Here is a checklist:
893
894=over 4
895
896=item - Make sure your locale I<and> the imLocale are supported on your OS.
897
898Try 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
902For example, B<kinput2> does not support UTF-8 locales, you should use
903C<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
909When you want to use e.g. B<kinput2>, it must be set to
910C<@im=kinput2>. For B<scim>, use C<@im=SCIM>. Youc an see what input
911method 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
873You can specify separate locales for the input method and the rest of the 921You can specify separate locales for the input method and the rest of the
874terminal, using the resource C<imlocale>: 922terminal, using the resource C<imlocale>:
875 923
876 URxvt.imlocale: ja_JP.EUC-JP 924 URxvt.imlocale: ja_JP.EUC-JP
877 925
878Now you can start your terminal with C<LC_CTYPE=ja_JP.UTF-8> and still 926Now you can start your terminal with C<LC_CTYPE=ja_JP.UTF-8> and still
879use your input method. Please note, however, that you will not be able to 927use your input method. Please note, however, that, depending on your Xlib
880input characters outside C<EUC-JP> in a normal way then, as your input 928version, you may not be able to input characters outside C<EUC-JP> in a
881method limits you. 929normal 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
885Unfortunately, this is unavoidable, as the XIM protocol is racy by 933Unfortunately, this is unavoidable, as the XIM protocol is racy by
886design. Applications can avoid some crashes at the expense of memory 934design. Applications can avoid some crashes at the expense of memory
2245Remove support for mouse selection style like that of xterm. 2293Remove 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
2249Use Gray Watson's malloc - which is good for debugging See 2297Use Gray Watson's malloc - which is good for debugging See
2250http://www.letters.com/dmalloc/ for details If you use either this or the 2298L<http://www.letters.com/dmalloc/> for details If you use either this or the
2251next option, you may need to edit src/Makefile after compiling to point 2299next option, you may need to edit src/Makefile after compiling to point
2252DINCLUDE and DLIB to the right places. 2300DINCLUDE and DLIB to the right places.
2253 2301
2254You can only use either this option and the following (should 2302You can only use either this option and the following (should
2255you use either) . 2303you use either) .

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines