On 17 Sep., 13:10, thomas <[EMAIL PROTECTED]> wrote: > > 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)?
The name is of no importance - only the idea behind is. Only if we call it vimball then we would need to use vimball (and not for example .zip, .tar.gz, .tar.bz2 or whatever). > 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? Frankly No. I am working on the modeline plugin for quite a while now and tried several possible solutions. In the end the problem is that almost no filetype plugin sets 'commentstring' (as they should do!!). You can use the modeline plugin without NERD_Commenter (it will use 'commentstring' as fall-back then) but unless you use a programming language which is using /* */ for comments (or Ada who's plug-in set 'commentstring' correctly) you won't have any fun with it. > 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?) That would be far more complicated then using an "else if" in "autoload/modelines.ada" to add another comment plug in. if you send me the patch then I put it into the main distribution. Since autoload is parsed only once, and only when needed, adding another 2 to 3 commenter plugin won't be a problem. > Unless the "bundle" provides some hyper-magic surplus value, IMHO > smaller self-contained plug ins that, for users, are easier to > modify/patch/adapt are in many situations a better solution. Most of the plugin I create are now at least 2 files one of which one is in autoload/ - mostly to speed up load time - especially cygwin can be quite sluggish. BTW: I consider it quite wastefulness NERD_Commenter won't use autoload/ - this means that the plug-in is fully loaded even when I never actually comment out any lines. Also NERD_Commenter uses some doc-install-magic - which does not work on i.E. on VMS. And it is wasteful as well as die documentation is now twice on the hard drive. All in the name of having just one plugin/ file. Bundles are not necessary big: 17.09.2007 11:19 92'426 ___A_________ ada-4.5.0.vba 17.09.2007 11:20 6'450 ___A_________ modelines-2.0.vba 17.09.2007 11:21 10'938 ___A_________ rainbow_parenthsis-3.0.vba 17.09.2007 11:21 16'057 ___A_________ tail-3.0.vba Just there is more then one file inside. i.E. the tail bundle - it comes with a helpful Shell script to start gvim and open some files in tail mode right away. Maybe not "hyper-magic surplus value" but helpful never the less. Martin --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
