| … | |
… | |
| 8 | Does it support tabs, can I have a tabbed rxvt-unicode? |
8 | Does it support tabs, can I have a tabbed rxvt-unicode? |
| 9 | Beginning with version 7.3, there is a perl extension that implements a |
9 | Beginning with version 7.3, there is a perl extension that implements a |
| 10 | simple tabbed terminal. It is installed by default, so any of these |
10 | simple tabbed terminal. It is installed by default, so any of these |
| 11 | should give you tabs: |
11 | should give you tabs: |
| 12 | |
12 | |
| 13 | rxvt -pe tabbed |
13 | urxvt -pe tabbed |
| 14 | |
14 | |
| 15 | URxvt.perl-ext-common: default,tabbed |
15 | URxvt.perl-ext-common: default,tabbed |
| 16 | |
16 | |
| 17 | It will also work fine with tabbing functionality of many window |
17 | It will also work fine with tabbing functionality of many window |
| 18 | managers or similar tabbing programs, and its embedding-features allow |
18 | managers or similar tabbing programs, and its embedding-features allow |
| … | |
… | |
| 21 | (murxvt) terminal as an example embedding application. |
21 | (murxvt) terminal as an example embedding application. |
| 22 | |
22 | |
| 23 | How do I know which rxvt-unicode version I'm using? |
23 | How do I know which rxvt-unicode version I'm using? |
| 24 | The version number is displayed with the usage (-h). Also the escape |
24 | The version number is displayed with the usage (-h). Also the escape |
| 25 | sequence "ESC [ 8 n" sets the window title to the version number. When |
25 | sequence "ESC [ 8 n" sets the window title to the version number. When |
| 26 | using the rxvtc client, the version displayed is that of the daemon. |
26 | using the urxvtc client, the version displayed is that of the daemon. |
| 27 | |
27 | |
| 28 | Rxvt-unicode uses gobs of memory, how can I reduce that? |
28 | Rxvt-unicode uses gobs of memory, how can I reduce that? |
| 29 | Rxvt-unicode tries to obey the rule of not charging you for something |
29 | Rxvt-unicode tries to obey the rule of not charging you for something |
| 30 | you don't use. One thing you should try is to configure out all settings |
30 | you don't use. One thing you should try is to configure out all settings |
| 31 | that you don't need, for example, Xft support is a resource hog by |
31 | that you don't need, for example, Xft support is a resource hog by |
| … | |
… | |
| 38 | bytes per screen cell. For a 160x?? window this amounts to almost a |
38 | bytes per screen cell. For a 160x?? window this amounts to almost a |
| 39 | kilobyte per line. A scrollback buffer of 10000 lines will then (if |
39 | kilobyte per line. A scrollback buffer of 10000 lines will then (if |
| 40 | full) use 10 Megabytes of memory. With "--enable-unicode3" it gets |
40 | full) use 10 Megabytes of memory. With "--enable-unicode3" it gets |
| 41 | worse, as rxvt-unicode then uses 8 bytes per screen cell. |
41 | worse, as rxvt-unicode then uses 8 bytes per screen cell. |
| 42 | |
42 | |
| 43 | How can I start rxvtd in a race-free way? |
43 | How can I start urxvtd in a race-free way? |
| 44 | Try "rxvtd -f -o", which tells rxvtd to open the display, create the |
44 | Try "urxvtd -f -o", which tells urxvtd to open the display, create the |
| 45 | listening socket and then fork. |
45 | listening socket and then fork. |
| 46 | |
46 | |
| 47 | How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc. |
47 | How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc. |
| 48 | rxvt and rxvt-unicode always export the variable "COLORTERM", so you can |
48 | rxvt and rxvt-unicode always export the variable "COLORTERM", so you can |
| 49 | check and see if that is set. Note that several programs, JED, slrn, |
49 | check and see if that is set. Note that several programs, JED, slrn, |
| … | |
… | |
| 164 | descriptions for the programs mentioned and rxvt-unicode. Really, do it! |
164 | descriptions for the programs mentioned and rxvt-unicode. Really, do it! |
| 165 | |
165 | |
| 166 | 1. Use inheritPixmap: |
166 | 1. Use inheritPixmap: |
| 167 | |
167 | |
| 168 | Esetroot wallpaper.jpg |
168 | Esetroot wallpaper.jpg |
| 169 | rxvt -ip -tint red -sh 40 |
169 | urxvt -ip -tint red -sh 40 |
| 170 | |
170 | |
| 171 | That works. If you think it doesn't, you lack transparency and tinting |
171 | That works. If you think it doesn't, you lack transparency and tinting |
| 172 | support, or you are unable to read. |
172 | support, or you are unable to read. |
| 173 | |
173 | |
| 174 | 2. Use a simple pixmap and emulate pseudo-transparency. This enables you |
174 | 2. Use a simple pixmap and emulate pseudo-transparency. This enables you |
| 175 | to use effects other than tinting and shading: Just shade/tint/whatever |
175 | to use effects other than tinting and shading: Just shade/tint/whatever |
| 176 | your picture with gimp or any other tool: |
176 | your picture with gimp or any other tool: |
| 177 | |
177 | |
| 178 | convert wallpaper.jpg -blur 20x20 -modulate 30 background.xpm |
178 | convert wallpaper.jpg -blur 20x20 -modulate 30 background.xpm |
| 179 | rxvt -pixmap background.xpm -pe automove-background |
179 | urxvt -pixmap background.xpm -pe automove-background |
| 180 | |
180 | |
| 181 | That works. If you think it doesn't, you lack XPM and Perl support, or |
181 | That works. If you think it doesn't, you lack XPM and Perl support, or |
| 182 | you are unable to read. |
182 | you are unable to read. |
| 183 | |
183 | |
| 184 | 3. Use an ARGB visual: |
184 | 3. Use an ARGB visual: |
| 185 | |
185 | |
| 186 | rxvt -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc |
186 | urxvt -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc |
| 187 | |
187 | |
| 188 | This requires XFT support, and the support of your X-server. If that |
188 | This requires XFT support, and the support of your X-server. If that |
| 189 | doesn't work for you, blame Xorg and Keith Packard. ARGB visuals aren't |
189 | doesn't work for you, blame Xorg and Keith Packard. ARGB visuals aren't |
| 190 | there yet, no matter what they claim. Rxvt-Unicode contains the |
190 | there yet, no matter what they claim. Rxvt-Unicode contains the |
| 191 | neccessary bugfixes and workarounds for Xft and Xlib to make it work, |
191 | neccessary bugfixes and workarounds for Xft and Xlib to make it work, |
| … | |
… | |
| 381 | the font that the characters it claims to contain indeed look correct. |
381 | the font that the characters it claims to contain indeed look correct. |
| 382 | |
382 | |
| 383 | In that case, select a font of your taste and add it to the font list, |
383 | In that case, select a font of your taste and add it to the font list, |
| 384 | e.g.: |
384 | e.g.: |
| 385 | |
385 | |
| 386 | rxvt -fn basefont,font2,font3... |
386 | urxvt -fn basefont,font2,font3... |
| 387 | |
387 | |
| 388 | When rxvt-unicode sees a character, it will first look at the base font. |
388 | When rxvt-unicode sees a character, it will first look at the base font. |
| 389 | If the base font does not contain the character, it will go to the next |
389 | If the base font does not contain the character, it will go to the next |
| 390 | font, and so on. Specifying your own fonts will also speed up this |
390 | font, and so on. Specifying your own fonts will also speed up this |
| 391 | search and use less resources within rxvt-unicode and the X-server. |
391 | search and use less resources within rxvt-unicode and the X-server. |
| … | |
… | |
| 417 | perl-ext-common resource to the empty string, which also keeps |
417 | perl-ext-common resource to the empty string, which also keeps |
| 418 | rxvt-unicode from initialising perl, saving memory. |
418 | rxvt-unicode from initialising perl, saving memory. |
| 419 | |
419 | |
| 420 | If you only want to disable specific features, you first have to |
420 | If you only want to disable specific features, you first have to |
| 421 | identify which perl extension is responsible. For this, read the section |
421 | identify which perl extension is responsible. For this, read the section |
| 422 | PREPACKAGED EXTENSIONS in the rxvtperl(3) manpage. For example, to |
422 | PREPACKAGED EXTENSIONS in the urxvtperl(3) manpage. For example, to |
| 423 | disable the selection-popup and option-popup, specify this |
423 | disable the selection-popup and option-popup, specify this |
| 424 | perl-ext-common resource: |
424 | perl-ext-common resource: |
| 425 | |
425 | |
| 426 | URxvt.perl-ext-common: default,-selection-popup,-option-popup |
426 | URxvt.perl-ext-common: default,-selection-popup,-option-popup |
| 427 | |
427 | |
| … | |
… | |
| 498 | |
498 | |
| 499 | For starting a new rxvt-unicode: |
499 | For starting a new rxvt-unicode: |
| 500 | |
500 | |
| 501 | # use Backspace = ^H |
501 | # use Backspace = ^H |
| 502 | $ stty erase ^H |
502 | $ stty erase ^H |
| 503 | $ rxvt |
503 | $ urxvt |
| 504 | |
504 | |
| 505 | # use Backspace = ^? |
505 | # use Backspace = ^? |
| 506 | $ stty erase ^? |
506 | $ stty erase ^? |
| 507 | $ rxvt |
507 | $ urxvt |
| 508 | |
508 | |
| 509 | Toggle with "ESC [ 36 h" / "ESC [ 36 l". |
509 | Toggle with "ESC [ 36 h" / "ESC [ 36 l". |
| 510 | |
510 | |
| 511 | For an existing rxvt-unicode: |
511 | For an existing rxvt-unicode: |
| 512 | |
512 | |
| … | |
… | |
| 538 | There are some compile-time selections available via configure. Unless |
538 | There are some compile-time selections available via configure. Unless |
| 539 | you have run "configure" with the "--disable-resources" option you can |
539 | you have run "configure" with the "--disable-resources" option you can |
| 540 | use the `keysym' resource to alter the keystrings associated with |
540 | use the `keysym' resource to alter the keystrings associated with |
| 541 | keysyms. |
541 | keysyms. |
| 542 | |
542 | |
| 543 | Here's an example for a URxvt session started using "rxvt -name URxvt" |
543 | Here's an example for a URxvt session started using "urxvt -name URxvt" |
| 544 | |
544 | |
| 545 | URxvt.keysym.Home: \033[1~ |
545 | URxvt.keysym.Home: \033[1~ |
| 546 | URxvt.keysym.End: \033[4~ |
546 | URxvt.keysym.End: \033[4~ |
| 547 | URxvt.keysym.C-apostrophe: \033<C-'> |
547 | URxvt.keysym.C-apostrophe: \033<C-'> |
| 548 | URxvt.keysym.C-slash: \033<C-/> |
548 | URxvt.keysym.C-slash: \033<C-/> |
| … | |
… | |
| 627 | |
627 | |
| 628 | "tic" outputs some error when compiling the terminfo entry. |
628 | "tic" outputs some error when compiling the terminfo entry. |
| 629 | Most likely it's the empty definition for "enacs=". Just replace it by |
629 | Most likely it's the empty definition for "enacs=". Just replace it by |
| 630 | "enacs=\E[0@" and try again. |
630 | "enacs=\E[0@" and try again. |
| 631 | |
631 | |
| 632 | "bash"'s readline does not work correctly under rxvt. |
632 | "bash"'s readline does not work correctly under urxvt. |
| 633 | See next entry. |
633 | See next entry. |
| 634 | |
634 | |
| 635 | I need a termcap file entry. |
635 | I need a termcap file entry. |
| 636 | One reason you might want this is that some distributions or operating |
636 | One reason you might want this is that some distributions or operating |
| 637 | systems still compile some programs using the long-obsoleted termcap |
637 | systems still compile some programs using the long-obsoleted termcap |
