On Fri, Dec 7, 2018 at 5:28 AM James McCoy <[email protected]> wrote:
> Setting aside the actual details of what options/settings are provided
> by defaults.vim, the mechanism used to provide newer defaults to users
> is faulty.
>
> The fairly standard precedence for configuration at large is:
>
> user config overrides system config overrides baked-in defaults
>
> The mechanism of using defaults.vim changes that to be
>
> (defaults.vim or user config) overrides system config overrides baked-in
> defaults
>
> Cheers,
> --
> James
Long before defaults.vim even existed, my vimrc has had
runtime vimrc_example.vim
near its beginning; then I overrode the settings which I didn't like.
Nowadays, most or all of what used to be in vimrc_example.vim has been
moved to defaults.vim, and the vimrc_example.vim merely sources that,
so on that point there has been no change for me. OTOH, the openSUSE
admins' /etc/vimrc contains a lot of stuff about whose utility I have
a lot of doubts, here is an example:
" Changed default required by SuSE security team--be aware if
enabling this
" that it potentially can open for malicious users to do harmful things.
set nomodeline
I don't agree with the SUSE admins' theory that Vim's sandbox
mechanism is insufficient everywhere including on a single-user
installation like mine. However, my own-compiled Vim looks for its
system vimrc at the default location which is $VIM/vimrc so that does
not disturb me either. BTW, "SuSE" with lowercase u isn't the
company's name anymore since 2003 so maybe this policy isn't
up-to-date anymore.
Best regards,
Tony.
--
--
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.
