| … | |
… | |
| 58 | This tries to create a new terminal, and if fails with exit status 2, |
58 | 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 |
59 | 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 |
60 | re-run the command. Subsequent invocations of the script will re-use the |
| 61 | existing daemon. |
61 | existing daemon. |
| 62 | |
62 | |
| 63 | How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc. |
63 | How do I distinguish whether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc. |
| 64 | The original rxvt and rxvt-unicode always export the variable |
64 | 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 |
65 | "COLORTERM", so you can check and see if that is set. Note that several |
| 66 | programs, JED, slrn, Midnight Commander automatically check this |
66 | programs, JED, slrn, Midnight Commander automatically check this |
| 67 | variable to decide whether or not to use color. |
67 | variable to decide whether or not to use color. |
| 68 | |
68 | |
| … | |
… | |
| 108 | 98398 1664 24 15695 1824 rxvt --disable-everything |
108 | 98398 1664 24 15695 1824 rxvt --disable-everything |
| 109 | 188985 9048 66616 18222 1788 urxvt --disable-everything |
109 | 188985 9048 66616 18222 1788 urxvt --disable-everything |
| 110 | |
110 | |
| 111 | When you "--enable-everything" (which *is* unfair, as this involves xft |
111 | When you "--enable-everything" (which *is* unfair, as this involves xft |
| 112 | and full locale/XIM support which are quite bloaty inside libX11 and my |
112 | and full locale/XIM support which are quite bloaty inside libX11 and my |
| 113 | libc), the two diverge, but not unreasnobaly so. |
113 | libc), the two diverge, but not unreasonably so. |
| 114 | |
114 | |
| 115 | text data bss drs rss filename |
115 | text data bss drs rss filename |
| 116 | 163431 2152 24 20123 2060 rxvt --enable-everything |
116 | 163431 2152 24 20123 2060 rxvt --enable-everything |
| 117 | 1035683 49680 66648 29096 3680 urxvt --enable-everything |
117 | 1035683 49680 66648 29096 3680 urxvt --enable-everything |
| 118 | |
118 | |
| … | |
… | |
| 202 | urxvt -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc |
202 | urxvt -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc |
| 203 | |
203 | |
| 204 | This requires XFT support, and the support of your X-server. If that |
204 | This requires XFT support, and the support of your X-server. If that |
| 205 | doesn't work for you, blame Xorg and Keith Packard. ARGB visuals aren't |
205 | doesn't work for you, blame Xorg and Keith Packard. ARGB visuals aren't |
| 206 | there yet, no matter what they claim. Rxvt-Unicode contains the |
206 | there yet, no matter what they claim. Rxvt-Unicode contains the |
| 207 | neccessary bugfixes and workarounds for Xft and Xlib to make it work, |
207 | necessary bugfixes and workarounds for Xft and Xlib to make it work, but |
| 208 | but that doesn't mean that your WM has the required kludges in place. |
208 | that doesn't mean that your WM has the required kludges in place. |
| 209 | |
209 | |
| 210 | 4. Use xcompmgr and let it do the job: |
210 | 4. Use xcompmgr and let it do the job: |
| 211 | |
211 | |
| 212 | xprop -frame -f _NET_WM_WINDOW_OPACITY 32c \ |
212 | xprop -frame -f _NET_WM_WINDOW_OPACITY 32c \ |
| 213 | -set _NET_WM_WINDOW_OPACITY 0xc0000000 |
213 | -set _NET_WM_WINDOW_OPACITY 0xc0000000 |
| … | |
… | |
| 228 | however: Xft fonts often draw glyphs larger than their acclaimed |
228 | however: Xft fonts often draw glyphs larger than their acclaimed |
| 229 | bounding box, and rxvt-unicode has no way of detecting this (the correct |
229 | bounding box, and rxvt-unicode has no way of detecting this (the correct |
| 230 | way is to ask for the character bounding box, which unfortunately is |
230 | way is to ask for the character bounding box, which unfortunately is |
| 231 | wrong in these cases). |
231 | wrong in these cases). |
| 232 | |
232 | |
| 233 | It's not clear (to me at least), wether this is a bug in Xft, freetype, |
233 | It's not clear (to me at least), whether this is a bug in Xft, freetype, |
| 234 | or the respective font. If you encounter this problem you might try |
234 | or the respective font. If you encounter this problem you might try |
| 235 | using the "-lsp" option to give the font more height. If that doesn't |
235 | using the "-lsp" option to give the font more height. If that doesn't |
| 236 | work, you might be forced to use a different font. |
236 | work, you might be forced to use a different font. |
| 237 | |
237 | |
| 238 | All of this is not a problem when using X11 core fonts, as their |
238 | All of this is not a problem when using X11 core fonts, as their |
| … | |
… | |
| 457 | circumstances, it will move your cursor around when you click into the |
457 | circumstances, it will move your cursor around when you click into the |
| 458 | line that contains it. It tries hard not to do this at the wrong moment, |
458 | line that contains it. It tries hard not to do this at the wrong moment, |
| 459 | but when running a program that doesn't parse cursor movements or in |
459 | but when running a program that doesn't parse cursor movements or in |
| 460 | some cases during rlogin sessions, it fails to detect this properly. |
460 | some cases during rlogin sessions, it fails to detect this properly. |
| 461 | |
461 | |
| 462 | You can permamently switch this feature off by disabling the "readline" |
462 | You can permanently switch this feature off by disabling the "readline" |
| 463 | extension: |
463 | extension: |
| 464 | |
464 | |
| 465 | URxvt.perl-ext-common: default,-readline |
465 | URxvt.perl-ext-common: default,-readline |
| 466 | |
466 | |
| 467 | My numerical keypad acts weird and generates differing output? |
467 | My numerical keypad acts weird and generates differing output? |
| 468 | Some Debian GNUL/Linux users seem to have this problem, although no |
468 | Some Debian GNUL/Linux users seem to have this problem, although no |
| 469 | specific details were reported so far. It is possible that this is |
469 | specific details were reported so far. It is possible that this is |
| 470 | caused by the wrong "TERM" setting, although the details of wether and |
470 | caused by the wrong "TERM" setting, although the details of whether and |
| 471 | how this can happen are unknown, as "TERM=rxvt" should offer a |
471 | how this can happen are unknown, as "TERM=rxvt" should offer a |
| 472 | compatible keymap. See the answer to the previous question, and please |
472 | compatible keymap. See the answer to the previous question, and please |
| 473 | report if that helped. |
473 | report if that helped. |
| 474 | |
474 | |
| 475 | My Compose (Multi_key) key is no longer working. |
475 | My Compose (Multi_key) key is no longer working. |
| … | |
… | |
| 496 | that tcsh may use mouse reporting unless it otherwise specified. A quick |
496 | that tcsh may use mouse reporting unless it otherwise specified. A quick |
| 497 | check is to see if cut/paste works when the Alt or Shift keys are |
497 | check is to see if cut/paste works when the Alt or Shift keys are |
| 498 | depressed. |
498 | depressed. |
| 499 | |
499 | |
| 500 | What's with the strange Backspace/Delete key behaviour? |
500 | What's with the strange Backspace/Delete key behaviour? |
| 501 | Assuming that the physical Backspace key corresponds to the BackSpace |
501 | Assuming that the physical Backspace key corresponds to the Backspace |
| 502 | keysym (not likely for Linux ... see the following question) there are |
502 | keysym (not likely for Linux ... see the following question) there are |
| 503 | two standard values that can be used for Backspace: "^H" and "^?". |
503 | two standard values that can be used for Backspace: "^H" and "^?". |
| 504 | |
504 | |
| 505 | Historically, either value is correct, but rxvt-unicode adopts the |
505 | Historically, either value is correct, but rxvt-unicode adopts the |
| 506 | debian policy of using "^?" when unsure, because it's the one only only |
506 | debian policy of using "^?" when unsure, because it's the one only only |
| … | |
… | |
| 628 | directory and also tells urxvt to use a large number of extensions. I |
628 | directory and also tells urxvt to use a large number of extensions. I |
| 629 | develop for myself mostly, so I actually use most of the extensions I |
629 | develop for myself mostly, so I actually use most of the extensions I |
| 630 | write. |
630 | write. |
| 631 | |
631 | |
| 632 | The selection stuff mainly makes the selection perl-error-message aware |
632 | The selection stuff mainly makes the selection perl-error-message aware |
| 633 | and tells it to convert pelr error mssages into vi-commands to load the |
633 | and tells it to convert perl error messages into vi-commands to load the |
| 634 | relevant file and go tot he error line number. |
634 | relevant file and go tot he error line number. |
| 635 | |
635 | |
| 636 | URxvt.scrollstyle: plain |
636 | URxvt.scrollstyle: plain |
| 637 | URxvt.secondaryScroll: true |
637 | URxvt.secondaryScroll: true |
| 638 | |
638 | |
| 639 | As the documentation says: plain is the preferred scrollbar for the |
639 | As the documentation says: plain is the preferred scrollbar for the |
| 640 | author. The "secondaryScroll" confgiures urxvt to scroll in full-screen |
640 | author. The "secondaryScroll" configures urxvt to scroll in full-screen |
| 641 | apps, like screen, so lines scorlled out of screen end up in urxvt's |
641 | apps, like screen, so lines scrolled out of screen end up in urxvt's |
| 642 | scrollback buffer. |
642 | scrollback buffer. |
| 643 | |
643 | |
| 644 | URxvt.background: #000000 |
644 | URxvt.background: #000000 |
| 645 | URxvt.foreground: gray90 |
645 | URxvt.foreground: gray90 |
| 646 | URxvt.color7: gray90 |
646 | URxvt.color7: gray90 |
| … | |
… | |
| 697 | urxvt.boldFont: -xos4-terminus-bold-r-normal--14-140-72-72-c-80-iso8859-15 |
697 | urxvt.boldFont: -xos4-terminus-bold-r-normal--14-140-72-72-c-80-iso8859-15 |
| 698 | urxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true |
698 | urxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true |
| 699 | urxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true |
699 | urxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true |
| 700 | |
700 | |
| 701 | I wrote rxvt-unicode to be able to specify fonts exactly. So don't be |
701 | I wrote rxvt-unicode to be able to specify fonts exactly. So don't be |
| 702 | overwhelmed. A special note: the "9x15bold" mentioend above is actually |
702 | overwhelmed. A special note: the "9x15bold" mentioned above is actually |
| 703 | the version from XFree-3.3, as XFree-4 replaced it by a totally |
703 | the version from XFree-3.3, as XFree-4 replaced it by a totally |
| 704 | different font (different glyphs for ";" and many other harmless |
704 | different font (different glyphs for ";" and many other harmless |
| 705 | characters), while the second font is actually the "9x15bold" from |
705 | characters), while the second font is actually the "9x15bold" from |
| 706 | XFree4/XOrg. The bold version has less chars than the medium version, so |
706 | XFree4/XOrg. The bold version has less chars than the medium version, so |
| 707 | I use it for rare characters, too. Whene ditign sources with vim, I use |
707 | I use it for rare characters, too. When editing sources with vim, I use |
| 708 | italic for comments and other stuff, which looks quite good with |
708 | italic for comments and other stuff, which looks quite good with |
| 709 | Bitstream Vera anti-aliased. |
709 | Bitstream Vera anti-aliased. |
| 710 | |
710 | |
| 711 | Terminus is a quite bad font (many very wrong glyphs), but for most of |
711 | Terminus is a quite bad font (many very wrong glyphs), but for most of |
| 712 | my purposes, it works, and gives a different look, as my normal |
712 | my purposes, it works, and gives a different look, as my normal |
| … | |
… | |
| 763 | Also consider the form resources have to use: |
763 | Also consider the form resources have to use: |
| 764 | |
764 | |
| 765 | URxvt.resource: value |
765 | URxvt.resource: value |
| 766 | |
766 | |
| 767 | If you want to use another form (there are lots of different ways of |
767 | If you want to use another form (there are lots of different ways of |
| 768 | specifying resources), make sure you understand wether and why it works. |
768 | specifying resources), make sure you understand whether and why it |
| 769 | If unsure, use the form above. |
769 | works. If unsure, use the form above. |
| 770 | |
770 | |
| 771 | When I log-in to another system it tells me about missing terminfo data? |
771 | When I log-in to another system it tells me about missing terminfo data? |
| 772 | The terminal description used by rxvt-unicode is not as widely available |
772 | The terminal description used by rxvt-unicode is not as widely available |
| 773 | as that for xterm, or even rxvt (for which the same problem often |
773 | as that for xterm, or even rxvt (for which the same problem often |
| 774 | arises). |
774 | arises). |
| … | |
… | |
| 807 | One reason you might want this is that some distributions or operating |
807 | One reason you might want this is that some distributions or operating |
| 808 | systems still compile some programs using the long-obsoleted termcap |
808 | systems still compile some programs using the long-obsoleted termcap |
| 809 | library (Fedora Core's bash is one example) and rely on a termcap entry |
809 | library (Fedora Core's bash is one example) and rely on a termcap entry |
| 810 | for "rxvt-unicode". |
810 | for "rxvt-unicode". |
| 811 | |
811 | |
| 812 | You could use rxvt's termcap entry with resonable results in many cases. |
812 | You could use rxvt's termcap entry with reasonable results in many |
| 813 | You can also create a termcap entry by using terminfo's infocmp program |
813 | cases. You can also create a termcap entry by using terminfo's infocmp |
| 814 | like this: |
814 | program like this: |
| 815 | |
815 | |
| 816 | infocmp -C rxvt-unicode |
816 | infocmp -C rxvt-unicode |
| 817 | |
817 | |
| 818 | Or you could use this termcap entry, generated by the command above: |
818 | Or you could use this termcap entry, generated by the command above: |
| 819 | |
819 | |
| … | |
… | |
| 838 | :us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\ |
838 | :us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\ |
| 839 | :vs=\E[?25h: |
839 | :vs=\E[?25h: |
| 840 | |
840 | |
| 841 | Why does "ls" no longer have coloured output? |
841 | Why does "ls" no longer have coloured output? |
| 842 | The "ls" in the GNU coreutils unfortunately doesn't use terminfo to |
842 | The "ls" in the GNU coreutils unfortunately doesn't use terminfo to |
| 843 | decide wether a terminal has colour, but uses its own configuration |
843 | decide whether a terminal has colour, but uses its own configuration |
| 844 | file. Needless to say, "rxvt-unicode" is not in its default file (among |
844 | file. Needless to say, "rxvt-unicode" is not in its default file (among |
| 845 | with most other terminals supporting colour). Either add: |
845 | with most other terminals supporting colour). Either add: |
| 846 | |
846 | |
| 847 | TERM rxvt-unicode |
847 | TERM rxvt-unicode |
| 848 | |
848 | |
| … | |
… | |
| 976 | |
976 | |
| 977 | - Make sure your XIM server is actually running. |
977 | - Make sure your XIM server is actually running. |
| 978 | - Make sure the "XMODIFIERS" environment variable is set correctly when |
978 | - Make sure the "XMODIFIERS" environment variable is set correctly when |
| 979 | *starting* rxvt-unicode. |
979 | *starting* rxvt-unicode. |
| 980 | When you want to use e.g. kinput2, it must be set to "@im=kinput2". |
980 | When you want to use e.g. kinput2, it must be set to "@im=kinput2". |
| 981 | For scim, use "@im=SCIM". Youc an see what input method servers are |
981 | For scim, use "@im=SCIM". You can see what input method servers are |
| 982 | running with this command: |
982 | running with this command: |
| 983 | |
983 | |
| 984 | xprop -root XIM_SERVERS |
984 | xprop -root XIM_SERVERS |
| 985 | |
985 | |
| 986 | |
986 | |
| … | |
… | |
| 1023 | that might encounter the same issue. |
1023 | that might encounter the same issue. |
| 1024 | |
1024 | |
| 1025 | I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation? |
1025 | I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation? |
| 1026 | You should build one binary with the default options. configure now |
1026 | You should build one binary with the default options. configure now |
| 1027 | enables most useful options, and the trend goes to making them |
1027 | enables most useful options, and the trend goes to making them |
| 1028 | runtime-switchable, too, so there is usually no drawback to enbaling |
1028 | runtime-switchable, too, so there is usually no drawback to enabling |
| 1029 | them, except higher disk and possibly memory usage. The perl interpreter |
1029 | them, except higher disk and possibly memory usage. The perl interpreter |
| 1030 | should be enabled, as important functionality (menus, selection, likely |
1030 | should be enabled, as important functionality (menus, selection, likely |
| 1031 | more in the future) depends on it. |
1031 | more in the future) depends on it. |
| 1032 | |
1032 | |
| 1033 | You should not overwrite the "perl-ext-common" snd "perl-ext" resources |
1033 | You should not overwrite the "perl-ext-common" snd "perl-ext" resources |
| … | |
… | |
| 1065 | #define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x) |
1065 | #define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x) |
| 1066 | |
1066 | |
| 1067 | I am on FreeBSD and rxvt-unicode does not seem to work at all. |
1067 | I am on FreeBSD and rxvt-unicode does not seem to work at all. |
| 1068 | Rxvt-unicode requires the symbol "__STDC_ISO_10646__" to be defined in |
1068 | Rxvt-unicode requires the symbol "__STDC_ISO_10646__" to be defined in |
| 1069 | your compile environment, or an implementation that implements it, |
1069 | your compile environment, or an implementation that implements it, |
| 1070 | wether it defines the symbol or not. "__STDC_ISO_10646__" requires that |
1070 | whether it defines the symbol or not. "__STDC_ISO_10646__" requires that |
| 1071 | wchar_t is represented as unicode. |
1071 | wchar_t is represented as unicode. |
| 1072 | |
1072 | |
| 1073 | As you might have guessed, FreeBSD does neither define this symobl nor |
1073 | As you might have guessed, FreeBSD does neither define this symbol nor |
| 1074 | does it support it. Instead, it uses its own internal representation of |
1074 | does it support it. Instead, it uses its own internal representation of |
| 1075 | wchar_t. This is, of course, completely fine with respect to standards. |
1075 | wchar_t. This is, of course, completely fine with respect to standards. |
| 1076 | |
1076 | |
| 1077 | However, that means rxvt-unicode only works in "POSIX", "ISO-8859-1" and |
1077 | However, that means rxvt-unicode only works in "POSIX", "ISO-8859-1" and |
| 1078 | "UTF-8" locales under FreeBSD (which all use Unicode as wchar_t. |
1078 | "UTF-8" locales under FreeBSD (which all use Unicode as wchar_t. |
