| … | |
… | |
| 172 | Beginning with version 7.3, there is a perl extension that implements a |
172 | Beginning with version 7.3, there is a perl extension that implements a |
| 173 | simple tabbed terminal. It is installed by default, so any of these should |
173 | simple tabbed terminal. It is installed by default, so any of these should |
| 174 | give you tabs: |
174 | give you tabs: |
| 175 | .PP |
175 | .PP |
| 176 | .Vb 1 |
176 | .Vb 1 |
| 177 | \& @@RXVT_NAME@@ -pe tabbed |
177 | \& @@URXVT_NAME@@ -pe tabbed |
| 178 | .Ve |
178 | .Ve |
| 179 | .PP |
179 | .PP |
| 180 | .Vb 1 |
180 | .Vb 1 |
| 181 | \& URxvt.perl-ext-common: default,tabbed |
181 | \& URxvt.perl-ext-common: default,tabbed |
| 182 | .Ve |
182 | .Ve |
| … | |
… | |
| 190 | \fIHow do I know which rxvt-unicode version I'm using?\fR |
190 | \fIHow do I know which rxvt-unicode version I'm using?\fR |
| 191 | .IX Subsection "How do I know which rxvt-unicode version I'm using?" |
191 | .IX Subsection "How do I know which rxvt-unicode version I'm using?" |
| 192 | .PP |
192 | .PP |
| 193 | The version number is displayed with the usage (\-h). Also the escape |
193 | The version number is displayed with the usage (\-h). Also the escape |
| 194 | sequence \f(CW\*(C`ESC [ 8 n\*(C'\fR sets the window title to the version number. When |
194 | sequence \f(CW\*(C`ESC [ 8 n\*(C'\fR sets the window title to the version number. When |
| 195 | using the @@RXVT_NAME@@c client, the version displayed is that of the |
195 | using the @@URXVT_NAME@@c client, the version displayed is that of the |
| 196 | daemon. |
196 | daemon. |
| 197 | .PP |
197 | .PP |
| 198 | \fIRxvt-unicode uses gobs of memory, how can I reduce that?\fR |
198 | \fIRxvt-unicode uses gobs of memory, how can I reduce that?\fR |
| 199 | .IX Subsection "Rxvt-unicode uses gobs of memory, how can I reduce that?" |
199 | .IX Subsection "Rxvt-unicode uses gobs of memory, how can I reduce that?" |
| 200 | .PP |
200 | .PP |
| … | |
… | |
| 209 | 6 bytes per screen cell. For a 160x?? window this amounts to almost a |
209 | 6 bytes per screen cell. For a 160x?? window this amounts to almost a |
| 210 | kilobyte per line. A scrollback buffer of 10000 lines will then (if full) |
210 | kilobyte per line. A scrollback buffer of 10000 lines will then (if full) |
| 211 | use 10 Megabytes of memory. With \f(CW\*(C`\-\-enable\-unicode3\*(C'\fR it gets worse, as |
211 | use 10 Megabytes of memory. With \f(CW\*(C`\-\-enable\-unicode3\*(C'\fR it gets worse, as |
| 212 | rxvt-unicode then uses 8 bytes per screen cell. |
212 | rxvt-unicode then uses 8 bytes per screen cell. |
| 213 | .PP |
213 | .PP |
| 214 | \fIHow can I start @@RXVT_NAME@@d in a race-free way?\fR |
214 | \fIHow can I start @@URXVT_NAME@@d in a race-free way?\fR |
| 215 | .IX Subsection "How can I start @@RXVT_NAME@@d in a race-free way?" |
215 | .IX Subsection "How can I start @@URXVT_NAME@@d in a race-free way?" |
| 216 | .PP |
216 | .PP |
| 217 | Try \f(CW\*(C`@@RXVT_NAME@@d \-f \-o\*(C'\fR, which tells @@RXVT_NAME@@d to open the |
217 | Try \f(CW\*(C`@@URXVT_NAME@@d \-f \-o\*(C'\fR, which tells @@URXVT_NAME@@d to open the |
| 218 | display, create the listening socket and then fork. |
218 | display, create the listening socket and then fork. |
| 219 | .PP |
219 | .PP |
| 220 | \fIHow do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc.\fR |
220 | \fIHow do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc.\fR |
| 221 | .IX Subsection "How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc." |
221 | .IX Subsection "How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc." |
| 222 | .PP |
222 | .PP |
| … | |
… | |
| 360 | .PP |
360 | .PP |
| 361 | 1. Use inheritPixmap: |
361 | 1. Use inheritPixmap: |
| 362 | .PP |
362 | .PP |
| 363 | .Vb 2 |
363 | .Vb 2 |
| 364 | \& Esetroot wallpaper.jpg |
364 | \& Esetroot wallpaper.jpg |
| 365 | \& @@RXVT_NAME@@ -ip -tint red -sh 40 |
365 | \& @@URXVT_NAME@@ -ip -tint red -sh 40 |
| 366 | .Ve |
366 | .Ve |
| 367 | .PP |
367 | .PP |
| 368 | That works. If you think it doesn't, you lack transparency and tinting |
368 | That works. If you think it doesn't, you lack transparency and tinting |
| 369 | support, or you are unable to read. |
369 | support, or you are unable to read. |
| 370 | .PP |
370 | .PP |
| … | |
… | |
| 372 | to use effects other than tinting and shading: Just shade/tint/whatever |
372 | to use effects other than tinting and shading: Just shade/tint/whatever |
| 373 | your picture with gimp or any other tool: |
373 | your picture with gimp or any other tool: |
| 374 | .PP |
374 | .PP |
| 375 | .Vb 2 |
375 | .Vb 2 |
| 376 | \& convert wallpaper.jpg -blur 20x20 -modulate 30 background.xpm |
376 | \& convert wallpaper.jpg -blur 20x20 -modulate 30 background.xpm |
| 377 | \& @@RXVT_NAME@@ -pixmap background.xpm -pe automove-background |
377 | \& @@URXVT_NAME@@ -pixmap background.xpm -pe automove-background |
| 378 | .Ve |
378 | .Ve |
| 379 | .PP |
379 | .PP |
| 380 | That works. If you think it doesn't, you lack \s-1XPM\s0 and Perl support, or you |
380 | That works. If you think it doesn't, you lack \s-1XPM\s0 and Perl support, or you |
| 381 | are unable to read. |
381 | are unable to read. |
| 382 | .PP |
382 | .PP |
| 383 | 3. Use an \s-1ARGB\s0 visual: |
383 | 3. Use an \s-1ARGB\s0 visual: |
| 384 | .PP |
384 | .PP |
| 385 | .Vb 1 |
385 | .Vb 1 |
| 386 | \& @@RXVT_NAME@@ -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc |
386 | \& @@URXVT_NAME@@ -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc |
| 387 | .Ve |
387 | .Ve |
| 388 | .PP |
388 | .PP |
| 389 | This requires \s-1XFT\s0 support, and the support of your X\-server. If that |
389 | This requires \s-1XFT\s0 support, and the support of your X\-server. If that |
| 390 | doesn't work for you, blame Xorg and Keith Packard. \s-1ARGB\s0 visuals aren't |
390 | doesn't work for you, blame Xorg and Keith Packard. \s-1ARGB\s0 visuals aren't |
| 391 | there yet, no matter what they claim. Rxvt-Unicode contains the neccessary |
391 | there yet, no matter what they claim. Rxvt-Unicode contains the neccessary |
| … | |
… | |
| 619 | .PP |
619 | .PP |
| 620 | In that case, select a font of your taste and add it to the font list, |
620 | In that case, select a font of your taste and add it to the font list, |
| 621 | e.g.: |
621 | e.g.: |
| 622 | .PP |
622 | .PP |
| 623 | .Vb 1 |
623 | .Vb 1 |
| 624 | \& @@RXVT_NAME@@ -fn basefont,font2,font3... |
624 | \& @@URXVT_NAME@@ -fn basefont,font2,font3... |
| 625 | .Ve |
625 | .Ve |
| 626 | .PP |
626 | .PP |
| 627 | When rxvt-unicode sees a character, it will first look at the base |
627 | When rxvt-unicode sees a character, it will first look at the base |
| 628 | font. If the base font does not contain the character, it will go to the |
628 | font. If the base font does not contain the character, it will go to the |
| 629 | next font, and so on. Specifying your own fonts will also speed up this |
629 | next font, and so on. Specifying your own fonts will also speed up this |
| … | |
… | |
| 663 | \&\fBperl-ext-common\fR resource to the empty string, which also keeps |
663 | \&\fBperl-ext-common\fR resource to the empty string, which also keeps |
| 664 | rxvt-unicode from initialising perl, saving memory. |
664 | rxvt-unicode from initialising perl, saving memory. |
| 665 | .PP |
665 | .PP |
| 666 | If you only want to disable specific features, you first have to |
666 | If you only want to disable specific features, you first have to |
| 667 | identify which perl extension is responsible. For this, read the section |
667 | identify which perl extension is responsible. For this, read the section |
| 668 | \&\fB\s-1PREPACKAGED\s0 \s-1EXTENSIONS\s0\fR in the @@RXVT_NAME@@\fIperl\fR\|(3) manpage. For |
668 | \&\fB\s-1PREPACKAGED\s0 \s-1EXTENSIONS\s0\fR in the @@URXVT_NAME@@\fIperl\fR\|(3) manpage. For |
| 669 | example, to disable the \fBselection-popup\fR and \fBoption-popup\fR, specify |
669 | example, to disable the \fBselection-popup\fR and \fBoption-popup\fR, specify |
| 670 | this \fBperl-ext-common\fR resource: |
670 | this \fBperl-ext-common\fR resource: |
| 671 | .PP |
671 | .PP |
| 672 | .Vb 1 |
672 | .Vb 1 |
| 673 | \& URxvt.perl-ext-common: default,-selection-popup,-option-popup |
673 | \& URxvt.perl-ext-common: default,-selection-popup,-option-popup |
| … | |
… | |
| 765 | For starting a new rxvt\-unicode: |
765 | For starting a new rxvt\-unicode: |
| 766 | .PP |
766 | .PP |
| 767 | .Vb 3 |
767 | .Vb 3 |
| 768 | \& # use Backspace = ^H |
768 | \& # use Backspace = ^H |
| 769 | \& $ stty erase ^H |
769 | \& $ stty erase ^H |
| 770 | \& $ @@RXVT_NAME@@ |
770 | \& $ @@URXVT_NAME@@ |
| 771 | .Ve |
771 | .Ve |
| 772 | .PP |
772 | .PP |
| 773 | .Vb 3 |
773 | .Vb 3 |
| 774 | \& # use Backspace = ^? |
774 | \& # use Backspace = ^? |
| 775 | \& $ stty erase ^? |
775 | \& $ stty erase ^? |
| 776 | \& $ @@RXVT_NAME@@ |
776 | \& $ @@URXVT_NAME@@ |
| 777 | .Ve |
777 | .Ve |
| 778 | .PP |
778 | .PP |
| 779 | Toggle with \f(CW\*(C`ESC [ 36 h\*(C'\fR / \f(CW\*(C`ESC [ 36 l\*(C'\fR. |
779 | Toggle with \f(CW\*(C`ESC [ 36 h\*(C'\fR / \f(CW\*(C`ESC [ 36 l\*(C'\fR. |
| 780 | .PP |
780 | .PP |
| 781 | For an existing rxvt\-unicode: |
781 | For an existing rxvt\-unicode: |
| … | |
… | |
| 814 | .PP |
814 | .PP |
| 815 | There are some compile-time selections available via configure. Unless |
815 | There are some compile-time selections available via configure. Unless |
| 816 | you have run \*(L"configure\*(R" with the \f(CW\*(C`\-\-disable\-resources\*(C'\fR option you can |
816 | you have run \*(L"configure\*(R" with the \f(CW\*(C`\-\-disable\-resources\*(C'\fR option you can |
| 817 | use the `keysym' resource to alter the keystrings associated with keysyms. |
817 | use the `keysym' resource to alter the keystrings associated with keysyms. |
| 818 | .PP |
818 | .PP |
| 819 | Here's an example for a URxvt session started using \f(CW\*(C`@@RXVT_NAME@@ \-name URxvt\*(C'\fR |
819 | Here's an example for a URxvt session started using \f(CW\*(C`@@URXVT_NAME@@ \-name URxvt\*(C'\fR |
| 820 | .PP |
820 | .PP |
| 821 | .Vb 20 |
821 | .Vb 20 |
| 822 | \& URxvt.keysym.Home: \e033[1~ |
822 | \& URxvt.keysym.Home: \e033[1~ |
| 823 | \& URxvt.keysym.End: \e033[4~ |
823 | \& URxvt.keysym.End: \e033[4~ |
| 824 | \& URxvt.keysym.C-apostrophe: \e033<C-'> |
824 | \& URxvt.keysym.C-apostrophe: \e033<C-'> |
| … | |
… | |
| 920 | .IX Subsection "tic outputs some error when compiling the terminfo entry." |
920 | .IX Subsection "tic outputs some error when compiling the terminfo entry." |
| 921 | .PP |
921 | .PP |
| 922 | Most likely it's the empty definition for \f(CW\*(C`enacs=\*(C'\fR. Just replace it by |
922 | Most likely it's the empty definition for \f(CW\*(C`enacs=\*(C'\fR. Just replace it by |
| 923 | \&\f(CW\*(C`enacs=\eE[0@\*(C'\fR and try again. |
923 | \&\f(CW\*(C`enacs=\eE[0@\*(C'\fR and try again. |
| 924 | .PP |
924 | .PP |
| 925 | \fI\f(CI\*(C`bash\*(C'\fI's readline does not work correctly under @@RXVT_NAME@@.\fR |
925 | \fI\f(CI\*(C`bash\*(C'\fI's readline does not work correctly under @@URXVT_NAME@@.\fR |
| 926 | .IX Subsection "bash's readline does not work correctly under @@RXVT_NAME@@." |
926 | .IX Subsection "bash's readline does not work correctly under @@URXVT_NAME@@." |
| 927 | .PP |
927 | .PP |
| 928 | See next entry. |
928 | See next entry. |
| 929 | .PP |
929 | .PP |
| 930 | \fII need a termcap file entry.\fR |
930 | \fII need a termcap file entry.\fR |
| 931 | .IX Subsection "I need a termcap file entry." |
931 | .IX Subsection "I need a termcap file entry." |
