wrote:
> > Agree, so why not simply provide .vim files, which does not need to be
> > decompressed at all?
>
> > I usually distribute my scripts in plain .vim format. Trying to integrate
> > everything into one single .vim isn't quite difficult.
>
> > For Windows Vim user, it would be much better too see something end with
> > .vim than .vba, (change it to .vima would be great.)
>
> Here are some reasons:
>
> * syntax files should go into syntax directories
> * plugin/ vs autoload/ -- putting everything into one file means
> slower startup
> * ftplugin/ and plugin/ -- sometimes plugins work with multiple
> filetypes (ex. my AutoAlign, which has a common portion and separate,
> typically small, sections for various filetypes). Its cleaner than
> using a lot of autocmds.
>
> I'm sure I could come up with more reasons if pressed.
>
You missed one huge one:
* A good plugin should come with good documentation which integrates
with the Vim :help. Vimball archives allow you to put the .txt help
file in the same archive, and will even (if I remember correctly)
automatically run :helptags after copying it to the appropriate
location.
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
No comments:
Post a Comment