Hi Chris!
On Di, 07 Jun 2011, Chris Brennan wrote:
> * 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 ">".
That is the correct one. But it uses the short form of formatoptions, fo
to set it:
#v+
chrisbra@host:~$ grep fo+ local/share/vim/vim72/ftplugin/mail.vim
setlocal fo+=tcql
#v-
This is obviously for vim 7.2, but that options hasn't changed since then.
> /usr/share/vim/vim73/ftplugin/mailaliases.vim:15:setlocal comments=:#
> commentstring=#\ %s formatoptions-=t formatoptions+=croql
This is no mail filetype, but only sourced for /etc/aliases
> /usr/share/vim/vim73/ftplugin/mailcap.vim:16:setlocal comments=:#
> commentstring=#\ %s formatoptions-=t formatoptions+=croql
Same for this one. This is sourced for mailcap files, e.g. /etc/mailcap.
> 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,
No.
> 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?
Actually, I think the runtime files are executed in the order they are
defined in the runtimepath setting. But since you have been using the
after directory, your settings were applied after all other settings
have been set.
regards,
Christian
