(Sorry, hit the "send" button too soon)
Etsushi Kato wrote:
> I'm one of the developer of uim. As far as I can tell, you can
> avoid this complete freeze of X by using --async option of
> uim-xim.
Thank you!!! This indeed works. In Debian Sid, I set
XIM_ARGS=--async in /etc/X11/xinit/xinput.d/uim-systray, and
indeed it works now exactly as you said: CPU usage goes to 100%
when I 'mis-hit' keys, but this is temporary and X does not
freeze. If no side effects are expected, I would vote for "async"
to be the default. I just wonder why Omote-san could not reproduce
this.
> I think this bug is caused from invalid use of filter key event
> in mozilla in the address bar widget.
So you agree it is a bug? Can you reproduce it? If it is a bug in
Mozilla/Firefox, somebody should report it, but I'm afraid I do
not have the technical knowledge about 'filter key events' to
describe it exactly.
> [..]
> By the way, you seem to like using XIM instead of gtk+ immodule
> because of the compose sequences in X11.
Two reasons:
1 - the compose sequences. With uim default method = "direct", it
is as if uim does not exist. There is just the arrow symbol in
the systray. All the xkb/compose stuff works (not so with
SCIM, that ís why I like uim better!). But if I want to use
uim, it is there, and I can activate it by right-clicking on
the arrow.
2 - xim always works. When I activate uim, I can use it
everywhere: xterm programs, openoffice, qt programs, gtk
programs, mozilla, even in xfig. Very simple, very neat.
Thanks again,
Jan
