When (and only when) the latexsuite plugin is in effect in gvim, it is impossible to use an XIM method to input text. kinput2 + canna XMODIFIERS="@im=kinput2" XIM="kinput2" GTK_IM_MODULE=xim It works fine when editing non-tex files. When editing a tex file, I am able to turn the XIM on with the proper keystroke. After typing a single symbol, the XIM is turned off, and the input key is sent to vim "as-is". I.e, if I typed "i", I get the hiragana i, い, If I typed k, I get just k.
Trying to Cc: James Noble, as per a request in the metadata of the package.
Ok, I have no clue about LaTex and no clue about XIM. Have you tried asking on the vim-latex-devel mailing list? I'm pretty sure that this is an upstream bug, not something we're causing.
I haven't tried asking upstream for help, and Googling didn't help. However, I am pretty sure I read somewhere (on a gentoo maintained page) that bugs have to be reported on the gentoo bugzilla, and that they will be sent upstream by the devs if appropriate. I will be more or less offline for the next two months, so I can only hope that someone who knows XIM a little more will glance at the bug. But, come-on, you gentoo devs should know better who to Cc to this bug, right? Maybe the cjk herd? You can lower its priority, though, as it only affects gvim, and with vim in the console, everything is good. I don't get the fancy \latex menus, but whatever.
I've narrowed down in the script a few places where I think it might be happening. It seems to not save state properly when it flicks modes on and off (as in, sets the mode then unsets it without thinking about if it was enabled in the first place). At least, that's the only likely way this would happen imho. I'll have a look at it in some more detail at the beginning of next week. I use vim, not gvim, and don't use XIM or the cjk stuff, so I'm unable to replicate this bug, but I'll see what I can do; if not I'll un-CC myself ciaranm: your shout with upstream etc.
see http://sourceforge.net/mailarchive/message.php?msg_id=6287165 link
Ok, we can't really fix this one, since it'd involve doing massive amounts of scary voodoo to vim's map code. Maybe someone will figure out a clever workaround, but I certainly can't see it...
