| … | |
… | |
| 127 | .\} |
127 | .\} |
| 128 | .rm #[ #] #H #V #F C |
128 | .rm #[ #] #H #V #F C |
| 129 | .\" ======================================================================== |
129 | .\" ======================================================================== |
| 130 | .\" |
130 | .\" |
| 131 | .IX Title "rxvt 7" |
131 | .IX Title "rxvt 7" |
| 132 | .TH rxvt 7 "2005-02-11" "5.0" "RXVT-UNICODE" |
132 | .TH rxvt 7 "2005-02-13" "5.1" "RXVT-UNICODE" |
| 133 | .SH "NAME" |
133 | .SH "NAME" |
| 134 | RXVT REFERENCE \- FAQ, command sequences and other background information |
134 | RXVT REFERENCE \- FAQ, command sequences and other background information |
| 135 | .SH "SYNOPSIS" |
135 | .SH "SYNOPSIS" |
| 136 | .IX Header "SYNOPSIS" |
136 | .IX Header "SYNOPSIS" |
| 137 | .Vb 2 |
137 | .Vb 2 |
| … | |
… | |
| 574 | .Sp |
574 | .Sp |
| 575 | Now you can start your terminal with \f(CW\*(C`LC_CTYPE=ja_JP.UTF\-8\*(C'\fR and still |
575 | Now you can start your terminal with \f(CW\*(C`LC_CTYPE=ja_JP.UTF\-8\*(C'\fR and still |
| 576 | use your input method. Please note, however, that you will not be able to |
576 | use your input method. Please note, however, that you will not be able to |
| 577 | input characters outside \f(CW\*(C`EUC\-JP\*(C'\fR in a normal way then, as your input |
577 | input characters outside \f(CW\*(C`EUC\-JP\*(C'\fR in a normal way then, as your input |
| 578 | method limits you. |
578 | method limits you. |
|
|
579 | .IP "Rxvt-unicode crashes when the X Input Method changes or exits." 4 |
|
|
580 | .IX Item "Rxvt-unicode crashes when the X Input Method changes or exits." |
|
|
581 | Unfortunately, this is unavoidable, as the \s-1XIM\s0 protocol is racy by |
|
|
582 | design. Applications can avoid some crashes at the expense of memory |
|
|
583 | leaks, and Input Methods can avoid some crashes by careful ordering at |
|
|
584 | exit time. \fBkinput2\fR (and derived input methods) generally succeeds, |
|
|
585 | while \fB\s-1SCIM\s0\fR (or similar input methods) fails. In the end, however, |
|
|
586 | crashes cannot be completely avoided even if both sides cooperate. |
|
|
587 | .Sp |
|
|
588 | So the only workaround is not to kill your Input Method Servers. |
| 579 | .IP "Rxvt-unicode uses gobs of memory, how can I reduce that?" 4 |
589 | .IP "Rxvt-unicode uses gobs of memory, how can I reduce that?" 4 |
| 580 | .IX Item "Rxvt-unicode uses gobs of memory, how can I reduce that?" |
590 | .IX Item "Rxvt-unicode uses gobs of memory, how can I reduce that?" |
| 581 | Rxvt-unicode tries to obey the rule of not charging you for something you |
591 | Rxvt-unicode tries to obey the rule of not charging you for something you |
| 582 | don't use. One thing you should try is to configure out all settings that |
592 | don't use. One thing you should try is to configure out all settings that |
| 583 | you don't need, for example, Xft support is a resource hog by design, |
593 | you don't need, for example, Xft support is a resource hog by design, |
