On Wed, Dec 31, 2008 at 8:11 AM, Tony Mechelynck wrote: > > On 31/12/08 07:48, Matt Wozniski wrote: >> On Tue, Dec 30, 2008 at 1:14 PM, Daniel Schierbeck wrote: >>> I hope there's a simple workaround. >> >> Sorry I couldn't come up with the solution earlier on IRC, but after >> some sleep, I think I see what's going wrong here. 10 to 1 says >> you're using a 'nix distro that installs a default system-wide vimrc, >> and that system-wide vimrc does 'filetype on', meaning that >> $VIMRUNTIME/filetype.vim gets loaded before your ~/.vimrc ever adds >> your runtimepaths onto the default runtimepath, and only the ftdetect >> directories in the default runtimepath are used. I'm not really sure >> what to do about that, though... > > You could use > :filetype off > :filetype on > after changing your 'runtimepath', which would first unset the > filetype-detection autocommands, and then re-source filetype.vim to set > them again with the new 'runtimepath' (invoking your ftdetect/*.vim > scripts).
Yes, then that seems like the best solution. I hadn't thought that :filetype off | filetype on would reload filetype.vim, but now that I think about it it makes sense. So, that's the solution, then. ~Matt --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
