| … | |
… | |
| 387 | |
387 | |
| 388 | Now you can start your terminal with "LC_CTYPE=ja_JP.UTF-8" and |
388 | 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 |
389 | 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, |
390 | be able to input characters outside "EUC-JP" in a normal way then, |
| 391 | as your input method limits you. |
391 | as your input method limits you. |
|
|
392 | |
|
|
393 | Rxvt-unicode crashes when the X Input Method changes or exits. |
|
|
394 | Unfortunately, this is unavoidable, as the XIM protocol is racy by |
|
|
395 | design. Applications can avoid some crashes at the expense of memory |
|
|
396 | leaks, and Input Methods can avoid some crashes by careful ordering |
|
|
397 | at exit time. kinput2 (and derived input methods) generally |
|
|
398 | succeeds, while SCIM (or similar input methods) fails. In the end, |
|
|
399 | however, crashes cannot be completely avoided even if both sides |
|
|
400 | cooperate. |
|
|
401 | |
|
|
402 | So the only workaround is not to kill your Input Method Servers. |
| 392 | |
403 | |
| 393 | Rxvt-unicode uses gobs of memory, how can I reduce that? |
404 | Rxvt-unicode uses gobs of memory, how can I reduce that? |
| 394 | Rxvt-unicode tries to obey the rule of not charging you for |
405 | 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 |
406 | 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 |
407 | out all settings that you don't need, for example, Xft support is a |
