* Christian Brabandt <cbli...@256bit.org> [2011-06-07 17:58:50 +0200]:
> I think, the 'l' flag comes from $VIMRUNTIME/ftplugin/mail.vim
>
> In your case, ~/.vim/after/ftplugin/mail.vim just was executed later
> than the mail.vim from the vim runtime directory and happens to also
> change your 'fo' setting, so the verbose did not really help here.
ch...@stewie.xaerolimit.net:~$ grep formatoptions
/usr/share/vim/vim73/ftplugin/mail*
/usr/share/vim/vim73/ftplugin/mail.vim:23:" Set 'formatoptions' to break text
lines and keep the comment leader ">".
/usr/share/vim/vim73/ftplugin/mailaliases.vim:15:setlocal comments=:#
commentstring=#\ %s formatoptions-=t formatoptions+=croql
/usr/share/vim/vim73/ftplugin/mailcap.vim:16:setlocal comments=:#
commentstring=#\ %s formatoptions-=t formatoptions+=croql
ch...@stewie.xaerolimit.net:~$
Here are the three mail files from
/usr/share/vim/vim73/ftplugin/{mail.vim,mailaliases.vim,mailcap.vim}
line 15 in mailaliases.vim and line 16 in mailcap.vim are setting fo+=l,
should I remove it from those files? Or move them locally? Incidentally,
I thought local files took presedence to global files? Or is this a
case of the vim maintainer not doing things as expected and ignoreing
.files?
--
> A: Yes.
> >Q: Are you sure?
> >>A: Because it reverses the logical flow of conversation.
> >>>Q: Why is top posting frowned upon?
