Vim for Windows has a default _vimrc with the following contents:
" Vim with all enhancements
source $VIMRUNTIME/vimrc_example.vim
" Use the internal diff if available.
" Otherwise use the special 'diffexpr' for Windows.
if &diffopt !~# 'internal'
set diffexpr=MyDiff()
endif
function MyDiff()
...
endfunction
To my humble opinion, the initial part in quite confusing.
" Vim with all enhancements
source $VIMRUNTIME/vimrc_example.vim
First, the comment and the filename don't match well. "Why does the file is named 'example,' but the comment implies it is a set of things I would probably like to keep," the user would ask himself/herself.
I would say the best solution is simply change the comment to something neutral:
" Example _vimrc
source $VIMRUNTIME/vimrc_example.vim
And second, because of such a comment, some users, especially the ones who just started to learn and configure the editor, may skip, overlook, or don't take serious enough the filename, which is vimrc_example.vim.
They have read a comment and they see some file is included... What would they expect? Right, they would expect something defaults.vim there! "Hey, this is probably a file will all the basic configurations I need. Thanks!" And then such a user may set textwidth to e.g. 80 and notice that sometimes it is 78 instead...
" ...because of the following line, of which he/she is not aware.
autocmd FileType text setlocal textwidth=78
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub.
Triage notifications on the go with GitHub Mobile for iOS or Android.
![]()
Closed #8844.
Hmm, but what about just change the comment to something neutral, so that the comment will not imply anything about whether the settings in vimrc_example are recommended or not?
" Example _vimrc
source $VIMRUNTIME/vimrc_example.vim
This is a key part of what I talked about.