>> It makes me wonder: Does it ever serve a purpose to use >> ~/.vim/ftplugin/ instead of ~/.vim/after/ftplugin/ ? > > The only purpose I can think of would be to _replace_ a global > filetype plugin with either your own or a more recent version from > vim.sf.net. By adding the appropriate code to a plugin in > ~/.vim/ftplugin, you can prevent the code in the global plugin from > being executed. (See ":help ftplugin-overrule" and ":help > ftplugin".) > > Otherwise, whether you're making changes to the settings made by a > global filetype plugin or creating your own filetype plugin for a > file type for which there is no global filetype plugin, you might as > well just put it in ~/.vim/after/ftplugin.
Thanks.. I think it would have been more logical to source ~/.vim/ftplugin as "after", though, and then if you wanted the pre-sourcing, you could stick it in ~/.vim/before/ftplugin. /Erik --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
