| … | |
… | |
| 430 | To get a selection that is very similar to the old code, try this |
430 | To get a selection that is very similar to the old code, try this |
| 431 | pattern: |
431 | pattern: |
| 432 | |
432 | |
| 433 | URxvt.selection.pattern-0: ([^"&'()*,;<=>?@[\\\\]^`{|})]+) |
433 | URxvt.selection.pattern-0: ([^"&'()*,;<=>?@[\\\\]^`{|})]+) |
| 434 | |
434 | |
| 435 | Please also note that the *LeftClick Shift-LeftClik* combination also |
435 | Please also note that the *LeftClick Shift-LeftClick* combination also |
| 436 | selects words like the old code. |
436 | selects words like the old code. |
| 437 | |
437 | |
| 438 | I don't like the new selection/popups/hotkeys/perl, how do I change/disable it? |
438 | I don't like the new selection/popups/hotkeys/perl, how do I change/disable it? |
| 439 | You can disable the perl extension completely by setting the |
439 | You can disable the perl extension completely by setting the |
| 440 | perl-ext-common resource to the empty string, which also keeps |
440 | perl-ext-common resource to the empty string, which also keeps |
| … | |
… | |
| 823 | cases. You can also create a termcap entry by using terminfo's infocmp |
823 | cases. You can also create a termcap entry by using terminfo's infocmp |
| 824 | program like this: |
824 | program like this: |
| 825 | |
825 | |
| 826 | infocmp -C rxvt-unicode |
826 | infocmp -C rxvt-unicode |
| 827 | |
827 | |
| 828 | Or you could use this termcap entry, generated by the command above: |
828 | Or you could use the termcap entry in doc/etc/rxvt-unicode.termcap, |
| 829 | |
829 | 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 | |
830 | |
| 851 | Why does "ls" no longer have coloured output? |
831 | Why does "ls" no longer have coloured output? |
| 852 | The "ls" in the GNU coreutils unfortunately doesn't use terminfo to |
832 | The "ls" in the GNU coreutils unfortunately doesn't use terminfo to |
| 853 | decide whether a terminal has colour, but uses its own configuration |
833 | 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 |
834 | file. Needless to say, "rxvt-unicode" is not in its default file (among |
| … | |
… | |
| 991 | For scim, use "@im=SCIM". You can see what input method servers are |
971 | For scim, use "@im=SCIM". You can see what input method servers are |
| 992 | running with this command: |
972 | running with this command: |
| 993 | |
973 | |
| 994 | xprop -root XIM_SERVERS |
974 | xprop -root XIM_SERVERS |
| 995 | |
975 | |
| 996 | * |
976 | |
| 997 | |
977 | |
| 998 | My input method wants <some encoding> but I want UTF-8, what can I do? |
978 | My input method wants <some encoding> but I want UTF-8, what can I do? |
| 999 | You can specify separate locales for the input method and the rest of |
979 | You can specify separate locales for the input method and the rest of |
| 1000 | the terminal, using the resource "imlocale": |
980 | the terminal, using the resource "imlocale": |
| 1001 | |
981 | |
| … | |
… | |
| 1076 | As you might have guessed, FreeBSD does neither define this symbol nor |
1056 | 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 |
1057 | 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. |
1058 | wchar_t. This is, of course, completely fine with respect to standards. |
| 1079 | |
1059 | |
| 1080 | However, that means rxvt-unicode only works in "POSIX", "ISO-8859-1" and |
1060 | 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. |
1061 | "UTF-8" locales under FreeBSD (which all use Unicode as wchar_t). |
| 1082 | |
1062 | |
| 1083 | "__STDC_ISO_10646__" is the only sane way to support multi-language apps |
1063 | "__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) |
1064 | in an OS, as using a locale-dependent (and non-standardized) |
| 1085 | representation of wchar_t makes it impossible to convert between wchar_t |
1065 | 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 |
1066 | (as used by X11 and your applications) and any other encoding without |
