On Tue, Dec 22, 2015 at 3:57 PM, Bram Moolenaar <[email protected]> wrote: > Nikolay Pavlov wrote: >> 2015-12-21 23:44 GMT+03:00 Bram Moolenaar <[email protected]>: > Please keep in mind that this feature is for users who are not familiar > with building programs. > > Those people who use a package manager or git won't need this command. > Just don't use it. The command can do a check if the Runtime files are > in a place that's likely under control of the package manager and give a > warning. > > On the other hand, if the provided packages are stale, this is a useful > way to update the runtime files without having to switch to building Vim > yourself (which requires figuring out the build options, not that easy > if you do it for the first time). > >> 2. I think this is useless idea for Windows users as well because patches >> 7.N.xxx *do* add features, thus forcing users to choose packages which have >> latest Vim like vim without cream. Such packages, of course, contain >> up-to-date runtime. Updating just runtime here makes some sense, but I >> think that getting used to updating the whole Vim is better. > > I don't agree. Ever looked over the shoulder of someone who tries to > find the Vim installer he wants to use? They probably end up installing > Vim 7.4, just because that's the easiest to find. And that should be > fine, for most users the latests patches don't help them.
This is circular reasoning and a total cop-out. Providing up-to-date win32 binaries at vim.org would avoid the problem; whereas with the extant inertia and lack of automation, there exists an invented problem to be "solved" by providing a new :RuntimeUpdate command that, I predict, will see as much (or rather, little) real-world usage as GLVS and the Vim "bundle" concept. Having observed many new users, and noting my own experience, I can tell you that most users do not have any clue what "runtime" means in the context of Vim. Providing a new :RuntimeUpdate command will be totally confusing, if any user even happens to discover it: they will expect it to update Vim itself, but instead they get some half-baked solution that was already addressed 5 years ago by real-world solutions in the form of Vundle, pathogen, Plug, and NeoBundle. And meanwhile the vim.org win32 binaries will be stale. --- Justin M. Keyes -- -- 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.
