On 08/12/13 14:56, 蘇連傑 wrote:
[…]
Ah yes, my vim version is 7.4 from vim.org <http://vim.org>.
[…]

Vim from vim.org isn't updated very often (usually only for an x.x "minor version" release, not at every patchlevel) because Bram knows that there are "almost official" versions available which are updated more often.

Near the top of the answer from the :version command, "Included patches" tells you which patches (if any) were included. (If the line is not present, it means "none"). What all those patches are for can be seen at http://ftp.vim.org/pub/vim/patches/7.4/README

An up-to-date or almost up-to-date Win32 version of Vim (which also runs under Win64 OSes, of course) can be found at http://sourceforge.net/projects/cream/files/Vim/ — this is what old-timers of these discussion groups know under the nickname "Vim without Cream". The latest distribution available there as of this writing is 7.4.110 with or without Perl. It is not the one pointed to by the link "Looking for the next version?", but the topmost two after the "↑ Parent folder" link.

This distribution is regarded as "unofficial" because it is not compiled by Bram, but it is made from Bram's official sources.


I don't know the details of using Vim with Windows IME but it should be documented under :help mbyte-IME


Bug reporting and bug fixing in Vim, as well as technical details which interest Vim developers but not the run-of-the-mill Vim user, are discussed in the vim_dev group. Multibyte-specific problems ought to belong in the vim_multibyte group but I'm not sure if that group still has many followers nowadays.



Best regards,
Tony.
--
Lisp hackers have to be bound (to-do 'it) ...

--
--
You received this message from the "vim_use" 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_use" 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/groups/opt_out.

Reply via email to