… | |
… | |
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 |
… | |
… | |
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 |