Maybe on certain Linux distributions
which keep their Vim a year or more out of date this idea makes sense,
but I still think even "serious" users can work for years without ever
touching the C code.
To do compile yourself is one thing, to touch the C code is quite another.
Most Linux distributions are too "free" on packaging vim and user got a
completely unknown version of vim and it may change very often. You even
don't know what feature will still exist and what unwanted feature will
be added in the next update!
So this actually is the problem of distribution package maintainer, and
this is the reason I would recommend against using the
distribution-specific version of vim.
By using your own version of vim you can:
1. know this is your vim and wanted feature is always there.
2. update to the latest patch.
3. embedded symbol information in it and have the correct stacktrace
when crash.
So, seriously, if you're using Linux please compile vim yourself. This
does not require any knowledge in C at all.
Well, if you're talking about the Windows version, then it seems no
point compile yourself. Because you know you ARE getting the "Cream"
version, but what is the percentage of Windows gvim users?
Yes, Windows rule 90% of the desktop, but most of those poeple do not
use vim, and vim runs not only in desktop but also in the server. I
expect more than 50% of vim users are not using vim in Windows.
--
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
