"Stephen J. Turnbull" <turnbull(a)sk.tsukuba.ac.jp> writes:
>> This is a known problem. I don't think XEmacs can
survive any
>> of the Input Method servers dying.
Kazz> No. As I said before (maybe), the current code lacks of
Kazz> register/unregister the input method. Instead of the
Kazz> implementation, input-method-xlib just opens XIM and attach
Kazz> it to the context. (It is very same with Motif, but Motif
Kazz> does this smart internally)
It's not clear to me what happens in your method if you have just
typed half of a kana in romaji.... Once the input context is open, I'm
not sure what happens if the connection dies. The man page does not
specify error returns for X*LookupString. If the call blocks, we're
screwed anyway.
I found that the latest version of kterm (6.2.0) can treat whenever
XIM is dead or alive, and it is using the X API I mentioned bellow.
Kazz> XRegisterIMInstantiateCallback
Kazz> XUnregisterIMInstantiateCallback
The differences between the kterm and our XEmacs is;
* kterm just has one context (maybe).
* XEmacs opens one XIM for DEVICE, and some XIC for FRAME.
--
Kazz