… | |
… | |
2 | Meta, Features & Commandline Issues |
2 | Meta, Features & Commandline Issues |
3 | My question isn't answered here, can I ask a human? |
3 | My question isn't answered here, can I ask a human? |
4 | Before sending me mail, you could go to IRC: "irc.freenode.net", channel |
4 | Before sending me mail, you could go to IRC: "irc.freenode.net", channel |
5 | "#rxvt-unicode" has some rxvt-unicode enthusiasts that might be |
5 | "#rxvt-unicode" has some rxvt-unicode enthusiasts that might be |
6 | interested in learning about new and exciting problems (but not FAQs :). |
6 | interested in learning about new and exciting problems (but not FAQs :). |
|
|
7 | |
|
|
8 | I use Gentoo, and I have a problem... |
|
|
9 | There are three big problems with Gentoo Linux: first of all, most if |
|
|
10 | not all Gentoo systems are completely broken (missing or mismatched |
|
|
11 | header files, broken compiler etc. are just the tip of the iceberg); |
|
|
12 | secondly, the Gentoo maintainer thinks it is a good idea to add broken |
|
|
13 | patches to the code; and lastly, it should be called Gentoo GNU/Linux. |
|
|
14 | |
|
|
15 | For these reasons, it is impossible to support rxvt-unicode on Gentoo. |
|
|
16 | Problems appearing on Gentoo systems will usually simply be ignored |
|
|
17 | unless they can be reproduced on non-Gentoo systems. |
7 | |
18 | |
8 | Does it support tabs, can I have a tabbed rxvt-unicode? |
19 | 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 |
20 | 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 |
21 | simple tabbed terminal. It is installed by default, so any of these |
11 | should give you tabs: |
22 | should give you tabs: |
… | |
… | |
58 | This tries to create a new terminal, and if fails with exit status 2, |
69 | This tries to create a new terminal, and if fails with exit status 2, |
59 | meaning it couldn't connect to the daemon, it will start the daemon and |
70 | meaning it couldn't connect to the daemon, it will start the daemon and |
60 | re-run the command. Subsequent invocations of the script will re-use the |
71 | re-run the command. Subsequent invocations of the script will re-use the |
61 | existing daemon. |
72 | existing daemon. |
62 | |
73 | |
63 | How do I distinguish whether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc. |
74 | How do I distinguish whether I'm running rxvt-unicode or a regular |
|
|
75 | xterm? I need this to decide about setting colours etc. |
64 | The original rxvt and rxvt-unicode always export the variable |
76 | The original rxvt and rxvt-unicode always export the variable |
65 | "COLORTERM", so you can check and see if that is set. Note that several |
77 | "COLORTERM", so you can check and see if that is set. Note that several |
66 | programs, JED, slrn, Midnight Commander automatically check this |
78 | programs, JED, slrn, Midnight Commander automatically check this |
67 | variable to decide whether or not to use color. |
79 | variable to decide whether or not to use colour. |
68 | |
80 | |
69 | How do I set the correct, full IP address for the DISPLAY variable? |
81 | How do I set the correct, full IP address for the DISPLAY variable? |
70 | If you've compiled rxvt-unicode with DISPLAY_IS_IP and have enabled |
82 | If you've compiled rxvt-unicode with DISPLAY_IS_IP and have enabled |
71 | insecure mode then it is possible to use the following shell script |
83 | insecure mode then it is possible to use the following shell script |
72 | snippets to correctly set the display. If your version of rxvt-unicode |
84 | snippets to correctly set the display. If your version of rxvt-unicode |
… | |
… | |
192 | your picture with gimp or any other tool: |
204 | your picture with gimp or any other tool: |
193 | |
205 | |
194 | convert wallpaper.jpg -blur 20x20 -modulate 30 background.jpg |
206 | convert wallpaper.jpg -blur 20x20 -modulate 30 background.jpg |
195 | urxvt -pixmap "background.jpg;:root" |
207 | urxvt -pixmap "background.jpg;:root" |
196 | |
208 | |
197 | That works. If you think it doesn't, you lack AfterImage support, or you |
209 | That works. If you think it doesn't, you lack libAfterImage or |
198 | are unable to read. |
210 | GDK-PixBuf support, or you are unable to read. |
199 | |
211 | |
200 | 3. Use an ARGB visual: |
212 | 3. Use an ARGB visual: |
201 | |
213 | |
202 | urxvt -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc |
214 | urxvt -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc |
203 | |
215 | |
… | |
… | |
301 | For the standard background colour, blinking will actually make the text |
313 | For the standard background colour, blinking will actually make the text |
302 | blink when compiled with "--enable-text-blink". Without |
314 | blink when compiled with "--enable-text-blink". Without |
303 | "--enable-text-blink", the blink attribute will be ignored. |
315 | "--enable-text-blink", the blink attribute will be ignored. |
304 | |
316 | |
305 | On ANSI colours, bold/blink attributes are used to set high-intensity |
317 | On ANSI colours, bold/blink attributes are used to set high-intensity |
306 | foreground/background colors. |
318 | foreground/background colours. |
307 | |
319 | |
308 | color0-7 are the low-intensity colors. |
320 | color0-7 are the low-intensity colours. |
309 | |
321 | |
310 | color8-15 are the corresponding high-intensity colors. |
322 | color8-15 are the corresponding high-intensity colours. |
311 | |
323 | |
312 | I don't like the screen colors. How do I change them? |
324 | I don't like the screen colours. How do I change them? |
313 | You can change the screen colors at run-time using ~/.Xdefaults |
325 | You can change the screen colours at run-time using ~/.Xdefaults |
314 | resources (or as long-options). |
326 | resources (or as long-options). |
315 | |
327 | |
316 | Here are values that are supposed to resemble a VGA screen, including |
328 | Here are values that are supposed to resemble a VGA screen, including |
317 | the murky brown that passes for low-intensity yellow: |
329 | the murky brown that passes for low-intensity yellow: |
318 | |
330 | |
… | |
… | |
332 | URxvt.color12: #0000FF |
344 | URxvt.color12: #0000FF |
333 | URxvt.color13: #FF00FF |
345 | URxvt.color13: #FF00FF |
334 | URxvt.color14: #00FFFF |
346 | URxvt.color14: #00FFFF |
335 | URxvt.color15: #FFFFFF |
347 | URxvt.color15: #FFFFFF |
336 | |
348 | |
337 | And here is a more complete set of non-standard colors. |
349 | And here is a more complete set of non-standard colours. |
338 | |
350 | |
339 | URxvt.cursorColor: #dc74d1 |
351 | URxvt.cursorColor: #dc74d1 |
340 | URxvt.pointerColor: #dc74d1 |
352 | URxvt.pointerColor: #dc74d1 |
341 | URxvt.background: #0e0e0e |
353 | URxvt.background: #0e0e0e |
342 | URxvt.foreground: #4ad5e1 |
354 | URxvt.foreground: #4ad5e1 |
… | |
… | |
487 | will continue without an input method. |
499 | will continue without an input method. |
488 | |
500 | |
489 | In this case either do not specify a preeditStyle or specify more than |
501 | In this case either do not specify a preeditStyle or specify more than |
490 | one pre-edit style, such as OverTheSpot,Root,None. |
502 | one pre-edit style, such as OverTheSpot,Root,None. |
491 | |
503 | |
|
|
504 | If it still doesn't work, then maybe your input method doesn't support |
|
|
505 | compose sequences - to fall back to the built-in one, make sure you |
|
|
506 | don't specify an input method via "-im" or "XMODIFIERS". |
|
|
507 | |
492 | I cannot type "Ctrl-Shift-2" to get an ASCII NUL character due to ISO 14755 |
508 | I cannot type "Ctrl-Shift-2" to get an ASCII NUL character due to ISO 14755 |
493 | Either try "Ctrl-2" alone (it often is mapped to ASCII NUL even on |
509 | Either try "Ctrl-2" alone (it often is mapped to ASCII NUL even on |
494 | international keyboards) or simply use ISO 14755 support to your |
510 | international keyboards) or simply use ISO 14755 support to your |
495 | advantage, typing <Ctrl-Shift-0> to get a ASCII NUL. This works for |
511 | advantage, typing <Ctrl-Shift-0> to get a ASCII NUL. This works for |
496 | other codes, too, such as "Ctrl-Shift-1-d" to type the default telnet |
512 | other codes, too, such as "Ctrl-Shift-1-d" to type the default telnet |
… | |
… | |
510 | |
526 | |
511 | Historically, either value is correct, but rxvt-unicode adopts the |
527 | Historically, either value is correct, but rxvt-unicode adopts the |
512 | debian policy of using "^?" when unsure, because it's the one and only |
528 | debian policy of using "^?" when unsure, because it's the one and only |
513 | correct choice :). |
529 | correct choice :). |
514 | |
530 | |
515 | Rxvt-unicode tries to inherit the current stty settings and uses the |
531 | It is possible to toggle between "^H" and "^?" with the DECBKM private |
516 | value of `erase' to guess the value for backspace. If rxvt-unicode |
532 | mode: |
517 | wasn't started from a terminal (say, from a menu or by remote shell), |
|
|
518 | then the system value of `erase', which corresponds to CERASE in |
|
|
519 | <termios.h>, will be used (which may not be the same as your stty |
|
|
520 | setting). |
|
|
521 | |
|
|
522 | For starting a new rxvt-unicode: |
|
|
523 | |
533 | |
524 | # use Backspace = ^H |
534 | # use Backspace = ^H |
525 | $ stty erase ^H |
535 | $ stty erase ^H |
526 | $ urxvt |
536 | $ echo -n "^[[?67h" |
527 | |
537 | |
528 | # use Backspace = ^? |
538 | # use Backspace = ^? |
529 | $ stty erase ^? |
539 | $ stty erase ^? |
530 | $ urxvt |
|
|
531 | |
|
|
532 | Toggle with "ESC [ 36 h" / "ESC [ 36 l". |
|
|
533 | |
|
|
534 | For an existing rxvt-unicode: |
|
|
535 | |
|
|
536 | # use Backspace = ^H |
|
|
537 | $ stty erase ^H |
|
|
538 | $ echo -n "^[[36h" |
|
|
539 | |
|
|
540 | # use Backspace = ^? |
|
|
541 | $ stty erase ^? |
|
|
542 | $ echo -n "^[[36l" |
540 | $ echo -n "^[[?67l" |
543 | |
541 | |
544 | This helps satisfy some of the Backspace discrepancies that occur, but |
542 | This helps satisfy some of the Backspace discrepancies that occur, but |
545 | if you use Backspace = "^H", make sure that the termcap/terminfo value |
543 | if you use Backspace = "^H", make sure that the termcap/terminfo value |
546 | properly reflects that. |
544 | properly reflects that. |
547 | |
545 | |
… | |
… | |
635 | develop for myself mostly, so I actually use most of the extensions I |
633 | develop for myself mostly, so I actually use most of the extensions I |
636 | write. |
634 | write. |
637 | |
635 | |
638 | The selection stuff mainly makes the selection perl-error-message aware |
636 | The selection stuff mainly makes the selection perl-error-message aware |
639 | and tells it to convert perl error messages into vi-commands to load the |
637 | and tells it to convert perl error messages into vi-commands to load the |
640 | relevant file and go tot he error line number. |
638 | relevant file and go to the error line number. |
641 | |
639 | |
642 | URxvt.scrollstyle: plain |
640 | URxvt.scrollstyle: plain |
643 | URxvt.secondaryScroll: true |
641 | URxvt.secondaryScroll: true |
644 | |
642 | |
645 | As the documentation says: plain is the preferred scrollbar for the |
643 | As the documentation says: plain is the preferred scrollbar for the |
… | |
… | |
718 | my purposes, it works, and gives a different look, as my normal |
716 | my purposes, it works, and gives a different look, as my normal |
719 | (Non-bold) font is already bold, and I want to see a difference between |
717 | (Non-bold) font is already bold, and I want to see a difference between |
720 | bold and normal fonts. |
718 | bold and normal fonts. |
721 | |
719 | |
722 | Please note that I used the "urxvt" instance name and not the "URxvt" |
720 | Please note that I used the "urxvt" instance name and not the "URxvt" |
723 | class name. Thats because I use different configs for different |
721 | class name. That is because I use different configs for different |
724 | purposes, for example, my IRC window is started with "-name IRC", and |
722 | purposes, for example, my IRC window is started with "-name IRC", and |
725 | uses these defaults: |
723 | uses these defaults: |
726 | |
724 | |
727 | IRC*title: IRC |
725 | IRC*title: IRC |
728 | IRC*geometry: 87x12+535+542 |
726 | IRC*geometry: 87x12+535+542 |
… | |
… | |
732 | IRC*boldFont: suxuseuro |
730 | IRC*boldFont: suxuseuro |
733 | IRC*colorBD: white |
731 | IRC*colorBD: white |
734 | IRC*keysym.M-C-1: command:\033]710;suxuseuro\007\033]711;suxuseuro\007 |
732 | IRC*keysym.M-C-1: command:\033]710;suxuseuro\007\033]711;suxuseuro\007 |
735 | IRC*keysym.M-C-2: command:\033]710;9x15bold\007\033]711;9x15bold\007 |
733 | IRC*keysym.M-C-2: command:\033]710;9x15bold\007\033]711;9x15bold\007 |
736 | |
734 | |
737 | "Alt-Shift-1" and "Alt-Shift-2" switch between two different font sizes. |
735 | "Alt-Ctrl-1" and "Alt-Ctrl-2" switch between two different font sizes. |
738 | "suxuseuro" allows me to keep an eye (and actually read) stuff while |
736 | "suxuseuro" allows me to keep an eye (and actually read) stuff while |
739 | keeping a very small window. If somebody pastes something complicated |
737 | keeping a very small window. If somebody pastes something complicated |
740 | (e.g. japanese), I temporarily switch to a larger font. |
738 | (e.g. japanese), I temporarily switch to a larger font. |
741 | |
739 | |
742 | The above is all in my ".Xdefaults" (I don't use ".Xresources" nor |
740 | The above is all in my ".Xdefaults" (I don't use ".Xresources" nor |
743 | "xrdb"). I also have some resources in a separate ".Xdefaults-hostname" |
741 | "xrdb"). I also have some resources in a separate ".Xdefaults-hostname" |
744 | file for different hosts, for example, on ym main desktop, I use: |
742 | file for different hosts, for example, on my main desktop, I use: |
745 | |
743 | |
746 | URxvt.keysym.C-M-q: command:\033[3;5;5t |
744 | URxvt.keysym.C-M-q: command:\033[3;5;5t |
747 | URxvt.keysym.C-M-y: command:\033[3;5;606t |
745 | URxvt.keysym.C-M-y: command:\033[3;5;606t |
748 | URxvt.keysym.C-M-e: command:\033[3;1605;5t |
746 | URxvt.keysym.C-M-e: command:\033[3;1605;5t |
749 | URxvt.keysym.C-M-c: command:\033[3;1605;606t |
747 | URxvt.keysym.C-M-c: command:\033[3;1605;606t |
… | |
… | |
778 | The terminal description used by rxvt-unicode is not as widely available |
776 | The terminal description used by rxvt-unicode is not as widely available |
779 | as that for xterm, or even rxvt (for which the same problem often |
777 | as that for xterm, or even rxvt (for which the same problem often |
780 | arises). |
778 | arises). |
781 | |
779 | |
782 | The correct solution for this problem is to install the terminfo, this |
780 | The correct solution for this problem is to install the terminfo, this |
783 | can be done like this (with ncurses' infocmp and works as user and |
781 | can be done by simply installing rxvt-unicode on the remote system as |
784 | admin): |
782 | well (in case you have a nice package manager ready), or you can install |
|
|
783 | the terminfo database manually like this (with ncurses infocmp. works as |
|
|
784 | user and root): |
785 | |
785 | |
786 | REMOTE=remotesystem.domain |
786 | REMOTE=remotesystem.domain |
787 | infocmp rxvt-unicode | ssh $REMOTE "mkdir -p .terminfo && cat >/tmp/ti && tic /tmp/ti" |
787 | infocmp rxvt-unicode | ssh $REMOTE "mkdir -p .terminfo && cat >/tmp/ti && tic /tmp/ti" |
788 | |
|
|
789 | ... or by installing rxvt-unicode normally on the remote system, |
|
|
790 | |
788 | |
791 | One some systems you might need to set $TERMINFO to the full path of |
789 | One some systems you might need to set $TERMINFO to the full path of |
792 | $HOME/.terminfo for this to work. |
790 | $HOME/.terminfo for this to work. |
793 | |
791 | |
794 | If you cannot or do not want to do this, then you can simply set |
792 | If you cannot or do not want to do this, then you can simply set |
… | |
… | |
803 | |
801 | |
804 | URxvt.termName: rxvt |
802 | URxvt.termName: rxvt |
805 | |
803 | |
806 | If you don't plan to use rxvt (quite common...) you could also replace |
804 | If you don't plan to use rxvt (quite common...) you could also replace |
807 | the rxvt terminfo file with the rxvt-unicode one and use "TERM=rxvt". |
805 | the rxvt terminfo file with the rxvt-unicode one and use "TERM=rxvt". |
|
|
806 | |
|
|
807 | nano fails with "Error opening terminal: rxvt-unicode" |
|
|
808 | This exceptionally confusing and useless error message is printed by |
|
|
809 | nano when it can't find the terminfo database. Nothing is wrong with |
|
|
810 | your terminal, read the previous answer for a solution. |
808 | |
811 | |
809 | "tic" outputs some error when compiling the terminfo entry. |
812 | "tic" outputs some error when compiling the terminfo entry. |
810 | Most likely it's the empty definition for "enacs=". Just replace it by |
813 | Most likely it's the empty definition for "enacs=". Just replace it by |
811 | "enacs=\E[0@" and try again. |
814 | "enacs=\E[0@" and try again. |
812 | |
815 | |
… | |
… | |
1018 | runtime-switchable, too, so there is usually no drawback to enabling |
1021 | runtime-switchable, too, so there is usually no drawback to enabling |
1019 | them, except higher disk and possibly memory usage. The perl interpreter |
1022 | them, except higher disk and possibly memory usage. The perl interpreter |
1020 | should be enabled, as important functionality (menus, selection, likely |
1023 | should be enabled, as important functionality (menus, selection, likely |
1021 | more in the future) depends on it. |
1024 | more in the future) depends on it. |
1022 | |
1025 | |
1023 | You should not overwrite the "perl-ext-common" snd "perl-ext" resources |
1026 | You should not overwrite the "perl-ext-common" and "perl-ext" resources |
1024 | system-wide (except maybe with "defaults"). This will result in useful |
1027 | system-wide (except maybe with "defaults"). This will result in useful |
1025 | behaviour. If your distribution aims at low memory, add an empty |
1028 | behaviour. If your distribution aims at low memory, add an empty |
1026 | "perl-ext-common" resource to the app-defaults file. This will keep the |
1029 | "perl-ext-common" resource to the app-defaults file. This will keep the |
1027 | perl interpreter disabled until the user enables it. |
1030 | perl interpreter disabled until the user enables it. |
1028 | |
1031 | |