On Fri, Oct 25, 2013 at 9:17 AM, tooth pik <[email protected]> wrote:
>
> This is one example of confusion created by vimrc_example. I think it's
> cute and all, but believe it should never be loaded in its entirety and
> most especially never recommended as Best Use to newbies.
>
> > Another way would be to delete the autocommands in the vimrcEx
> > group,
>
> > augroup vimrcEx
> > au!
> > augroup END
>
> another ugly hack
toothpick et al:
You make some good points about the example vimrc file, but there is
enough good stuff in there that I plan to continue recommending it to
newbies. Maybe we can compromise:
:runtime vimrc_example.vim
is good advice for real newbies, but as soon as they run into trouble (as
Aaron did) it means they care enough to follow your advice.
Another advantage of using the example file is that you benefit if it
gets updated. How many of us have really crufty personal vimrc files? I m
pretty sure that, at one point, the Red Hat package maintainers copied an
example vimrc file (and maybe modified it) as their system vimrc file, then
let it get very stale. (They did other things that bothered me ...)
Because vim is flexible by design (:help design-flexible) we should
also say what to do in case Aaron chooses not to take your advice. I do
not see anything hacky about deleting the single offending autocommand:
:au! vimrcEx FileType
HTH --Benji Fisher
--
--
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.
