> > This is a "live long" problem of Windows console in all versions of Windows, > which Microsoft never care to fix in the past, now, or in the future. >
Actually, the console version of vim CAN accept IME input in some earlier version of windows, e.g. Windows XP. (Of course, with a system default codepage, mine is cp936. But there are issues on input if vimrc set enc to utf8 while tenc is cp936.) I found that input in vim.exe is incorrect since 2012 when I tried windows 8 Release Preview. Now from windows 8 RP to windows 8.1, x86 and x64 version all failed in my test, I thought it should be some issue about conhost (because the earlier version of windows do not use conhost, but there's conime for ime support), but because git-bash has fixed the input issue, I now believe that the input issue should be related to applications but not conhost. BTW days ago, I tried to use MSYS2, which comes with a `POSIX` version of vim. That vim (with the help of msys2.dll et.al.) can accept IME input if its encoding is utf8, and leave tenc to be empty (Well, still have few issues). All above, there MUST be some way to fix this issue, although it seems that a console version under windows is not so popular. -- -- 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 vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
