| … | |
… | |
| 420 | |
420 | |
| 421 | Now you can start your terminal with C<LC_CTYPE=ja_JP.UTF-8> and still |
421 | Now you can start your terminal with C<LC_CTYPE=ja_JP.UTF-8> and still |
| 422 | use your input method. Please note, however, that you will not be able to |
422 | use your input method. Please note, however, that you will not be able to |
| 423 | input characters outside C<EUC-JP> in a normal way then, as your input |
423 | input characters outside C<EUC-JP> in a normal way then, as your input |
| 424 | method limits you. |
424 | method limits you. |
|
|
425 | |
|
|
426 | =item Rxvt-unicode crashes when the X Input Method changes or exits. |
|
|
427 | |
|
|
428 | Unfortunately, this is unavoidable, as the XIM protocol is racy by |
|
|
429 | design. Applications can avoid some crashes at the expense of memory |
|
|
430 | leaks, and Input Methods can avoid some crashes by careful ordering at |
|
|
431 | exit time. B<kinput2> (and derived input methods) generally succeeds, |
|
|
432 | while B<SCIM> (or similar input methods) fails. In the end, however, |
|
|
433 | crashes cannot be completely avoided even if both sides cooperate. |
|
|
434 | |
|
|
435 | So the only workaround is not to kill your Input Method Servers. |
| 425 | |
436 | |
| 426 | =item Rxvt-unicode uses gobs of memory, how can I reduce that? |
437 | =item Rxvt-unicode uses gobs of memory, how can I reduce that? |
| 427 | |
438 | |
| 428 | Rxvt-unicode tries to obey the rule of not charging you for something you |
439 | Rxvt-unicode tries to obey the rule of not charging you for something you |
| 429 | don't use. One thing you should try is to configure out all settings that |
440 | don't use. One thing you should try is to configure out all settings that |
