| … | |
… | |
| 29 | Does it support tabs, can I have a tabbed rxvt-unicode? |
29 | Does it support tabs, can I have a tabbed rxvt-unicode? |
| 30 | Beginning with version 7.3, there is a perl extension that implements a |
30 | Beginning with version 7.3, there is a perl extension that implements a |
| 31 | simple tabbed terminal. It is installed by default, so any of these |
31 | simple tabbed terminal. It is installed by default, so any of these |
| 32 | should give you tabs: |
32 | should give you tabs: |
| 33 | |
33 | |
| 34 | rxvt -pe tabbed |
34 | urxvt -pe tabbed |
| 35 | |
35 | |
| 36 | URxvt.perl-ext-common: default,tabbed |
36 | URxvt.perl-ext-common: default,tabbed |
| 37 | |
37 | |
| 38 | It will also work fine with tabbing functionality of many window |
38 | It will also work fine with tabbing functionality of many window |
| 39 | managers or similar tabbing programs, and its embedding-features allow |
39 | managers or similar tabbing programs, and its embedding-features allow |
| … | |
… | |
| 42 | (murxvt) terminal as an example embedding application. |
42 | (murxvt) terminal as an example embedding application. |
| 43 | |
43 | |
| 44 | How do I know which rxvt-unicode version I'm using? |
44 | How do I know which rxvt-unicode version I'm using? |
| 45 | The version number is displayed with the usage (-h). Also the escape |
45 | The version number is displayed with the usage (-h). Also the escape |
| 46 | sequence "ESC [ 8 n" sets the window title to the version number. When |
46 | sequence "ESC [ 8 n" sets the window title to the version number. When |
| 47 | using the rxvtc client, the version displayed is that of the daemon. |
47 | using the urxvtc client, the version displayed is that of the daemon. |
| 48 | |
48 | |
| 49 | Rxvt-unicode uses gobs of memory, how can I reduce that? |
49 | Rxvt-unicode uses gobs of memory, how can I reduce that? |
| 50 | Rxvt-unicode tries to obey the rule of not charging you for something |
50 | Rxvt-unicode tries to obey the rule of not charging you for something |
| 51 | you don't use. One thing you should try is to configure out all settings |
51 | you don't use. One thing you should try is to configure out all settings |
| 52 | that you don't need, for example, Xft support is a resource hog by |
52 | that you don't need, for example, Xft support is a resource hog by |
| … | |
… | |
| 59 | bytes per screen cell. For a 160x?? window this amounts to almost a |
59 | bytes per screen cell. For a 160x?? window this amounts to almost a |
| 60 | kilobyte per line. A scrollback buffer of 10000 lines will then (if |
60 | kilobyte per line. A scrollback buffer of 10000 lines will then (if |
| 61 | full) use 10 Megabytes of memory. With "--enable-unicode3" it gets |
61 | full) use 10 Megabytes of memory. With "--enable-unicode3" it gets |
| 62 | worse, as rxvt-unicode then uses 8 bytes per screen cell. |
62 | worse, as rxvt-unicode then uses 8 bytes per screen cell. |
| 63 | |
63 | |
| 64 | How can I start rxvtd in a race-free way? |
64 | How can I start urxvtd in a race-free way? |
| 65 | Try "rxvtd -f -o", which tells rxvtd to open the display, create the |
65 | Try "urxvtd -f -o", which tells urxvtd to open the display, create the |
| 66 | listening socket and then fork. |
66 | listening socket and then fork. |
| 67 | |
67 | |
| 68 | How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc. |
68 | How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc. |
| 69 | rxvt and rxvt-unicode always export the variable "COLORTERM", so you can |
69 | rxvt and rxvt-unicode always export the variable "COLORTERM", so you can |
| 70 | check and see if that is set. Note that several programs, JED, slrn, |
70 | check and see if that is set. Note that several programs, JED, slrn, |
| … | |
… | |
| 185 | descriptions for the programs mentioned and rxvt-unicode. Really, do it! |
185 | descriptions for the programs mentioned and rxvt-unicode. Really, do it! |
| 186 | |
186 | |
| 187 | 1. Use inheritPixmap: |
187 | 1. Use inheritPixmap: |
| 188 | |
188 | |
| 189 | Esetroot wallpaper.jpg |
189 | Esetroot wallpaper.jpg |
| 190 | rxvt -ip -tint red -sh 40 |
190 | urxvt -ip -tint red -sh 40 |
| 191 | |
191 | |
| 192 | That works. If you think it doesn't, you lack transparency and tinting |
192 | That works. If you think it doesn't, you lack transparency and tinting |
| 193 | support, or you are unable to read. |
193 | support, or you are unable to read. |
| 194 | |
194 | |
| 195 | 2. Use a simple pixmap and emulate pseudo-transparency. This enables you |
195 | 2. Use a simple pixmap and emulate pseudo-transparency. This enables you |
| 196 | to use effects other than tinting and shading: Just shade/tint/whatever |
196 | to use effects other than tinting and shading: Just shade/tint/whatever |
| 197 | your picture with gimp or any other tool: |
197 | your picture with gimp or any other tool: |
| 198 | |
198 | |
| 199 | convert wallpaper.jpg -blur 20x20 -modulate 30 background.xpm |
199 | convert wallpaper.jpg -blur 20x20 -modulate 30 background.xpm |
| 200 | rxvt -pixmap background.xpm -pe automove-background |
200 | urxvt -pixmap background.xpm -pe automove-background |
| 201 | |
201 | |
| 202 | That works. If you think it doesn't, you lack XPM and Perl support, or |
202 | That works. If you think it doesn't, you lack XPM and Perl support, or |
| 203 | you are unable to read. |
203 | you are unable to read. |
| 204 | |
204 | |
| 205 | 3. Use an ARGB visual: |
205 | 3. Use an ARGB visual: |
| 206 | |
206 | |
| 207 | rxvt -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc |
207 | urxvt -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc |
| 208 | |
208 | |
| 209 | This requires XFT support, and the support of your X-server. If that |
209 | This requires XFT support, and the support of your X-server. If that |
| 210 | doesn't work for you, blame Xorg and Keith Packard. ARGB visuals aren't |
210 | doesn't work for you, blame Xorg and Keith Packard. ARGB visuals aren't |
| 211 | there yet, no matter what they claim. Rxvt-Unicode contains the |
211 | there yet, no matter what they claim. Rxvt-Unicode contains the |
| 212 | neccessary bugfixes and workarounds for Xft and Xlib to make it work, |
212 | neccessary bugfixes and workarounds for Xft and Xlib to make it work, |
| … | |
… | |
| 402 | the font that the characters it claims to contain indeed look correct. |
402 | the font that the characters it claims to contain indeed look correct. |
| 403 | |
403 | |
| 404 | In that case, select a font of your taste and add it to the font list, |
404 | In that case, select a font of your taste and add it to the font list, |
| 405 | e.g.: |
405 | e.g.: |
| 406 | |
406 | |
| 407 | rxvt -fn basefont,font2,font3... |
407 | urxvt -fn basefont,font2,font3... |
| 408 | |
408 | |
| 409 | When rxvt-unicode sees a character, it will first look at the base font. |
409 | When rxvt-unicode sees a character, it will first look at the base font. |
| 410 | If the base font does not contain the character, it will go to the next |
410 | If the base font does not contain the character, it will go to the next |
| 411 | font, and so on. Specifying your own fonts will also speed up this |
411 | font, and so on. Specifying your own fonts will also speed up this |
| 412 | search and use less resources within rxvt-unicode and the X-server. |
412 | search and use less resources within rxvt-unicode and the X-server. |
| … | |
… | |
| 438 | perl-ext-common resource to the empty string, which also keeps |
438 | perl-ext-common resource to the empty string, which also keeps |
| 439 | rxvt-unicode from initialising perl, saving memory. |
439 | rxvt-unicode from initialising perl, saving memory. |
| 440 | |
440 | |
| 441 | If you only want to disable specific features, you first have to |
441 | If you only want to disable specific features, you first have to |
| 442 | identify which perl extension is responsible. For this, read the section |
442 | identify which perl extension is responsible. For this, read the section |
| 443 | PREPACKAGED EXTENSIONS in the rxvtperl(3) manpage. For example, to |
443 | PREPACKAGED EXTENSIONS in the urxvtperl(3) manpage. For example, to |
| 444 | disable the selection-popup and option-popup, specify this |
444 | disable the selection-popup and option-popup, specify this |
| 445 | perl-ext-common resource: |
445 | perl-ext-common resource: |
| 446 | |
446 | |
| 447 | URxvt.perl-ext-common: default,-selection-popup,-option-popup |
447 | URxvt.perl-ext-common: default,-selection-popup,-option-popup |
| 448 | |
448 | |
| … | |
… | |
| 519 | |
519 | |
| 520 | For starting a new rxvt-unicode: |
520 | For starting a new rxvt-unicode: |
| 521 | |
521 | |
| 522 | # use Backspace = ^H |
522 | # use Backspace = ^H |
| 523 | $ stty erase ^H |
523 | $ stty erase ^H |
| 524 | $ rxvt |
524 | $ urxvt |
| 525 | |
525 | |
| 526 | # use Backspace = ^? |
526 | # use Backspace = ^? |
| 527 | $ stty erase ^? |
527 | $ stty erase ^? |
| 528 | $ rxvt |
528 | $ urxvt |
| 529 | |
529 | |
| 530 | Toggle with "ESC [ 36 h" / "ESC [ 36 l". |
530 | Toggle with "ESC [ 36 h" / "ESC [ 36 l". |
| 531 | |
531 | |
| 532 | For an existing rxvt-unicode: |
532 | For an existing rxvt-unicode: |
| 533 | |
533 | |
| … | |
… | |
| 559 | There are some compile-time selections available via configure. Unless |
559 | There are some compile-time selections available via configure. Unless |
| 560 | you have run "configure" with the "--disable-resources" option you can |
560 | you have run "configure" with the "--disable-resources" option you can |
| 561 | use the `keysym' resource to alter the keystrings associated with |
561 | use the `keysym' resource to alter the keystrings associated with |
| 562 | keysyms. |
562 | keysyms. |
| 563 | |
563 | |
| 564 | Here's an example for a URxvt session started using "rxvt -name URxvt" |
564 | Here's an example for a URxvt session started using "urxvt -name URxvt" |
| 565 | |
565 | |
| 566 | URxvt.keysym.Home: \033[1~ |
566 | URxvt.keysym.Home: \033[1~ |
| 567 | URxvt.keysym.End: \033[4~ |
567 | URxvt.keysym.End: \033[4~ |
| 568 | URxvt.keysym.C-apostrophe: \033<C-'> |
568 | URxvt.keysym.C-apostrophe: \033<C-'> |
| 569 | URxvt.keysym.C-slash: \033<C-/> |
569 | URxvt.keysym.C-slash: \033<C-/> |
| … | |
… | |
| 648 | |
648 | |
| 649 | "tic" outputs some error when compiling the terminfo entry. |
649 | "tic" outputs some error when compiling the terminfo entry. |
| 650 | Most likely it's the empty definition for "enacs=". Just replace it by |
650 | Most likely it's the empty definition for "enacs=". Just replace it by |
| 651 | "enacs=\E[0@" and try again. |
651 | "enacs=\E[0@" and try again. |
| 652 | |
652 | |
| 653 | "bash"'s readline does not work correctly under rxvt. |
653 | "bash"'s readline does not work correctly under urxvt. |
| 654 | See next entry. |
654 | See next entry. |
| 655 | |
655 | |
| 656 | I need a termcap file entry. |
656 | I need a termcap file entry. |
| 657 | One reason you might want this is that some distributions or operating |
657 | One reason you might want this is that some distributions or operating |
| 658 | systems still compile some programs using the long-obsoleted termcap |
658 | systems still compile some programs using the long-obsoleted termcap |
