> " If automatically loading plugins, use these variables to disable > " certain of them. ... > let g:loaded_getscriptPlugin = 0 " getscriptPlugin.vim > " let g:loaded_gzip = 0 " gzip.vim > " let g:loaded_matchparen = 0 " matchparen.vim > " let g:loaded_netrwPlugin = 0 " netrwPlugin.vim > let g:loaded_rrhelper = 0 " rrhelper.vim > let g:loaded_spellfile_plugin = 0 " spellfile.vim > " let g:loaded_tarPlugin = 0 " tarPlugin.vim > " " tohtml.vim (See below) > let g:loaded_vimballPlugin = 0 " vimballPlugin.vim > " let g:loaded_zipPlugin = 0 " zipPlugin.vim > > " tohtml.vim convert a file with syntax highlighting to > HTML > " This one is irritating and cannot be blocked with a simple variable. > " Instead, the TOhtml command must be created, so create a bogus one. > command -range=% TOhtml :echo "TOhtml is not implemented"
If I'm right, the original request was not about technical possibility. It was about the standardization and ease of use. You can see above that this is not the case now: 1. there is no naming scheme for those variables now. The only way how to get their names is to examine the plugin code. This is not nice for the end user. 2. some plugins don't allow any nice way (tohtml is an example above) 3. it's not easy to get a list of all plugins "wanting to be loaded" with a meaningful description of each - see below I can imagine that something like "plugin registration" would help here. Same as each plugin has a code part and doc part now, it would contain something like a registration part (a header with metadata), useful for several purposes: better knowledge what each plugin really is about, who is the maintainer, what is the URL for updates and - the point - how to disable it. Or, better, each plugin should support the same method for disabling itself. The header does not need to be anything complex, just a set of standardized comments at the beginning of plugin code with mandatory and non-mandatory metadata fields. Or in a separate metadata file, that's for discussion. With such metadata we can, for example, generate a list of plugins and call disable methods (or set disabling variables-flags) for some of them in .vimrc And it would be also much easier to find what some plugin is about - even for those which are not a part of any official distro package but downloaded from some site several years ago. My idea is to agree on the metadata set (and format), announce it and mark each plugin at vim.org which follows this policy. This would make the life with plugins easier. Milan -- Milan Vancura, Prague, Czech Republic, Europe --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
