2015-11-03 오후 4:41에 Tony Mechelynck 이(가) 쓴 글: > On Tue, Nov 3, 2015 at 8:22 AM, SungHyun Nam <[email protected]> wrote: >> Hello, >> >> I used hangulin feature nowadays, because it does not support >> utf-8 encoding, I always ran vim with 'set encoding=cp949'. >> But it gave me a pain whenever I open utf-8 encoded file. >> >> So that, today I made a patch. Any feedback is welcome! >> >> Thanks, >> namsh > > From the top of doc/hangulin.txt (Last change 2009 Jun 24): > > <quote> > NOTE: The |+hangul_input| feature is scheduled to be removed. If you want to > keep it, please send a message to the Vim user maillist. > </quote> > > I see you are one of the authors of that feature. Maybe you should > carry on on that caveat, now that most Unix-like systems have a XIM > package available. > > I suppose users should use the input method (XIM or Windows IME) > directly, selecting whichever input method flavour suits them best, > and just scrap the +hangul_input feature. It is not compatible with > GTK2 anyway. And if someone is on some Unix-like OS with no XIM > installed, let him check the available installable packages.
I didn't notice it is scheduled to be removed. :-( I prefer input method if possible. But, from time to time, I needed this feature for some environment. At this time, it seems cygwin64 does not support XIM, so that I used this feature on cygwin64. And when I logged into some remote host and run gvim there, IM does not worked. In that case, I install gvim(+hangulin) to that remote host and use it. BTW, If Bram (and other core developers) want to remove this feature, I will accept the situation. I think I could fork and maintain my own copy. Thanks, namsh -- -- 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 --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
