| … | |
… | |
| 79 | This tries to create a new terminal, and if fails with exit status 2, |
79 | This tries to create a new terminal, and if fails with exit status 2, |
| 80 | meaning it couldn't connect to the daemon, it will start the daemon and |
80 | meaning it couldn't connect to the daemon, it will start the daemon and |
| 81 | re-run the command. Subsequent invocations of the script will re-use the |
81 | re-run the command. Subsequent invocations of the script will re-use the |
| 82 | existing daemon. |
82 | existing daemon. |
| 83 | |
83 | |
| 84 | How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc. |
84 | How do I distinguish whether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc. |
| 85 | The original rxvt and rxvt-unicode always export the variable |
85 | The original rxvt and rxvt-unicode always export the variable |
| 86 | "COLORTERM", so you can check and see if that is set. Note that several |
86 | "COLORTERM", so you can check and see if that is set. Note that several |
| 87 | programs, JED, slrn, Midnight Commander automatically check this |
87 | programs, JED, slrn, Midnight Commander automatically check this |
| 88 | variable to decide whether or not to use color. |
88 | variable to decide whether or not to use color. |
| 89 | |
89 | |
| … | |
… | |
| 129 | 98398 1664 24 15695 1824 rxvt --disable-everything |
129 | 98398 1664 24 15695 1824 rxvt --disable-everything |
| 130 | 188985 9048 66616 18222 1788 urxvt --disable-everything |
130 | 188985 9048 66616 18222 1788 urxvt --disable-everything |
| 131 | |
131 | |
| 132 | When you "--enable-everything" (which *is* unfair, as this involves xft |
132 | When you "--enable-everything" (which *is* unfair, as this involves xft |
| 133 | and full locale/XIM support which are quite bloaty inside libX11 and my |
133 | and full locale/XIM support which are quite bloaty inside libX11 and my |
| 134 | libc), the two diverge, but not unreasnobaly so. |
134 | libc), the two diverge, but not unreasonably so. |
| 135 | |
135 | |
| 136 | text data bss drs rss filename |
136 | text data bss drs rss filename |
| 137 | 163431 2152 24 20123 2060 rxvt --enable-everything |
137 | 163431 2152 24 20123 2060 rxvt --enable-everything |
| 138 | 1035683 49680 66648 29096 3680 urxvt --enable-everything |
138 | 1035683 49680 66648 29096 3680 urxvt --enable-everything |
| 139 | |
139 | |
| … | |
… | |
| 223 | urxvt -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc |
223 | urxvt -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc |
| 224 | |
224 | |
| 225 | This requires XFT support, and the support of your X-server. If that |
225 | This requires XFT support, and the support of your X-server. If that |
| 226 | doesn't work for you, blame Xorg and Keith Packard. ARGB visuals aren't |
226 | doesn't work for you, blame Xorg and Keith Packard. ARGB visuals aren't |
| 227 | there yet, no matter what they claim. Rxvt-Unicode contains the |
227 | there yet, no matter what they claim. Rxvt-Unicode contains the |
| 228 | neccessary bugfixes and workarounds for Xft and Xlib to make it work, |
228 | necessary bugfixes and workarounds for Xft and Xlib to make it work, but |
| 229 | but that doesn't mean that your WM has the required kludges in place. |
229 | that doesn't mean that your WM has the required kludges in place. |
| 230 | |
230 | |
| 231 | 4. Use xcompmgr and let it do the job: |
231 | 4. Use xcompmgr and let it do the job: |
| 232 | |
232 | |
| 233 | xprop -frame -f _NET_WM_WINDOW_OPACITY 32c \ |
233 | xprop -frame -f _NET_WM_WINDOW_OPACITY 32c \ |
| 234 | -set _NET_WM_WINDOW_OPACITY 0xc0000000 |
234 | -set _NET_WM_WINDOW_OPACITY 0xc0000000 |
| … | |
… | |
| 249 | however: Xft fonts often draw glyphs larger than their acclaimed |
249 | however: Xft fonts often draw glyphs larger than their acclaimed |
| 250 | bounding box, and rxvt-unicode has no way of detecting this (the correct |
250 | bounding box, and rxvt-unicode has no way of detecting this (the correct |
| 251 | way is to ask for the character bounding box, which unfortunately is |
251 | way is to ask for the character bounding box, which unfortunately is |
| 252 | wrong in these cases). |
252 | wrong in these cases). |
| 253 | |
253 | |
| 254 | It's not clear (to me at least), wether this is a bug in Xft, freetype, |
254 | It's not clear (to me at least), whether this is a bug in Xft, freetype, |
| 255 | or the respective font. If you encounter this problem you might try |
255 | or the respective font. If you encounter this problem you might try |
| 256 | using the "-lsp" option to give the font more height. If that doesn't |
256 | using the "-lsp" option to give the font more height. If that doesn't |
| 257 | work, you might be forced to use a different font. |
257 | work, you might be forced to use a different font. |
| 258 | |
258 | |
| 259 | All of this is not a problem when using X11 core fonts, as their |
259 | All of this is not a problem when using X11 core fonts, as their |
| … | |
… | |
| 478 | circumstances, it will move your cursor around when you click into the |
478 | circumstances, it will move your cursor around when you click into the |
| 479 | line that contains it. It tries hard not to do this at the wrong moment, |
479 | line that contains it. It tries hard not to do this at the wrong moment, |
| 480 | but when running a program that doesn't parse cursor movements or in |
480 | but when running a program that doesn't parse cursor movements or in |
| 481 | some cases during rlogin sessions, it fails to detect this properly. |
481 | some cases during rlogin sessions, it fails to detect this properly. |
| 482 | |
482 | |
| 483 | You can permamently switch this feature off by disabling the "readline" |
483 | You can permanently switch this feature off by disabling the "readline" |
| 484 | extension: |
484 | extension: |
| 485 | |
485 | |
| 486 | URxvt.perl-ext-common: default,-readline |
486 | URxvt.perl-ext-common: default,-readline |
| 487 | |
487 | |
| 488 | My numerical keypad acts weird and generates differing output? |
488 | My numerical keypad acts weird and generates differing output? |
| 489 | Some Debian GNUL/Linux users seem to have this problem, although no |
489 | Some Debian GNUL/Linux users seem to have this problem, although no |
| 490 | specific details were reported so far. It is possible that this is |
490 | specific details were reported so far. It is possible that this is |
| 491 | caused by the wrong "TERM" setting, although the details of wether and |
491 | caused by the wrong "TERM" setting, although the details of whether and |
| 492 | how this can happen are unknown, as "TERM=rxvt" should offer a |
492 | how this can happen are unknown, as "TERM=rxvt" should offer a |
| 493 | compatible keymap. See the answer to the previous question, and please |
493 | compatible keymap. See the answer to the previous question, and please |
| 494 | report if that helped. |
494 | report if that helped. |
| 495 | |
495 | |
| 496 | My Compose (Multi_key) key is no longer working. |
496 | My Compose (Multi_key) key is no longer working. |
| … | |
… | |
| 517 | that tcsh may use mouse reporting unless it otherwise specified. A quick |
517 | that tcsh may use mouse reporting unless it otherwise specified. A quick |
| 518 | check is to see if cut/paste works when the Alt or Shift keys are |
518 | check is to see if cut/paste works when the Alt or Shift keys are |
| 519 | depressed. |
519 | depressed. |
| 520 | |
520 | |
| 521 | What's with the strange Backspace/Delete key behaviour? |
521 | What's with the strange Backspace/Delete key behaviour? |
| 522 | Assuming that the physical Backspace key corresponds to the BackSpace |
522 | Assuming that the physical Backspace key corresponds to the Backspace |
| 523 | keysym (not likely for Linux ... see the following question) there are |
523 | keysym (not likely for Linux ... see the following question) there are |
| 524 | two standard values that can be used for Backspace: "^H" and "^?". |
524 | two standard values that can be used for Backspace: "^H" and "^?". |
| 525 | |
525 | |
| 526 | Historically, either value is correct, but rxvt-unicode adopts the |
526 | Historically, either value is correct, but rxvt-unicode adopts the |
| 527 | debian policy of using "^?" when unsure, because it's the one only only |
527 | debian policy of using "^?" when unsure, because it's the one only only |
| … | |
… | |
| 649 | directory and also tells urxvt to use a large number of extensions. I |
649 | directory and also tells urxvt to use a large number of extensions. I |
| 650 | develop for myself mostly, so I actually use most of the extensions I |
650 | develop for myself mostly, so I actually use most of the extensions I |
| 651 | write. |
651 | write. |
| 652 | |
652 | |
| 653 | The selection stuff mainly makes the selection perl-error-message aware |
653 | The selection stuff mainly makes the selection perl-error-message aware |
| 654 | and tells it to convert pelr error mssages into vi-commands to load the |
654 | and tells it to convert perl error messages into vi-commands to load the |
| 655 | relevant file and go tot he error line number. |
655 | relevant file and go tot he error line number. |
| 656 | |
656 | |
| 657 | URxvt.scrollstyle: plain |
657 | URxvt.scrollstyle: plain |
| 658 | URxvt.secondaryScroll: true |
658 | URxvt.secondaryScroll: true |
| 659 | |
659 | |
| 660 | As the documentation says: plain is the preferred scrollbar for the |
660 | As the documentation says: plain is the preferred scrollbar for the |
| 661 | author. The "secondaryScroll" confgiures urxvt to scroll in full-screen |
661 | author. The "secondaryScroll" configures urxvt to scroll in full-screen |
| 662 | apps, like screen, so lines scorlled out of screen end up in urxvt's |
662 | apps, like screen, so lines scrolled out of screen end up in urxvt's |
| 663 | scrollback buffer. |
663 | scrollback buffer. |
| 664 | |
664 | |
| 665 | URxvt.background: #000000 |
665 | URxvt.background: #000000 |
| 666 | URxvt.foreground: gray90 |
666 | URxvt.foreground: gray90 |
| 667 | URxvt.color7: gray90 |
667 | URxvt.color7: gray90 |
| … | |
… | |
| 718 | urxvt.boldFont: -xos4-terminus-bold-r-normal--14-140-72-72-c-80-iso8859-15 |
718 | urxvt.boldFont: -xos4-terminus-bold-r-normal--14-140-72-72-c-80-iso8859-15 |
| 719 | urxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true |
719 | urxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true |
| 720 | urxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true |
720 | urxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true |
| 721 | |
721 | |
| 722 | I wrote rxvt-unicode to be able to specify fonts exactly. So don't be |
722 | I wrote rxvt-unicode to be able to specify fonts exactly. So don't be |
| 723 | overwhelmed. A special note: the "9x15bold" mentioend above is actually |
723 | overwhelmed. A special note: the "9x15bold" mentioned above is actually |
| 724 | the version from XFree-3.3, as XFree-4 replaced it by a totally |
724 | the version from XFree-3.3, as XFree-4 replaced it by a totally |
| 725 | different font (different glyphs for ";" and many other harmless |
725 | different font (different glyphs for ";" and many other harmless |
| 726 | characters), while the second font is actually the "9x15bold" from |
726 | characters), while the second font is actually the "9x15bold" from |
| 727 | XFree4/XOrg. The bold version has less chars than the medium version, so |
727 | XFree4/XOrg. The bold version has less chars than the medium version, so |
| 728 | I use it for rare characters, too. Whene ditign sources with vim, I use |
728 | I use it for rare characters, too. When editing sources with vim, I use |
| 729 | italic for comments and other stuff, which looks quite good with |
729 | italic for comments and other stuff, which looks quite good with |
| 730 | Bitstream Vera anti-aliased. |
730 | Bitstream Vera anti-aliased. |
| 731 | |
731 | |
| 732 | Terminus is a quite bad font (many very wrong glyphs), but for most of |
732 | Terminus is a quite bad font (many very wrong glyphs), but for most of |
| 733 | my purposes, it works, and gives a different look, as my normal |
733 | my purposes, it works, and gives a different look, as my normal |
| … | |
… | |
| 784 | Also consider the form resources have to use: |
784 | Also consider the form resources have to use: |
| 785 | |
785 | |
| 786 | URxvt.resource: value |
786 | URxvt.resource: value |
| 787 | |
787 | |
| 788 | If you want to use another form (there are lots of different ways of |
788 | If you want to use another form (there are lots of different ways of |
| 789 | specifying resources), make sure you understand wether and why it works. |
789 | specifying resources), make sure you understand whether and why it |
| 790 | If unsure, use the form above. |
790 | works. If unsure, use the form above. |
| 791 | |
791 | |
| 792 | When I log-in to another system it tells me about missing terminfo data? |
792 | When I log-in to another system it tells me about missing terminfo data? |
| 793 | The terminal description used by rxvt-unicode is not as widely available |
793 | The terminal description used by rxvt-unicode is not as widely available |
| 794 | as that for xterm, or even rxvt (for which the same problem often |
794 | as that for xterm, or even rxvt (for which the same problem often |
| 795 | arises). |
795 | arises). |
| … | |
… | |
| 828 | One reason you might want this is that some distributions or operating |
828 | One reason you might want this is that some distributions or operating |
| 829 | systems still compile some programs using the long-obsoleted termcap |
829 | systems still compile some programs using the long-obsoleted termcap |
| 830 | library (Fedora Core's bash is one example) and rely on a termcap entry |
830 | library (Fedora Core's bash is one example) and rely on a termcap entry |
| 831 | for "rxvt-unicode". |
831 | for "rxvt-unicode". |
| 832 | |
832 | |
| 833 | You could use rxvt's termcap entry with resonable results in many cases. |
833 | You could use rxvt's termcap entry with reasonable results in many |
| 834 | You can also create a termcap entry by using terminfo's infocmp program |
834 | cases. You can also create a termcap entry by using terminfo's infocmp |
| 835 | like this: |
835 | program like this: |
| 836 | |
836 | |
| 837 | infocmp -C rxvt-unicode |
837 | infocmp -C rxvt-unicode |
| 838 | |
838 | |
| 839 | Or you could use this termcap entry, generated by the command above: |
839 | Or you could use this termcap entry, generated by the command above: |
| 840 | |
840 | |
| … | |
… | |
| 859 | :us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\ |
859 | :us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\ |
| 860 | :vs=\E[?25h: |
860 | :vs=\E[?25h: |
| 861 | |
861 | |
| 862 | Why does "ls" no longer have coloured output? |
862 | Why does "ls" no longer have coloured output? |
| 863 | The "ls" in the GNU coreutils unfortunately doesn't use terminfo to |
863 | The "ls" in the GNU coreutils unfortunately doesn't use terminfo to |
| 864 | decide wether a terminal has colour, but uses its own configuration |
864 | decide whether a terminal has colour, but uses its own configuration |
| 865 | file. Needless to say, "rxvt-unicode" is not in its default file (among |
865 | file. Needless to say, "rxvt-unicode" is not in its default file (among |
| 866 | with most other terminals supporting colour). Either add: |
866 | with most other terminals supporting colour). Either add: |
| 867 | |
867 | |
| 868 | TERM rxvt-unicode |
868 | TERM rxvt-unicode |
| 869 | |
869 | |
| … | |
… | |
| 997 | |
997 | |
| 998 | - Make sure your XIM server is actually running. |
998 | - Make sure your XIM server is actually running. |
| 999 | - Make sure the "XMODIFIERS" environment variable is set correctly when |
999 | - Make sure the "XMODIFIERS" environment variable is set correctly when |
| 1000 | *starting* rxvt-unicode. |
1000 | *starting* rxvt-unicode. |
| 1001 | When you want to use e.g. kinput2, it must be set to "@im=kinput2". |
1001 | When you want to use e.g. kinput2, it must be set to "@im=kinput2". |
| 1002 | For scim, use "@im=SCIM". Youc an see what input method servers are |
1002 | For scim, use "@im=SCIM". You can see what input method servers are |
| 1003 | running with this command: |
1003 | running with this command: |
| 1004 | |
1004 | |
| 1005 | xprop -root XIM_SERVERS |
1005 | xprop -root XIM_SERVERS |
| 1006 | |
1006 | |
| 1007 | |
1007 | |
| … | |
… | |
| 1044 | that might encounter the same issue. |
1044 | that might encounter the same issue. |
| 1045 | |
1045 | |
| 1046 | I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation? |
1046 | I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation? |
| 1047 | You should build one binary with the default options. configure now |
1047 | You should build one binary with the default options. configure now |
| 1048 | enables most useful options, and the trend goes to making them |
1048 | enables most useful options, and the trend goes to making them |
| 1049 | runtime-switchable, too, so there is usually no drawback to enbaling |
1049 | runtime-switchable, too, so there is usually no drawback to enabling |
| 1050 | them, except higher disk and possibly memory usage. The perl interpreter |
1050 | them, except higher disk and possibly memory usage. The perl interpreter |
| 1051 | should be enabled, as important functionality (menus, selection, likely |
1051 | should be enabled, as important functionality (menus, selection, likely |
| 1052 | more in the future) depends on it. |
1052 | more in the future) depends on it. |
| 1053 | |
1053 | |
| 1054 | You should not overwrite the "perl-ext-common" snd "perl-ext" resources |
1054 | You should not overwrite the "perl-ext-common" snd "perl-ext" resources |
| … | |
… | |
| 1086 | #define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x) |
1086 | #define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x) |
| 1087 | |
1087 | |
| 1088 | I am on FreeBSD and rxvt-unicode does not seem to work at all. |
1088 | I am on FreeBSD and rxvt-unicode does not seem to work at all. |
| 1089 | Rxvt-unicode requires the symbol "__STDC_ISO_10646__" to be defined in |
1089 | Rxvt-unicode requires the symbol "__STDC_ISO_10646__" to be defined in |
| 1090 | your compile environment, or an implementation that implements it, |
1090 | your compile environment, or an implementation that implements it, |
| 1091 | wether it defines the symbol or not. "__STDC_ISO_10646__" requires that |
1091 | whether it defines the symbol or not. "__STDC_ISO_10646__" requires that |
| 1092 | wchar_t is represented as unicode. |
1092 | wchar_t is represented as unicode. |
| 1093 | |
1093 | |
| 1094 | As you might have guessed, FreeBSD does neither define this symobl nor |
1094 | As you might have guessed, FreeBSD does neither define this symbol nor |
| 1095 | does it support it. Instead, it uses its own internal representation of |
1095 | does it support it. Instead, it uses its own internal representation of |
| 1096 | wchar_t. This is, of course, completely fine with respect to standards. |
1096 | wchar_t. This is, of course, completely fine with respect to standards. |
| 1097 | |
1097 | |
| 1098 | However, that means rxvt-unicode only works in "POSIX", "ISO-8859-1" and |
1098 | However, that means rxvt-unicode only works in "POSIX", "ISO-8859-1" and |
| 1099 | "UTF-8" locales under FreeBSD (which all use Unicode as wchar_t. |
1099 | "UTF-8" locales under FreeBSD (which all use Unicode as wchar_t. |
| … | |
… | |
| 1926 | rectangular selections |
1926 | rectangular selections |
| 1927 | trailing space removal for selections |
1927 | trailing space removal for selections |
| 1928 | verbose X error handling |
1928 | verbose X error handling |
| 1929 | |
1929 | |
| 1930 | --enable-iso14755 (default: on) |
1930 | --enable-iso14755 (default: on) |
| 1931 | Enable extended ISO 14755 support (see urxvt(1), or doc/rxvt.1.txt). |
1931 | Enable extended ISO 14755 support (see rxvt(1), or doc/rxvt.1.txt). |
| 1932 | Basic support (section 5.1) is enabled by "--enable-frills", while |
1932 | Basic support (section 5.1) is enabled by "--enable-frills", while |
| 1933 | support for 5.2, 5.3 and 5.4 is enabled with this switch. |
1933 | support for 5.2, 5.3 and 5.4 is enabled with this switch. |
| 1934 | |
1934 | |
| 1935 | --enable-keepscrolling (default: on) |
1935 | --enable-keepscrolling (default: on) |
| 1936 | Add support for continual scrolling of the display when you hold the |
1936 | Add support for continual scrolling of the display when you hold the |
| … | |
… | |
| 1967 | |
1967 | |
| 1968 | --enable-pointer-blank (default: on) |
1968 | --enable-pointer-blank (default: on) |
| 1969 | Add support to have the pointer disappear when typing or inactive. |
1969 | Add support to have the pointer disappear when typing or inactive. |
| 1970 | |
1970 | |
| 1971 | --enable-perl (default: on) |
1971 | --enable-perl (default: on) |
| 1972 | Enable an embedded perl interpreter. See the urxvtperl(3) manpage |
1972 | Enable an embedded perl interpreter. See the rxvtperl(3) manpage |
| 1973 | (doc/rxvtperl.txt) for more info on this feature, or the files in |
1973 | (doc/rxvtperl.txt) for more info on this feature, or the files in |
| 1974 | src/perl-ext/ for the extensions that are installed by default. The |
1974 | src/perl-ext/ for the extensions that are installed by default. The |
| 1975 | perl interpreter that is used can be specified via the "PERL" |
1975 | perl interpreter that is used can be specified via the "PERL" |
| 1976 | environment variable when running configure. |
1976 | environment variable when running configure. |
| 1977 | |
1977 | |
