… | |
… | |
17 | |
17 | |
18 | This document contains the FAQ, the RXVT TECHNICAL REFERENCE documenting |
18 | This document contains the FAQ, the RXVT TECHNICAL REFERENCE documenting |
19 | all escape sequences, and other background information. |
19 | all escape sequences, and other background information. |
20 | |
20 | |
21 | The newest version of this document is also available on the World Wide Web at |
21 | The newest version of this document is also available on the World Wide Web at |
22 | L<http://cvs.schmorp.de/browse/*checkout*/rxvt-unicode/doc/rxvt.7.html>. |
22 | L<http://cvs.schmorp.de/browse/rxvt-unicode/doc/rxvt.7.html>. |
23 | |
23 | |
24 | =head1 RXVT-UNICODE/URXVT FREQUENTLY ASKED QUESTIONS |
24 | =head1 RXVT-UNICODE/URXVT FREQUENTLY ASKED QUESTIONS |
25 | |
25 | |
26 | |
26 | |
27 | =head2 Meta, Features & Commandline Issues |
27 | =head2 Meta, Features & Commandline Issues |
… | |
… | |
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 | |
77 | |
78 | =head3 How can I start @@URXVT_NAME@@d automatically when I run URXVT_NAME@@c? |
78 | =head3 How can I start @@URXVT_NAME@@d automatically when I run @@URXVT_NAME@@c? |
79 | |
79 | |
80 | If you want to start @@URXVT_NAME@@d automatically whenever you run |
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: |
81 | @@URXVT_NAME@@c and the daemon isn't running yet, use this script: |
82 | |
82 | |
83 | #!/bin/sh |
83 | #!/bin/sh |
… | |
… | |
562 | Backspace keysym (not likely for Linux ... see the following |
562 | Backspace keysym (not likely for Linux ... see the following |
563 | question) there are two standard values that can be used for |
563 | question) there are two standard values that can be used for |
564 | Backspace: C<^H> and C<^?>. |
564 | Backspace: C<^H> and C<^?>. |
565 | |
565 | |
566 | Historically, either value is correct, but rxvt-unicode adopts the debian |
566 | Historically, either value is correct, but rxvt-unicode adopts the debian |
567 | policy of using C<^?> when unsure, because it's the one only only correct |
567 | policy of using C<^?> when unsure, because it's the one and only correct |
568 | choice :). |
568 | choice :). |
569 | |
569 | |
570 | Rxvt-unicode tries to inherit the current stty settings and uses the value |
570 | Rxvt-unicode tries to inherit the current stty settings and uses the value |
571 | of `erase' to guess the value for backspace. If rxvt-unicode wasn't |
571 | of `erase' to guess the value for backspace. If rxvt-unicode wasn't |
572 | started from a terminal (say, from a menu or by remote shell), then the |
572 | started from a terminal (say, from a menu or by remote shell), then the |
… | |
… | |
838 | |
838 | |
839 | The terminal description used by rxvt-unicode is not as widely available |
839 | The terminal description used by rxvt-unicode is not as widely available |
840 | as that for xterm, or even rxvt (for which the same problem often arises). |
840 | as that for xterm, or even rxvt (for which the same problem often arises). |
841 | |
841 | |
842 | The correct solution for this problem is to install the terminfo, this can |
842 | The correct solution for this problem is to install the terminfo, this can |
843 | be done like this (with ncurses' infocmp): |
843 | be done like this (with ncurses' infocmp and works as user and admin): |
844 | |
844 | |
845 | REMOTE=remotesystem.domain |
845 | REMOTE=remotesystem.domain |
846 | infocmp rxvt-unicode | ssh $REMOTE "cat >/tmp/ti && tic /tmp/ti" |
846 | infocmp rxvt-unicode | ssh $REMOTE "mkdir -p .terminfo && cat >/tmp/ti && tic /tmp/ti" |
847 | |
847 | |
848 | ... or by installing rxvt-unicode normally on the remote system, |
848 | ... or by installing rxvt-unicode normally on the remote system, |
|
|
849 | |
|
|
850 | One some systems you might need to set C<$TERMINFO> to the full path of |
|
|
851 | F<$HOME/.terminfo> for this to work. |
849 | |
852 | |
850 | If you cannot or do not want to do this, then you can simply set |
853 | If you cannot or do not want to do this, then you can simply set |
851 | C<TERM=rxvt> or even C<TERM=xterm>, and live with the small number of |
854 | C<TERM=rxvt> or even C<TERM=xterm>, and live with the small number of |
852 | problems arising, which includes wrong keymapping, less and different |
855 | problems arising, which includes wrong keymapping, less and different |
853 | colours and some refresh errors in fullscreen applications. It's a nice |
856 | colours and some refresh errors in fullscreen applications. It's a nice |
… | |
… | |
953 | If you encounter strange problems like typing an accented character but |
956 | If you encounter strange problems like typing an accented character but |
954 | getting two unrelated other characters or similar, or if program output is |
957 | getting two unrelated other characters or similar, or if program output is |
955 | subtly garbled, then you should check your locale settings. |
958 | subtly garbled, then you should check your locale settings. |
956 | |
959 | |
957 | Rxvt-unicode must be started with the same C<LC_CTYPE> setting as the |
960 | Rxvt-unicode must be started with the same C<LC_CTYPE> setting as the |
958 | programs. Often rxvt-unicode is started in the C<C> locale, while the |
961 | programs running in it. Often rxvt-unicode is started in the C<C> locale, |
959 | login script running within the rxvt-unicode window changes the locale to |
962 | while the login script running within the rxvt-unicode window changes the |
960 | something else, e.g. C<en_GB.UTF-8>. Needless to say, this is not going to work. |
963 | locale to something else, e.g. C<en_GB.UTF-8>. Needless to say, this is |
|
|
964 | not going to work, and is the most common cause for problems. |
961 | |
965 | |
962 | The best thing is to fix your startup environment, as you will likely run |
966 | The best thing is to fix your startup environment, as you will likely run |
963 | into other problems. If nothing works you can try this in your .profile. |
967 | into other problems. If nothing works you can try this in your .profile. |
964 | |
968 | |
965 | printf '\33]701;%s\007' "$LC_CTYPE" |
969 | printf '\33]701;%s\007' "$LC_CTYPE" # $LANG or $LC_ALL are worth a try, too |
966 | |
970 | |
967 | If this doesn't work, then maybe you use a C<LC_CTYPE> specification not |
971 | If this doesn't work, then maybe you use a C<LC_CTYPE> specification not |
968 | supported on your systems. Some systems have a C<locale> command which |
972 | supported on your systems. Some systems have a C<locale> command which |
969 | displays this (also, C<perl -e0> can be used to check locale settings, as |
973 | displays this (also, C<perl -e0> can be used to check locale settings, as |
970 | it will complain loudly if it cannot set the locale). If it displays something |
974 | it will complain loudly if it cannot set the locale). If it displays something |
… | |
… | |
2197 | |
2201 | |
2198 | =head1 CONFIGURE OPTIONS |
2202 | =head1 CONFIGURE OPTIONS |
2199 | |
2203 | |
2200 | General hint: if you get compile errors, then likely your configuration |
2204 | General hint: if you get compile errors, then likely your configuration |
2201 | hasn't been tested well. Either try with C<--enable-everything> or use |
2205 | hasn't been tested well. Either try with C<--enable-everything> or use |
2202 | the F<./reconf> script as a base for experiments. F<./reconf> is used by |
2206 | the default configuration (i.e. C<--enable-xxx> or C<--disable-xxx>). Of |
2203 | myself, so it should generally be a working config. Of course, you should |
2207 | course, you should always report when a combination doesn't work, so it |
2204 | always report when a combination doesn't work, so it can be fixed. Marc |
2208 | can be fixed. Marc Lehmann <rxvt@schmorp.de>. |
2205 | Lehmann <rxvt@schmorp.de>. |
|
|
2206 | |
2209 | |
2207 | All |
2210 | All |
2208 | |
2211 | |
2209 | =over 4 |
2212 | =over 4 |
2210 | |
2213 | |
… | |
… | |
2242 | |
2245 | |
2243 | =begin table |
2246 | =begin table |
2244 | |
2247 | |
2245 | all all available codeset groups |
2248 | all all available codeset groups |
2246 | zh common chinese encodings |
2249 | zh common chinese encodings |
2247 | zh_ext rarely used but very big chinese encodigs |
2250 | zh_ext rarely used but very big chinese encodings |
2248 | jp common japanese encodings |
2251 | jp common japanese encodings |
2249 | jp_ext rarely used but big japanese encodings |
2252 | jp_ext rarely used but big japanese encodings |
2250 | kr korean encodings |
2253 | kr korean encodings |
2251 | |
2254 | |
2252 | =end table |
2255 | =end table |
… | |
… | |
2409 | |
2412 | |
2410 | It also enables some non-essential features otherwise disabled, such as: |
2413 | It also enables some non-essential features otherwise disabled, such as: |
2411 | |
2414 | |
2412 | some round-trip time optimisations |
2415 | some round-trip time optimisations |
2413 | nearest color allocation on pseudocolor screens |
2416 | nearest color allocation on pseudocolor screens |
2414 | UTF8_STRING supporr for selection |
2417 | UTF8_STRING support for selection |
2415 | sgr modes 90..97 and 100..107 |
2418 | sgr modes 90..97 and 100..107 |
2416 | backindex and forwardindex escape sequences |
2419 | backindex and forwardindex escape sequences |
2417 | view change/zero scorllback esacpe sequences |
2420 | view change/zero scrollback escape sequences |
2418 | locale switching escape sequence |
2421 | locale switching escape sequence |
2419 | window op and some xterm/OSC escape sequences |
2422 | window op and some xterm/OSC escape sequences |
2420 | rectangular selections |
2423 | rectangular selections |
2421 | trailing space removal for selections |
2424 | trailing space removal for selections |
2422 | verbose X error handling |
2425 | verbose X error handling |