| … | |
… | |
| 70 | |
70 | |
| 71 | "bash"'s readline does not work correctly under rxvt. |
71 | "bash"'s readline does not work correctly under rxvt. |
| 72 | I need a termcap file entry. |
72 | I need a termcap file entry. |
| 73 | One reason you might want this is that some distributions or |
73 | One reason you might want this is that some distributions or |
| 74 | operating systems still compile some programs using the |
74 | operating systems still compile some programs using the |
| 75 | long-obsoleted termcap (Fedora Core's bash is one example) and rely |
75 | long-obsoleted termcap library (Fedora Core's bash is one example) |
| 76 | on a termcap entry for "rxvt-unicode". |
76 | and rely on a termcap entry for "rxvt-unicode". |
| 77 | |
77 | |
| 78 | You could use rxvt's termcap entry with resonable results in many |
78 | You could use rxvt's termcap entry with resonable results in many |
| 79 | cases. You can also create a termcap entry by using terminfo's |
79 | cases. You can also create a termcap entry by using terminfo's |
| 80 | infocmp program like this: |
80 | infocmp program like this: |
| 81 | |
81 | |
| … | |
… | |
| 83 | |
83 | |
| 84 | Or you could use this termcap entry, generated by the command above: |
84 | Or you could use this termcap entry, generated by the command above: |
| 85 | |
85 | |
| 86 | rxvt-unicode|rxvt-unicode terminal (X Window System):\ |
86 | rxvt-unicode|rxvt-unicode terminal (X Window System):\ |
| 87 | :am:bw:eo:km:mi:ms:xn:xo:\ |
87 | :am:bw:eo:km:mi:ms:xn:xo:\ |
| 88 | :co#80:it#8:li#24:\ |
88 | :co#80:it#8:li#24:lm#0:\ |
| 89 | :AL=\E[%dL:DC=\E[%dP:DL=\E[%dM:DO=\E[%dB:IC=\E[%d@:\ |
89 | :AL=\E[%dL:DC=\E[%dP:DL=\E[%dM:DO=\E[%dB:IC=\E[%d@:\ |
| 90 | :K1=\EOw:K2=\EOu:K3=\EOy:K4=\EOq:K5=\EOs:LE=\E[%dD:\ |
90 | :K1=\EOw:K2=\EOu:K3=\EOy:K4=\EOq:K5=\EOs:LE=\E[%dD:\ |
| 91 | :RI=\E[%dC:SF=\E[%dS:SR=\E[%dT:UP=\E[%dA:ae=^O:al=\E[L:\ |
91 | :RI=\E[%dC:SF=\E[%dS:SR=\E[%dT:UP=\E[%dA:ae=\E(B:al=\E[L:\ |
| 92 | :as=^N:bl=^G:cd=\E[J:ce=\E[K:cl=\E[H\E[2J:cm=\E[%i%d;%dH:\ |
92 | :as=\E(0:bl=^G:cd=\E[J:ce=\E[K:cl=\E[H\E[2J:\ |
| 93 | :cr=^M:cs=\E[%i%d;%dr:ct=\E[3g:dc=\E[P:dl=\E[M:do=^J:\ |
93 | :cm=\E[%i%d;%dH:cr=^M:cs=\E[%i%d;%dr:ct=\E[3g:dc=\E[P:\ |
| 94 | :ec=\E[%dX:ei=\E[4l:ho=\E[H:i1=\E[?47l\E=\E[?1l:ic=\E[@:\ |
94 | :dl=\E[M:do=^J:ec=\E[%dX:ei=\E[4l:ho=\E[H:\ |
|
|
95 | :i1=\E[?47l\E=\E[?1l:ic=\E[@:im=\E[4h:\ |
| 95 | :im=\E[4h:is=\E[r\E[m\E[2J\E[H\E[?7h\E[?1;3;4;6l\E[4l:\ |
96 | :is=\E[r\E[m\E[2J\E[H\E[?7h\E[?1;3;4;6l\E[4l:\ |
| 96 | :k0=\E[21~:k1=\E[11~:k2=\E[12~:k3=\E[13~:k4=\E[14~:\ |
97 | :k1=\E[11~:k2=\E[12~:k3=\E[13~:k4=\E[14~:k5=\E[15~:\ |
| 97 | :k5=\E[15~:k6=\E[17~:k7=\E[18~:k8=\E[19~:k9=\E[20~:\ |
98 | :k6=\E[17~:k7=\E[18~:k8=\E[19~:k9=\E[20~:kD=\E[3~:\ |
| 98 | :kD=\E[3~:kI=\E[2~:kN=\E[6~:kP=\E[5~:kb=\177:kd=\EOB:\ |
99 | :kI=\E[2~:kN=\E[6~:kP=\E[5~:kb=\177:kd=\EOB:ke=\E[?1l\E>:\ |
| 99 | :ke=\E[?1l\E>:kh=\E[7~:kl=\EOD:kr=\EOC:ks=\E[?1h\E=:\ |
100 | :kh=\E[7~:kl=\EOD:kr=\EOC:ks=\E[?1h\E=:ku=\EOA:le=^H:\ |
| 100 | :ku=\EOA:le=^H:mb=\E[5m:md=\E[1m:me=\E[m\017:mr=\E[7m:\ |
101 | :mb=\E[5m:md=\E[1m:me=\E[m\017:mr=\E[7m:nd=\E[C:rc=\E8:\ |
| 101 | :nd=\E[C:rc=\E8:sc=\E7:se=\E[27m:sf=^J:so=\E[7m:sr=\EM:\ |
102 | :sc=\E7:se=\E[27m:sf=^J:so=\E[7m:sr=\EM:st=\EH:ta=^I:\ |
| 102 | :st=\EH:ta=^I:te=\E[r\E[?1049l:ti=\E[?1049h:ue=\E[24m:\ |
103 | :te=\E[r\E[?1049l:ti=\E[?1049h:ue=\E[24m:up=\E[A:\ |
| 103 | :up=\E[A:us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\ |
104 | :us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\ |
| 104 | :vs=\E[?25h: |
105 | :vs=\E[?25h: |
| 105 | |
106 | |
| 106 | Why does "ls" no longer have coloured output? |
107 | Why does "ls" no longer have coloured output? |
| 107 | The "ls" in the GNU coreutils unfortunately doesn't use terminfo to |
108 | The "ls" in the GNU coreutils unfortunately doesn't use terminfo to |
| 108 | decide wether a terminal has colour, but uses it's own configuration |
109 | decide wether a terminal has colour, but uses it's own configuration |
| … | |
… | |
| 408 | |
409 | |
| 409 | Now you can start your terminal with "LC_CTYPE=ja_JP.UTF-8" and |
410 | Now you can start your terminal with "LC_CTYPE=ja_JP.UTF-8" and |
| 410 | still use your input method. Please note, however, that you will not |
411 | still use your input method. Please note, however, that you will not |
| 411 | be able to input characters outside "EUC-JP" in a normal way then, |
412 | be able to input characters outside "EUC-JP" in a normal way then, |
| 412 | as your input method limits you. |
413 | as your input method limits you. |
|
|
414 | |
|
|
415 | Rxvt-unicode crashes when the X Input Method changes or exits. |
|
|
416 | Unfortunately, this is unavoidable, as the XIM protocol is racy by |
|
|
417 | design. Applications can avoid some crashes at the expense of memory |
|
|
418 | leaks, and Input Methods can avoid some crashes by careful ordering |
|
|
419 | at exit time. kinput2 (and derived input methods) generally |
|
|
420 | succeeds, while SCIM (or similar input methods) fails. In the end, |
|
|
421 | however, crashes cannot be completely avoided even if both sides |
|
|
422 | cooperate. |
|
|
423 | |
|
|
424 | So the only workaround is not to kill your Input Method Servers. |
| 413 | |
425 | |
| 414 | Rxvt-unicode uses gobs of memory, how can I reduce that? |
426 | Rxvt-unicode uses gobs of memory, how can I reduce that? |
| 415 | Rxvt-unicode tries to obey the rule of not charging you for |
427 | Rxvt-unicode tries to obey the rule of not charging you for |
| 416 | something you don't use. One thing you should try is to configure |
428 | something you don't use. One thing you should try is to configure |
| 417 | out all settings that you don't need, for example, Xft support is a |
429 | out all settings that you don't need, for example, Xft support is a |
| … | |
… | |
| 1203 | [menu] |
1215 | [menu] |
| 1204 | access the current menuBar for alteration |
1216 | access the current menuBar for alteration |
| 1205 | |
1217 | |
| 1206 | [title:+*string*] |
1218 | [title:+*string*] |
| 1207 | set the current menuBar's title to *string*, which may contain the |
1219 | set the current menuBar's title to *string*, which may contain the |
| 1208 | following format specifiers: %% : literal % character %n : rxvt name |
1220 | following format specifiers: |
| 1209 | (as per the -name command-line option) %v : rxvt version |
1221 | |
|
|
1222 | B<%n> rxvt name (as per the B<-name> command-line option) |
|
|
1223 | B<%v> rxvt version |
|
|
1224 | B<%%> literal B<%> character |
| 1210 | |
1225 | |
| 1211 | [done] |
1226 | [done] |
| 1212 | set menuBar access as readonly. End-of-file tag for [read:+*file*] |
1227 | set menuBar access as readonly. End-of-file tag for [read:+*file*] |
| 1213 | operations. |
1228 | operations. |
| 1214 | |
1229 | |
| … | |
… | |
| 1690 | accents are encoded as seperate unicode characters. This is done by |
1705 | accents are encoded as seperate unicode characters. This is done by |
| 1691 | using precomposited characters when available or creating new |
1706 | using precomposited characters when available or creating new |
| 1692 | pseudo-characters when no precomposed form exists. |
1707 | pseudo-characters when no precomposed form exists. |
| 1693 | |
1708 | |
| 1694 | Without --enable-unicode3, the number of additional precomposed |
1709 | Without --enable-unicode3, the number of additional precomposed |
| 1695 | characters is rather limited (2048, if this is full, rxvt will use |
1710 | characters is rather limited (2048, if this is full, rxvt-unicode |
| 1696 | the private use area, extending the number of combinations to 8448). |
1711 | will use the private use area, extending the number of combinations |
| 1697 | With --enable-unicode3, no practical limit exists. This will also |
1712 | to 8448). With --enable-unicode3, no practical limit exists. |
| 1698 | enable storage of characters >65535. |
1713 | |
|
|
1714 | This option will also enable storage (but not display) of characters |
|
|
1715 | beyond plane 0 (>65535) when --enable-unicode3 was not specified. |
| 1699 | |
1716 | |
| 1700 | The combining table also contains entries for arabic presentation |
1717 | The combining table also contains entries for arabic presentation |
| 1701 | forms, but these are not currently used. Bug me if you want these to |
1718 | forms, but these are not currently used. Bug me if you want these to |
| 1702 | be used. |
1719 | be used (and tell me how these are to be used...). |
| 1703 | |
1720 | |
| 1704 | --enable-fallback(=CLASS) |
1721 | --enable-fallback(=CLASS) |
| 1705 | When reading resource settings, also read settings for class CLASS |
1722 | When reading resource settings, also read settings for class CLASS |
| 1706 | (default: Rxvt). To disable resource fallback use |
1723 | (default: Rxvt). To disable resource fallback use |
| 1707 | --disable-fallback. |
1724 | --disable-fallback. |
| … | |
… | |
| 1815 | backindex and forwardindex escape sequence |
1832 | backindex and forwardindex escape sequence |
| 1816 | window op and locale change escape sequences |
1833 | window op and locale change escape sequences |
| 1817 | tripleclickwords |
1834 | tripleclickwords |
| 1818 | settable insecure mode |
1835 | settable insecure mode |
| 1819 | keysym remapping support |
1836 | keysym remapping support |
|
|
1837 | -embed and -pty-fd options |
| 1820 | |
1838 | |
| 1821 | --enable-iso14755 |
1839 | --enable-iso14755 |
| 1822 | Enable extended ISO 14755 support (see rxvt(1), or doc/rxvt.1.txt). |
1840 | Enable extended ISO 14755 support (see rxvt(1), or doc/rxvt.1.txt). |
| 1823 | Basic support (section 5.1) is enabled by "--enable-frills", while |
1841 | Basic support (section 5.1) is enabled by "--enable-frills", while |
| 1824 | support for 5.2, 5.3 and 5.4 is enabled with this switch. |
1842 | support for 5.2, 5.3 and 5.4 is enabled with this switch. |
