> So what do you think? Well, I'm no vim developer but read this list nevertheless from time to time. Frankly speaking, I do not fully understand what this is about. Why do you want a new name for files distributed in vba format other than vba (or vimball)?
Besides, I personally prefer the finer granularity of vim's plugins over Emacs's modes. Eg latex-suite (which is another name) is an excellent package but it does a lot of things I don't need/want, which is why I eventually uninstalled it. Bundled plugins have a tendency to take over vim. An example of this would be your modelines bundle that wants user to use a specific commenter plugin. (BTW couldn't this be achieved with a simple abbreviation? BTW2 why don't you define a user configurable variable that contains an ex command that is run on the line containing the modeline which would allow users to use the comment plugin they like?) Unless the "bundle" provides some hyper-magic surplus value, IMHO smaller self-contained plugins that, for users, are easier to modify/patch/adapt are in many situations a better solution. Just my 2c :-) Regards, Thomas. --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
