On 18.09.15 09:47, Christian Brabandt wrote: > > On Fr, 18 Sep 2015, Erik Christiansen wrote: > > > So, in .vimrc, something vaguely like: > > > > au BufNewFile,BufRead ~/Desktop/mutt-* call Set_for_mutt() > [...] > > You don't need that autocommand. Simply create a file > ~/.vim/ftplugin/mail.vim and put all mutt related stuff there and > add an entry :filetype plugin to your .vimrc
Thanks Christian, for the alternative implementation, but I don't need ~/.vim/ftplugin/mail.vim when I can equally easily do it in .vimrc. > Keeps your .vimrc cleaner. Keeping everything vim-related in one config file is _waaaay_ cleaner. Cluttering the filesystem with a swarm of files seems untidy, and is a good way to leave config behind when moving to a new installation/OS upgrade, I figure. I have folding enabled in .vimrc, and the mutt stuff has its own section: " Alt-O & Alt-I between files, just as ^O & ^I retrace move history: " Convenience: " Cursor Appearance and behaviour: " Custom Mode Settings: " Date Insertion: " Encryption: " Filename-dependent autocommands: " Folding: " Function Keys: " Mutt: " Numbered Lists: " Paste " Path: " Quickfix: " Spellchecking: Now there's no need to hunt around amongst all sorts of files, wondering where stuff is configured - it's configured in the config file! While ftplugin doubtless has some use cases, somewhere, I suspect that it's a bit like those tabs things in vim. I still find them a step backwards from just using buffers and the :bu commands. (Admittedly mapped, so <A-b> does :bu) Erik
