Dear James. James McCoy - 06.07.17, 03:09:23 CEST: > > 3) Vim wordwraps by default now. I wonder about how many admins will > > break config files with long lines accidently by that new default > > behaviour. > I don't see anything in defaults.vim that changes 'textwidth' from its > default value of 0, so I'm not sure what you're experiencing here. > Maybe ":verbose set textwidth?" will help next time you run into this > issue.
Finally I found this one. It is: % grep filetype /usr/share/vim/vim82/defaults.vim " Use the default filetype settings, so that mail gets 'tw' set to 72, " Revert with ":filetype off". filetype plugin indent on It triggers for example for editing Git commit messages. And no, I don't like command line output to be wrapped in there. Thus I did: % cat /etc/vim/vimrc.local […] " 'set mouse=' in /etc/vim/vimrc.local is ignored unless ~/.vimrc exists " https://bugs.debian.org/864074 runtime! defaults.vim let g:skip_defaults_vim = 1 […] :filetype plugin indent off […] Let's hope no other unexpected configuration changes creep in by using defaults.vim – otherwise I may reconsider having 'runtime! defaults.vim' in 'vimrc.local', so far I am not sure it gives me any substantial benefits over just using my own configuration. I am also not sure whether I really like incremental search so far. Let's see. I am still not convinced that the current handling of 'vimrc.local' is Debian user friendly. Ciao, -- Martin
