Igor Sverkos - 21.07.17, 14:25: > Hi, > > On Thu, 20 Jul 2017 22:24:01 -0400 James McCoy <james...@debian.org> wrote: > > There's no need to disable defaults.vim. As I have also suggested (in > > this very bug report), you can explicitly load defaults.vim and then > > disable whatever settings you don't like. > > I hit the same problem. Maybe I don't understand your suggestion. Could > you please explain it in more details? > > My problem: > =========== > We have a network running ~600 Debian boxes at the moment. > > We are using Puppet for configuration management. > > I now want to deploy a default system-wide VIM configuration which can > be overwritten by the user using ~/.vimrc. > > How am I supposed to do that? > > I would expect to alter "/etc/vim/vimrc" respective > "/etc/vim/vimrc.local" but this doesn't work when > "/usr/share/vim/vim80/defaults.vim" will be sourced as last > configuration file.
Well that one is actually documented in README.Debian as pointed out here in this bug report several times already. Add let g:skip_defaults_vim = 1 at the beginning of "/etc/vim/vimrc.local". And that is not really the issue of this bug report. The issue is, that it is required to have a work-around like this, or the one James suggested – where it will if I understand correctly load defaults.vim before making changes to it –, in order to have a sane behavior. Since I use Linux, configuration loading always worked from global to local. Here it does not, unless you add a work-around. This has been an upstream decision according to James and I think its best to bring this issue to upstream. If upstream does not adapt the behavior, I am all for a patch in the Debian package, but it seems James thinks differently on that one. Another option would be to vote about that new behavior by switching to neovim. Thanks, -- Martin
signature.asc
Description: This is a digitally signed message part.
