Yasuhiro Matsumoto wrote: > On Thursday, July 19, 2012 8:36:43 PM UTC+9, 依云 wrote: > > On Wed, Jul 18, 2012 at 05:07:23AM -0700, mattn wrote: > > > Please try previous patch. > > > > > > https://gist.github.com/3135711 > > > > I tried this patch. Unfortunately, I don't see any difference. > > > > (I finally find out that) the problem I have is, Vim will shutdown the > > IM when entering and leaving normal mode. This will make my autocmds > > handling at the wrong IM context. > > > > My patch simply makes Vim lose the control of IM, which is undesired > > when without a more precise IM controlling plugin. > > > > So, my suggestion is to use an option to let Vim not control the IM (those > > codes in #ifdef USE_IM_CONTROL) (maybe in addtion to cleaning up the old > > code). Is this ok? > > Then, How about new option 'imactivateexpr' ? > If imactivateexpr is set as user function, vim don't shutdown IM, and call > the function. > > function MyImActivateExpr(active) > " something to switch activate of IM > endfunction > > set imactivateexpr=MyActivateExpr
So, what is the conclusion about this patch? Is it really an improvement and does not break IME for any language? -- Hear about the guy who played a blank tape at full blast? The mime next door went nuts. /// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\ /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ an exciting new programming language -- http://www.Zimbu.org /// \\\ help me help AIDS victims -- http://ICCF-Holland.org /// -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
