| … | |
… | |
| 408 | |
408 | |
| 409 | Now you can start your terminal with "LC_CTYPE=ja_JP.UTF-8" and |
409 | 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 |
410 | 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, |
411 | be able to input characters outside "EUC-JP" in a normal way then, |
| 412 | as your input method limits you. |
412 | as your input method limits you. |
|
|
413 | |
|
|
414 | Rxvt-unicode crashes when the X Input Method changes or exits. |
|
|
415 | Unfortunately, this is unavoidable, as the XIM protocol is racy by |
|
|
416 | design. Applications can avoid some crashes at the expense of memory |
|
|
417 | leaks, and Input Methods can avoid some crashes by careful ordering |
|
|
418 | at exit time. kinput2 (and derived input methods) generally |
|
|
419 | succeeds, while SCIM (or similar input methods) fails. In the end, |
|
|
420 | however, crashes cannot be completely avoided even if both sides |
|
|
421 | cooperate. |
|
|
422 | |
|
|
423 | So the only workaround is not to kill your Input Method Servers. |
| 413 | |
424 | |
| 414 | Rxvt-unicode uses gobs of memory, how can I reduce that? |
425 | Rxvt-unicode uses gobs of memory, how can I reduce that? |
| 415 | Rxvt-unicode tries to obey the rule of not charging you for |
426 | 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 |
427 | 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 |
428 | out all settings that you don't need, for example, Xft support is a |
