It is very old article... But I saved this because I have an idea.
SL Baur <steve(a)xemacs.org> writes:
> Buld and run fine. Except:
> 1. --with-xim=xlib, if you kill your XIM while you're running XIM
> featured xemacs, the xemacs will die or hang.
> This might be known problem since from input-method-xlib was
> introduced.
This is a known problem. I don't think XEmacs can survive any of the
Input Method servers dying.
No. As I said before (maybe), the current code lacks of
register/unregister the input method. Instead of the implementation,
input-method-xlib just opens XIM and attach it to the context.
(It is very same with Motif, but Motif does this smart internally)
Instead of just opening the XIM, we should set the code to:
1. when opening the context, we should set the callback for XIM
that if the XIM is available for the context, use it.
XRegisterIMInstantiateCallback
2. when invoking the XIM, we should register the callback that if
the XIM is unavailable, then release the XIM.
XUnregisterIMInstantiateCallback
I'd been having this idea 1 year, but I have no coding power and the
enough time for this.
Any Xpert?