… | |
… | |
36 | |
36 | |
37 | Beginning with version 7.3, there is a perl extension that implements a |
37 | Beginning with version 7.3, there is a perl extension that implements a |
38 | simple tabbed terminal. It is installed by default, so any of these should |
38 | simple tabbed terminal. It is installed by default, so any of these should |
39 | give you tabs: |
39 | give you tabs: |
40 | |
40 | |
41 | @@RXVT_NAME@@ -pe tabbed |
41 | @@URXVT_NAME@@ -pe tabbed |
42 | |
42 | |
43 | URxvt.perl-ext-common: default,tabbed |
43 | URxvt.perl-ext-common: default,tabbed |
44 | |
44 | |
45 | It will also work fine with tabbing functionality of many window managers |
45 | It will also work fine with tabbing functionality of many window managers |
46 | or similar tabbing programs, and its embedding-features allow it to be |
46 | or similar tabbing programs, and its embedding-features allow it to be |
… | |
… | |
50 | |
50 | |
51 | =head3 How do I know which rxvt-unicode version I'm using? |
51 | =head3 How do I know which rxvt-unicode version I'm using? |
52 | |
52 | |
53 | The version number is displayed with the usage (-h). Also the escape |
53 | The version number is displayed with the usage (-h). Also the escape |
54 | sequence C<ESC [ 8 n> sets the window title to the version number. When |
54 | sequence C<ESC [ 8 n> sets the window title to the version number. When |
55 | using the @@RXVT_NAME@@c client, the version displayed is that of the |
55 | using the @@URXVT_NAME@@c client, the version displayed is that of the |
56 | daemon. |
56 | daemon. |
57 | |
57 | |
58 | =head3 Rxvt-unicode uses gobs of memory, how can I reduce that? |
58 | =head3 Rxvt-unicode uses gobs of memory, how can I reduce that? |
59 | |
59 | |
60 | Rxvt-unicode tries to obey the rule of not charging you for something you |
60 | Rxvt-unicode tries to obey the rule of not charging you for something you |
… | |
… | |
68 | 6 bytes per screen cell. For a 160x?? window this amounts to almost a |
68 | 6 bytes per screen cell. For a 160x?? window this amounts to almost a |
69 | kilobyte per line. A scrollback buffer of 10000 lines will then (if full) |
69 | kilobyte per line. A scrollback buffer of 10000 lines will then (if full) |
70 | use 10 Megabytes of memory. With C<--enable-unicode3> it gets worse, as |
70 | use 10 Megabytes of memory. With C<--enable-unicode3> it gets worse, as |
71 | rxvt-unicode then uses 8 bytes per screen cell. |
71 | rxvt-unicode then uses 8 bytes per screen cell. |
72 | |
72 | |
73 | =head3 How can I start @@RXVT_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<@@RXVT_NAME@@d -f -o>, which tells @@RXVT_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 | rxvt and rxvt-unicode always export the variable "COLORTERM", so you can |
… | |
… | |
203 | descriptions for the programs mentioned and rxvt-unicode. Really, do it! |
203 | descriptions for the programs mentioned and rxvt-unicode. Really, do it! |
204 | |
204 | |
205 | 1. Use inheritPixmap: |
205 | 1. Use inheritPixmap: |
206 | |
206 | |
207 | Esetroot wallpaper.jpg |
207 | Esetroot wallpaper.jpg |
208 | @@RXVT_NAME@@ -ip -tint red -sh 40 |
208 | @@URXVT_NAME@@ -ip -tint red -sh 40 |
209 | |
209 | |
210 | That works. If you think it doesn't, you lack transparency and tinting |
210 | That works. If you think it doesn't, you lack transparency and tinting |
211 | support, or you are unable to read. |
211 | support, or you are unable to read. |
212 | |
212 | |
213 | 2. Use a simple pixmap and emulate pseudo-transparency. This enables you |
213 | 2. Use a simple pixmap and emulate pseudo-transparency. This enables you |
214 | to use effects other than tinting and shading: Just shade/tint/whatever |
214 | to use effects other than tinting and shading: Just shade/tint/whatever |
215 | your picture with gimp or any other tool: |
215 | your picture with gimp or any other tool: |
216 | |
216 | |
217 | convert wallpaper.jpg -blur 20x20 -modulate 30 background.xpm |
217 | convert wallpaper.jpg -blur 20x20 -modulate 30 background.xpm |
218 | @@RXVT_NAME@@ -pixmap background.xpm -pe automove-background |
218 | @@URXVT_NAME@@ -pixmap background.xpm -pe automove-background |
219 | |
219 | |
220 | That works. If you think it doesn't, you lack XPM and Perl support, or you |
220 | That works. If you think it doesn't, you lack XPM and Perl support, or you |
221 | are unable to read. |
221 | are unable to read. |
222 | |
222 | |
223 | 3. Use an ARGB visual: |
223 | 3. Use an ARGB visual: |
224 | |
224 | |
225 | @@RXVT_NAME@@ -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc |
225 | @@URXVT_NAME@@ -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc |
226 | |
226 | |
227 | This requires XFT support, and the support of your X-server. If that |
227 | This requires XFT support, and the support of your X-server. If that |
228 | doesn't work for you, blame Xorg and Keith Packard. ARGB visuals aren't |
228 | doesn't work for you, blame Xorg and Keith Packard. ARGB visuals aren't |
229 | there yet, no matter what they claim. Rxvt-Unicode contains the neccessary |
229 | there yet, no matter what they claim. Rxvt-Unicode contains the neccessary |
230 | bugfixes and workarounds for Xft and Xlib to make it work, but that |
230 | bugfixes and workarounds for Xft and Xlib to make it work, but that |
… | |
… | |
431 | the font that the characters it claims to contain indeed look correct. |
431 | the font that the characters it claims to contain indeed look correct. |
432 | |
432 | |
433 | In that case, select a font of your taste and add it to the font list, |
433 | In that case, select a font of your taste and add it to the font list, |
434 | e.g.: |
434 | e.g.: |
435 | |
435 | |
436 | @@RXVT_NAME@@ -fn basefont,font2,font3... |
436 | @@URXVT_NAME@@ -fn basefont,font2,font3... |
437 | |
437 | |
438 | When rxvt-unicode sees a character, it will first look at the base |
438 | When rxvt-unicode sees a character, it will first look at the base |
439 | font. If the base font does not contain the character, it will go to the |
439 | font. If the base font does not contain the character, it will go to the |
440 | next font, and so on. Specifying your own fonts will also speed up this |
440 | next font, and so on. Specifying your own fonts will also speed up this |
441 | search and use less resources within rxvt-unicode and the X-server. |
441 | search and use less resources within rxvt-unicode and the X-server. |
… | |
… | |
470 | B<perl-ext-common> resource to the empty string, which also keeps |
470 | B<perl-ext-common> resource to the empty string, which also keeps |
471 | rxvt-unicode from initialising perl, saving memory. |
471 | rxvt-unicode from initialising perl, saving memory. |
472 | |
472 | |
473 | If you only want to disable specific features, you first have to |
473 | If you only want to disable specific features, you first have to |
474 | identify which perl extension is responsible. For this, read the section |
474 | identify which perl extension is responsible. For this, read the section |
475 | B<PREPACKAGED EXTENSIONS> in the @@RXVT_NAME@@perl(3) manpage. For |
475 | B<PREPACKAGED EXTENSIONS> in the @@URXVT_NAME@@perl(3) manpage. For |
476 | example, to disable the B<selection-popup> and B<option-popup>, specify |
476 | example, to disable the B<selection-popup> and B<option-popup>, specify |
477 | this B<perl-ext-common> resource: |
477 | this B<perl-ext-common> resource: |
478 | |
478 | |
479 | URxvt.perl-ext-common: default,-selection-popup,-option-popup |
479 | URxvt.perl-ext-common: default,-selection-popup,-option-popup |
480 | |
480 | |
… | |
… | |
558 | |
558 | |
559 | For starting a new rxvt-unicode: |
559 | For starting a new rxvt-unicode: |
560 | |
560 | |
561 | # use Backspace = ^H |
561 | # use Backspace = ^H |
562 | $ stty erase ^H |
562 | $ stty erase ^H |
563 | $ @@RXVT_NAME@@ |
563 | $ @@URXVT_NAME@@ |
564 | |
564 | |
565 | # use Backspace = ^? |
565 | # use Backspace = ^? |
566 | $ stty erase ^? |
566 | $ stty erase ^? |
567 | $ @@RXVT_NAME@@ |
567 | $ @@URXVT_NAME@@ |
568 | |
568 | |
569 | Toggle with C<ESC [ 36 h> / C<ESC [ 36 l>. |
569 | Toggle with C<ESC [ 36 h> / C<ESC [ 36 l>. |
570 | |
570 | |
571 | For an existing rxvt-unicode: |
571 | For an existing rxvt-unicode: |
572 | |
572 | |
… | |
… | |
599 | |
599 | |
600 | There are some compile-time selections available via configure. Unless |
600 | There are some compile-time selections available via configure. Unless |
601 | you have run "configure" with the C<--disable-resources> option you can |
601 | you have run "configure" with the C<--disable-resources> option you can |
602 | use the `keysym' resource to alter the keystrings associated with keysyms. |
602 | use the `keysym' resource to alter the keystrings associated with keysyms. |
603 | |
603 | |
604 | Here's an example for a URxvt session started using C<@@RXVT_NAME@@ -name URxvt> |
604 | Here's an example for a URxvt session started using C<@@URXVT_NAME@@ -name URxvt> |
605 | |
605 | |
606 | URxvt.keysym.Home: \033[1~ |
606 | URxvt.keysym.Home: \033[1~ |
607 | URxvt.keysym.End: \033[4~ |
607 | URxvt.keysym.End: \033[4~ |
608 | URxvt.keysym.C-apostrophe: \033<C-'> |
608 | URxvt.keysym.C-apostrophe: \033<C-'> |
609 | URxvt.keysym.C-slash: \033<C-/> |
609 | URxvt.keysym.C-slash: \033<C-/> |
… | |
… | |
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. |
698 | |
698 | |
699 | =head3 C<bash>'s readline does not work correctly under @@RXVT_NAME@@. |
699 | =head3 C<bash>'s readline does not work correctly under @@URXVT_NAME@@. |
700 | |
700 | |
701 | See next entry. |
701 | See next entry. |
702 | |
702 | |
703 | =head3 I need a termcap file entry. |
703 | =head3 I need a termcap file entry. |
704 | |
704 | |