| … | |
… | |
| 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: |
| … | |
… | |
| 486 | support this (for instance because it is not visual), then rxvt-unicode |
497 | support this (for instance because it is not visual), then rxvt-unicode |
| 487 | will continue without an input method. |
498 | will continue without an input method. |
| 488 | |
499 | |
| 489 | In this case either do not specify a preeditStyle or specify more than |
500 | In this case either do not specify a preeditStyle or specify more than |
| 490 | one pre-edit style, such as OverTheSpot,Root,None. |
501 | one pre-edit style, such as OverTheSpot,Root,None. |
|
|
502 | |
|
|
503 | If it still doesn't work, then maybe your input method doesn't support |
|
|
504 | compose sequences - to fall back to the built-in one, make sure you |
|
|
505 | don't specify an input method via "-im" or "XMODIFIERS". |
| 491 | |
506 | |
| 492 | I cannot type "Ctrl-Shift-2" to get an ASCII NUL character due to ISO 14755 |
507 | 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 |
508 | 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 |
509 | international keyboards) or simply use ISO 14755 support to your |
| 495 | advantage, typing <Ctrl-Shift-0> to get a ASCII NUL. This works for |
510 | advantage, typing <Ctrl-Shift-0> to get a ASCII NUL. This works for |
| … | |
… | |
| 635 | 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 |
| 636 | write. |
651 | write. |
| 637 | |
652 | |
| 638 | The selection stuff mainly makes the selection perl-error-message aware |
653 | 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 |
654 | and tells it to convert perl error messages into vi-commands to load the |
| 640 | relevant file and go tot he error line number. |
655 | relevant file and go to the error line number. |
| 641 | |
656 | |
| 642 | URxvt.scrollstyle: plain |
657 | URxvt.scrollstyle: plain |
| 643 | URxvt.secondaryScroll: true |
658 | URxvt.secondaryScroll: true |
| 644 | |
659 | |
| 645 | As the documentation says: plain is the preferred scrollbar for the |
660 | As the documentation says: plain is the preferred scrollbar for the |
| … | |
… | |
| 718 | 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 |
| 719 | (Non-bold) font is already bold, and I want to see a difference between |
734 | (Non-bold) font is already bold, and I want to see a difference between |
| 720 | bold and normal fonts. |
735 | bold and normal fonts. |
| 721 | |
736 | |
| 722 | Please note that I used the "urxvt" instance name and not the "URxvt" |
737 | Please note that I used the "urxvt" instance name and not the "URxvt" |
| 723 | class name. Thats because I use different configs for different |
738 | class name. That is because I use different configs for different |
| 724 | purposes, for example, my IRC window is started with "-name IRC", and |
739 | purposes, for example, my IRC window is started with "-name IRC", and |
| 725 | uses these defaults: |
740 | uses these defaults: |
| 726 | |
741 | |
| 727 | IRC*title: IRC |
742 | IRC*title: IRC |
| 728 | IRC*geometry: 87x12+535+542 |
743 | IRC*geometry: 87x12+535+542 |
| … | |
… | |
| 732 | IRC*boldFont: suxuseuro |
747 | IRC*boldFont: suxuseuro |
| 733 | IRC*colorBD: white |
748 | IRC*colorBD: white |
| 734 | IRC*keysym.M-C-1: command:\033]710;suxuseuro\007\033]711;suxuseuro\007 |
749 | 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 |
750 | IRC*keysym.M-C-2: command:\033]710;9x15bold\007\033]711;9x15bold\007 |
| 736 | |
751 | |
| 737 | "Alt-Shift-1" and "Alt-Shift-2" switch between two different font sizes. |
752 | "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 |
753 | "suxuseuro" allows me to keep an eye (and actually read) stuff while |
| 739 | keeping a very small window. If somebody pastes something complicated |
754 | keeping a very small window. If somebody pastes something complicated |
| 740 | (e.g. japanese), I temporarily switch to a larger font. |
755 | (e.g. japanese), I temporarily switch to a larger font. |
| 741 | |
756 | |
| 742 | The above is all in my ".Xdefaults" (I don't use ".Xresources" nor |
757 | The above is all in my ".Xdefaults" (I don't use ".Xresources" nor |
| … | |
… | |
| 778 | 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 |
| 779 | 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 |
| 780 | arises). |
795 | arises). |
| 781 | |
796 | |
| 782 | The correct solution for this problem is to install the terminfo, this |
797 | 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 |
798 | can be done by simply installing rxvt-unicode on the remote system as |
| 784 | admin): |
799 | well (in case you have a nice package manager ready), or you can install |
|
|
800 | the terminfo database manually like this (with ncurses infocmp. works as |
|
|
801 | user and root): |
| 785 | |
802 | |
| 786 | REMOTE=remotesystem.domain |
803 | REMOTE=remotesystem.domain |
| 787 | infocmp rxvt-unicode | ssh $REMOTE "mkdir -p .terminfo && cat >/tmp/ti && tic /tmp/ti" |
804 | 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 | |
805 | |
| 791 | One some systems you might need to set $TERMINFO to the full path of |
806 | One some systems you might need to set $TERMINFO to the full path of |
| 792 | $HOME/.terminfo for this to work. |
807 | $HOME/.terminfo for this to work. |
| 793 | |
808 | |
| 794 | If you cannot or do not want to do this, then you can simply set |
809 | If you cannot or do not want to do this, then you can simply set |
| … | |
… | |
| 804 | URxvt.termName: rxvt |
819 | URxvt.termName: rxvt |
| 805 | |
820 | |
| 806 | If you don't plan to use rxvt (quite common...) you could also replace |
821 | 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". |
822 | the rxvt terminfo file with the rxvt-unicode one and use "TERM=rxvt". |
| 808 | |
823 | |
|
|
824 | nano fails with "Error opening terminal: rxvt-unicode" |
|
|
825 | This exceptionally confusing and useless error message is printed by |
|
|
826 | nano when it can't find the terminfo database. Nothing is wrong with |
|
|
827 | your terminal, read the previous answer for a solution. |
|
|
828 | |
| 809 | "tic" outputs some error when compiling the terminfo entry. |
829 | "tic" outputs some error when compiling the terminfo entry. |
| 810 | Most likely it's the empty definition for "enacs=". Just replace it by |
830 | Most likely it's the empty definition for "enacs=". Just replace it by |
| 811 | "enacs=\E[0@" and try again. |
831 | "enacs=\E[0@" and try again. |
| 812 | |
832 | |
| 813 | "bash"'s readline does not work correctly under urxvt. |
833 | "bash"'s readline does not work correctly under urxvt. |
| … | |
… | |
| 823 | cases. You can also create a termcap entry by using terminfo's infocmp |
843 | cases. You can also create a termcap entry by using terminfo's infocmp |
| 824 | program like this: |
844 | program like this: |
| 825 | |
845 | |
| 826 | infocmp -C rxvt-unicode |
846 | infocmp -C rxvt-unicode |
| 827 | |
847 | |
| 828 | Or you could use this termcap entry, generated by the command above: |
848 | Or you could use the termcap entry in doc/etc/rxvt-unicode.termcap, |
| 829 | |
849 | generated by the command above. |
| 830 | rxvt-unicode|rxvt-unicode terminal (X Window System):\ |
|
|
| 831 | :am:bw:eo:km:mi:ms:xn:xo:\ |
|
|
| 832 | :co#80:it#8:li#24:lm#0:\ |
|
|
| 833 | :AL=\E[%dL:DC=\E[%dP:DL=\E[%dM:DO=\E[%dB:IC=\E[%d@:\ |
|
|
| 834 | :K1=\EOw:K2=\EOu:K3=\EOy:K4=\EOq:K5=\EOs:LE=\E[%dD:\ |
|
|
| 835 | :RI=\E[%dC:SF=\E[%dS:SR=\E[%dT:UP=\E[%dA:ae=\E(B:al=\E[L:\ |
|
|
| 836 | :as=\E(0:bl=^G:cd=\E[J:ce=\E[K:cl=\E[H\E[2J:\ |
|
|
| 837 | :cm=\E[%i%d;%dH:cr=^M:cs=\E[%i%d;%dr:ct=\E[3g:dc=\E[P:\ |
|
|
| 838 | :dl=\E[M:do=^J:ec=\E[%dX:ei=\E[4l:ho=\E[H:\ |
|
|
| 839 | :i1=\E[?47l\E=\E[?1l:ic=\E[@:im=\E[4h:\ |
|
|
| 840 | :is=\E[r\E[m\E[2J\E[H\E[?7h\E[?1;3;4;6l\E[4l:\ |
|
|
| 841 | :k1=\E[11~:k2=\E[12~:k3=\E[13~:k4=\E[14~:k5=\E[15~:\ |
|
|
| 842 | :k6=\E[17~:k7=\E[18~:k8=\E[19~:k9=\E[20~:kD=\E[3~:\ |
|
|
| 843 | :kI=\E[2~:kN=\E[6~:kP=\E[5~:kb=\177:kd=\EOB:ke=\E[?1l\E>:\ |
|
|
| 844 | :kh=\E[7~:kl=\EOD:kr=\EOC:ks=\E[?1h\E=:ku=\EOA:le=^H:\ |
|
|
| 845 | :mb=\E[5m:md=\E[1m:me=\E[m\017:mr=\E[7m:nd=\E[C:rc=\E8:\ |
|
|
| 846 | :sc=\E7:se=\E[27m:sf=^J:so=\E[7m:sr=\EM:st=\EH:ta=^I:\ |
|
|
| 847 | :te=\E[r\E[?1049l:ti=\E[?1049h:ue=\E[24m:up=\E[A:\ |
|
|
| 848 | :us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\ |
|
|
| 849 | :vs=\E[?25h: |
|
|
| 850 | |
850 | |
| 851 | Why does "ls" no longer have coloured output? |
851 | Why does "ls" no longer have coloured output? |
| 852 | The "ls" in the GNU coreutils unfortunately doesn't use terminfo to |
852 | The "ls" in the GNU coreutils unfortunately doesn't use terminfo to |
| 853 | decide whether a terminal has colour, but uses its own configuration |
853 | decide whether a terminal has colour, but uses its own configuration |
| 854 | file. Needless to say, "rxvt-unicode" is not in its default file (among |
854 | file. Needless to say, "rxvt-unicode" is not in its default file (among |
| … | |
… | |
| 1038 | runtime-switchable, too, so there is usually no drawback to enabling |
1038 | runtime-switchable, too, so there is usually no drawback to enabling |
| 1039 | them, except higher disk and possibly memory usage. The perl interpreter |
1039 | them, except higher disk and possibly memory usage. The perl interpreter |
| 1040 | should be enabled, as important functionality (menus, selection, likely |
1040 | should be enabled, as important functionality (menus, selection, likely |
| 1041 | more in the future) depends on it. |
1041 | more in the future) depends on it. |
| 1042 | |
1042 | |
| 1043 | You should not overwrite the "perl-ext-common" snd "perl-ext" resources |
1043 | You should not overwrite the "perl-ext-common" and "perl-ext" resources |
| 1044 | system-wide (except maybe with "defaults"). This will result in useful |
1044 | system-wide (except maybe with "defaults"). This will result in useful |
| 1045 | behaviour. If your distribution aims at low memory, add an empty |
1045 | behaviour. If your distribution aims at low memory, add an empty |
| 1046 | "perl-ext-common" resource to the app-defaults file. This will keep the |
1046 | "perl-ext-common" resource to the app-defaults file. This will keep the |
| 1047 | perl interpreter disabled until the user enables it. |
1047 | perl interpreter disabled until the user enables it. |
| 1048 | |
1048 | |
| … | |
… | |
| 1076 | As you might have guessed, FreeBSD does neither define this symbol nor |
1076 | As you might have guessed, FreeBSD does neither define this symbol nor |
| 1077 | does it support it. Instead, it uses its own internal representation of |
1077 | does it support it. Instead, it uses its own internal representation of |
| 1078 | wchar_t. This is, of course, completely fine with respect to standards. |
1078 | wchar_t. This is, of course, completely fine with respect to standards. |
| 1079 | |
1079 | |
| 1080 | However, that means rxvt-unicode only works in "POSIX", "ISO-8859-1" and |
1080 | However, that means rxvt-unicode only works in "POSIX", "ISO-8859-1" and |
| 1081 | "UTF-8" locales under FreeBSD (which all use Unicode as wchar_t. |
1081 | "UTF-8" locales under FreeBSD (which all use Unicode as wchar_t). |
| 1082 | |
1082 | |
| 1083 | "__STDC_ISO_10646__" is the only sane way to support multi-language apps |
1083 | "__STDC_ISO_10646__" is the only sane way to support multi-language apps |
| 1084 | in an OS, as using a locale-dependent (and non-standardized) |
1084 | in an OS, as using a locale-dependent (and non-standardized) |
| 1085 | representation of wchar_t makes it impossible to convert between wchar_t |
1085 | representation of wchar_t makes it impossible to convert between wchar_t |
| 1086 | (as used by X11 and your applications) and any other encoding without |
1086 | (as used by X11 and your applications) and any other encoding without |
| … | |
… | |
| 1120 | The solution is to upgrade your system or switch to a better one. A |
1120 | The solution is to upgrade your system or switch to a better one. A |
| 1121 | possibly working workaround is to use a wcwidth implementation like |
1121 | possibly working workaround is to use a wcwidth implementation like |
| 1122 | |
1122 | |
| 1123 | http://www.cl.cam.ac.uk/~mgk25/ucs/wcwidth.c |
1123 | http://www.cl.cam.ac.uk/~mgk25/ucs/wcwidth.c |
| 1124 | |
1124 | |
|
|
1125 | I want 256 colors |
|
|
1126 | Are you sure you need 256 colors? 88 colors should be enough for most |
|
|
1127 | purposes. If you really need more, there is an unsupported patch for it |
|
|
1128 | in the doc directory, but please do not ask for it to be applied. |
|
|
1129 | |
