| … | |
… | |
| 49 | |
49 | |
| 50 | "bash"'s readline does not work correctly under rxvt. |
50 | "bash"'s readline does not work correctly under rxvt. |
| 51 | I need a termcap file entry. |
51 | I need a termcap file entry. |
| 52 | One reason you might want this is that some distributions or |
52 | One reason you might want this is that some distributions or |
| 53 | operating systems still compile some programs using the |
53 | operating systems still compile some programs using the |
| 54 | long-obsoleted termcap (Fedora Core's bash is one example) and rely |
54 | long-obsoleted termcap library (Fedora Core's bash is one example) |
| 55 | on a termcap entry for "rxvt-unicode". |
55 | and rely on a termcap entry for "rxvt-unicode". |
| 56 | |
56 | |
| 57 | You could use rxvt's termcap entry with resonable results in many |
57 | You could use rxvt's termcap entry with resonable results in many |
| 58 | cases. You can also create a termcap entry by using terminfo's |
58 | cases. You can also create a termcap entry by using terminfo's |
| 59 | infocmp program like this: |
59 | infocmp program like this: |
| 60 | |
60 | |
| … | |
… | |
| 62 | |
62 | |
| 63 | Or you could use this termcap entry, generated by the command above: |
63 | Or you could use this termcap entry, generated by the command above: |
| 64 | |
64 | |
| 65 | rxvt-unicode|rxvt-unicode terminal (X Window System):\ |
65 | rxvt-unicode|rxvt-unicode terminal (X Window System):\ |
| 66 | :am:bw:eo:km:mi:ms:xn:xo:\ |
66 | :am:bw:eo:km:mi:ms:xn:xo:\ |
| 67 | :co#80:it#8:li#24:\ |
67 | :co#80:it#8:li#24:lm#0:\ |
| 68 | :AL=\E[%dL:DC=\E[%dP:DL=\E[%dM:DO=\E[%dB:IC=\E[%d@:\ |
68 | :AL=\E[%dL:DC=\E[%dP:DL=\E[%dM:DO=\E[%dB:IC=\E[%d@:\ |
| 69 | :K1=\EOw:K2=\EOu:K3=\EOy:K4=\EOq:K5=\EOs:LE=\E[%dD:\ |
69 | :K1=\EOw:K2=\EOu:K3=\EOy:K4=\EOq:K5=\EOs:LE=\E[%dD:\ |
| 70 | :RI=\E[%dC:SF=\E[%dS:SR=\E[%dT:UP=\E[%dA:ae=^O:al=\E[L:\ |
70 | :RI=\E[%dC:SF=\E[%dS:SR=\E[%dT:UP=\E[%dA:ae=\E(B:al=\E[L:\ |
| 71 | :as=^N:bl=^G:cd=\E[J:ce=\E[K:cl=\E[H\E[2J:cm=\E[%i%d;%dH:\ |
71 | :as=\E(0:bl=^G:cd=\E[J:ce=\E[K:cl=\E[H\E[2J:\ |
| 72 | :cr=^M:cs=\E[%i%d;%dr:ct=\E[3g:dc=\E[P:dl=\E[M:do=^J:\ |
72 | :cm=\E[%i%d;%dH:cr=^M:cs=\E[%i%d;%dr:ct=\E[3g:dc=\E[P:\ |
| 73 | :ec=\E[%dX:ei=\E[4l:ho=\E[H:i1=\E[?47l\E=\E[?1l:ic=\E[@:\ |
73 | :dl=\E[M:do=^J:ec=\E[%dX:ei=\E[4l:ho=\E[H:\ |
|
|
74 | :i1=\E[?47l\E=\E[?1l:ic=\E[@:im=\E[4h:\ |
| 74 | :im=\E[4h:is=\E[r\E[m\E[2J\E[H\E[?7h\E[?1;3;4;6l\E[4l:\ |
75 | :is=\E[r\E[m\E[2J\E[H\E[?7h\E[?1;3;4;6l\E[4l:\ |
| 75 | :k0=\E[21~:k1=\E[11~:k2=\E[12~:k3=\E[13~:k4=\E[14~:\ |
76 | :k1=\E[11~:k2=\E[12~:k3=\E[13~:k4=\E[14~:k5=\E[15~:\ |
| 76 | :k5=\E[15~:k6=\E[17~:k7=\E[18~:k8=\E[19~:k9=\E[20~:\ |
77 | :k6=\E[17~:k7=\E[18~:k8=\E[19~:k9=\E[20~:kD=\E[3~:\ |
| 77 | :kD=\E[3~:kI=\E[2~:kN=\E[6~:kP=\E[5~:kb=\177:kd=\EOB:\ |
78 | :kI=\E[2~:kN=\E[6~:kP=\E[5~:kb=\177:kd=\EOB:ke=\E[?1l\E>:\ |
| 78 | :ke=\E[?1l\E>:kh=\E[7~:kl=\EOD:kr=\EOC:ks=\E[?1h\E=:\ |
79 | :kh=\E[7~:kl=\EOD:kr=\EOC:ks=\E[?1h\E=:ku=\EOA:le=^H:\ |
| 79 | :ku=\EOA:le=^H:mb=\E[5m:md=\E[1m:me=\E[m\017:mr=\E[7m:\ |
80 | :mb=\E[5m:md=\E[1m:me=\E[m\017:mr=\E[7m:nd=\E[C:rc=\E8:\ |
| 80 | :nd=\E[C:rc=\E8:sc=\E7:se=\E[27m:sf=^J:so=\E[7m:sr=\EM:\ |
81 | :sc=\E7:se=\E[27m:sf=^J:so=\E[7m:sr=\EM:st=\EH:ta=^I:\ |
| 81 | :st=\EH:ta=^I:te=\E[r\E[?1049l:ti=\E[?1049h:ue=\E[24m:\ |
82 | :te=\E[r\E[?1049l:ti=\E[?1049h:ue=\E[24m:up=\E[A:\ |
| 82 | :up=\E[A:us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\ |
83 | :us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\ |
| 83 | :vs=\E[?25h: |
84 | :vs=\E[?25h: |
| 84 | |
85 | |
| 85 | Why does "ls" no longer have coloured output? |
86 | Why does "ls" no longer have coloured output? |
| 86 | The "ls" in the GNU coreutils unfortunately doesn't use terminfo to |
87 | The "ls" in the GNU coreutils unfortunately doesn't use terminfo to |
| 87 | decide wether a terminal has colour, but uses it's own configuration |
88 | decide wether a terminal has colour, but uses it's own configuration |
| … | |
… | |
| 278 | As you might have guessed, FreeBSD does neither define this symobl |
279 | As you might have guessed, FreeBSD does neither define this symobl |
| 279 | nor does it support it. Instead, it uses it's own internal |
280 | nor does it support it. Instead, it uses it's own internal |
| 280 | representation of wchar_t. This is, of course, completely fine with |
281 | representation of wchar_t. This is, of course, completely fine with |
| 281 | respect to standards. |
282 | respect to standards. |
| 282 | |
283 | |
|
|
284 | However, that means rxvt-unicode only works in "POSIX", "ISO-8859-1" |
|
|
285 | and "UTF-8" locales under FreeBSD (which all use Unicode as wchar_t. |
|
|
286 | |
| 283 | However, "__STDC_ISO_10646__" is the only sane way to support |
287 | "__STDC_ISO_10646__" is the only sane way to support multi-language |
| 284 | multi-language apps in an OS, as using a locale-dependent (and |
288 | apps in an OS, as using a locale-dependent (and non-standardized) |
| 285 | non-standardized) representation of wchar_t makes it impossible to |
289 | representation of wchar_t makes it impossible to convert between |
| 286 | convert between wchar_t (as used by X11 and your applications) and |
290 | wchar_t (as used by X11 and your applications) and any other |
| 287 | any other encoding without implementing OS-specific-wrappers for |
291 | encoding without implementing OS-specific-wrappers for each and |
| 288 | each and every locale. There simply are no APIs to convert wchar_t |
292 | every locale. There simply are no APIs to convert wchar_t into |
| 289 | into anything except the current locale encoding. |
293 | anything except the current locale encoding. |
| 290 | |
294 | |
| 291 | Some applications (such as the formidable mlterm) work around this |
295 | Some applications (such as the formidable mlterm) work around this |
| 292 | by carrying their own replacement functions for character set |
296 | by carrying their own replacement functions for character set |
| 293 | handling with them, and either implementing OS-dependent hacks or |
297 | handling with them, and either implementing OS-dependent hacks or |
| 294 | doing multiple conversions (which is slow and unreliable in case the |
298 | doing multiple conversions (which is slow and unreliable in case the |
| … | |
… | |
| 387 | |
391 | |
| 388 | Now you can start your terminal with "LC_CTYPE=ja_JP.UTF-8" and |
392 | Now you can start your terminal with "LC_CTYPE=ja_JP.UTF-8" and |
| 389 | still use your input method. Please note, however, that you will not |
393 | still use your input method. Please note, however, that you will not |
| 390 | be able to input characters outside "EUC-JP" in a normal way then, |
394 | be able to input characters outside "EUC-JP" in a normal way then, |
| 391 | as your input method limits you. |
395 | as your input method limits you. |
|
|
396 | |
|
|
397 | Rxvt-unicode crashes when the X Input Method changes or exits. |
|
|
398 | Unfortunately, this is unavoidable, as the XIM protocol is racy by |
|
|
399 | design. Applications can avoid some crashes at the expense of memory |
|
|
400 | leaks, and Input Methods can avoid some crashes by careful ordering |
|
|
401 | at exit time. kinput2 (and derived input methods) generally |
|
|
402 | succeeds, while SCIM (or similar input methods) fails. In the end, |
|
|
403 | however, crashes cannot be completely avoided even if both sides |
|
|
404 | cooperate. |
|
|
405 | |
|
|
406 | So the only workaround is not to kill your Input Method Servers. |
| 392 | |
407 | |
| 393 | Rxvt-unicode uses gobs of memory, how can I reduce that? |
408 | Rxvt-unicode uses gobs of memory, how can I reduce that? |
| 394 | Rxvt-unicode tries to obey the rule of not charging you for |
409 | Rxvt-unicode tries to obey the rule of not charging you for |
| 395 | something you don't use. One thing you should try is to configure |
410 | something you don't use. One thing you should try is to configure |
| 396 | out all settings that you don't need, for example, Xft support is a |
411 | out all settings that you don't need, for example, Xft support is a |
