Hi, 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.
I think this bug is caused from invalid use of filter key event in mozilla in the address bar widget. Even if you use uim-xim --async (or maybe SCIM's x11 module), CPU usage may increase to 100% while inputting some characters with completed addresses below address widget popup, but in this case mozilla won't freeze at all. By the way, you seem to like using XIM instead of gtk+ immodule because of the compose sequences in X11. I think you can try uim's gtk+ immodule with latin IM (selecting "Latin characters" from toolbar) enabled. It support most of the sequence in X's compose sequence using Compose key (bug dead key is not supported yet). You can modify this table if you like. Please check the table in /usr/share/uim/latin.scm. Cheers, -- Etsushi Kato [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
