… | |
… | |
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 do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc. |
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. |
79 | |
79 | |
80 | rxvt and rxvt-unicode always export the variable "COLORTERM", so you can |
80 | The original rxvt and rxvt-unicode always export the variable "COLORTERM", |
81 | check and see if that is set. Note that several programs, JED, slrn, |
81 | so you can check and see if that is set. Note that several programs, JED, |
82 | Midnight Commander automatically check this variable to decide whether or |
82 | slrn, Midnight Commander automatically check this variable to decide |
83 | not to use color. |
83 | whether or not to use color. |
84 | |
84 | |
85 | =head3 How do I set the correct, full IP address for the DISPLAY variable? |
85 | =head3 How do I set the correct, full IP address for the DISPLAY variable? |
86 | |
86 | |
87 | If you've compiled rxvt-unicode with DISPLAY_IS_IP and have enabled |
87 | If you've compiled rxvt-unicode with DISPLAY_IS_IP and have enabled |
88 | insecure mode then it is possible to use the following shell script |
88 | insecure mode then it is possible to use the following shell script |
… | |
… | |
687 | resource to set it: |
687 | resource to set it: |
688 | |
688 | |
689 | URxvt.termName: rxvt |
689 | URxvt.termName: rxvt |
690 | |
690 | |
691 | If you don't plan to use B<rxvt> (quite common...) you could also replace |
691 | If you don't plan to use B<rxvt> (quite common...) you could also replace |
692 | the rxvt terminfo file with the rxvt-unicode one. |
692 | the rxvt terminfo file with the rxvt-unicode one and use C<TERM=rxvt>. |
693 | |
693 | |
694 | =head3 C<tic> outputs some error when compiling the terminfo entry. |
694 | =head3 C<tic> outputs some error when compiling the terminfo entry. |
695 | |
695 | |
696 | Most likely it's the empty definition for C<enacs=>. Just replace it by |
696 | Most likely it's the empty definition for C<enacs=>. Just replace it by |
697 | C<enacs=\E[0@> and try again. |
697 | C<enacs=\E[0@> and try again. |
… | |
… | |
1003 | |
1003 | |
1004 | At the time of this writing, cygwin didn't seem to support any multi-byte |
1004 | At the time of this writing, cygwin didn't seem to support any multi-byte |
1005 | encodings (you might try C<LC_CTYPE=C-UTF-8>), so you are likely limited |
1005 | encodings (you might try C<LC_CTYPE=C-UTF-8>), so you are likely limited |
1006 | to 8-bit encodings. |
1006 | to 8-bit encodings. |
1007 | |
1007 | |
1008 | =head1 RXVT TECHNICAL REFERENCE |
1008 | =head1 RXVT-UNICODE TECHNICAL REFERENCE |
1009 | |
1009 | |
1010 | =head1 DESCRIPTION |
1010 | =head1 DESCRIPTION |
1011 | |
1011 | |
1012 | The rest of this document describes various technical aspects of |
1012 | The rest of this document describes various technical aspects of |
1013 | B<rxvt-unicode>. First the description of supported command sequences, |
1013 | B<rxvt-unicode>. First the description of supported command sequences, |
… | |
… | |
1911 | =begin table |
1911 | =begin table |
1912 | |
1912 | |
1913 | 4 Shift |
1913 | 4 Shift |
1914 | 8 Meta |
1914 | 8 Meta |
1915 | 16 Control |
1915 | 16 Control |
1916 | 32 Double Click I<(Rxvt extension)> |
1916 | 32 Double Click I<(rxvt extension)> |
1917 | |
1917 | |
1918 | =end table |
1918 | =end table |
1919 | |
1919 | |
1920 | Col = B<< C<< <x> - SPACE >> >> |
1920 | Col = B<< C<< <x> - SPACE >> >> |
1921 | |
1921 | |