On Thu, Jul 19, 2012 at 09:15:46AM -0700, mattn wrote: > On Thursday, July 19, 2012 8:36:43 PM UTC+9, 依云 wrote: > > [...] > > > > 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
I like this idea! Will someone implement it? -- Best regards, lilydjwg Linux Vim Python 我的博客: http://lilydjwg.is-programmer.com/ -- A: Because it obfuscates the reading. Q: Why is top posting so bad? -- 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
