On Mon, Oct 27, 2008 at 5:23 PM, Tony Mechelynck <[EMAIL PROTECTED]> wrote: > > Well, you could create a ~/.vim/after/ftplugin/html.vim (on Unix) or > ~/vimfiles/after/ftplugin/html.vim (on Windows), and similarly for > whatever filetype the *.inc files are detected as having, with the > single line: > > setlocal fo+=r > > Create the directories if they don't yet exist. You can do this from > within Vim, using for instance, on Unix: > > :!mkdir -pv ~/.vim/after/ftplugin > > or, on Windows, this can give errors (which can be neglected) if the > directories already exist: > > :!md $HOME/vimfiles > :!md $HOME/vimfiles/after > :!md $HOME/vimfiles/after/ftplugin > > This has the advantage (on Windows) that it uses whatever Vim sets $HOME > to even if the HOME environment variable is unset outside of Vim. > > > Best regards, > Tony.
Thanks, but what I meant was that it doesn't seem like I should need a workaround at all. Somewhere vim is applying custom formatoptions to php files. Since vim is smart enough to determine that a .inc file should have filetype=php if it starts with <?php, shouldn't it apply the custom formatoptions as well in those cases? To me, the current behavior seems unexpected. I'm happy to file a bug report if others agree. Ian --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
