beside that, I wish vim.org could provide other script type like autoload , class , plugin , ftplugin, compiler, ... etc value to "script type" field when uploading new scripts.
On Feb 22, 6:35 pm, Cornelius <[email protected]> wrote: > Hi folks, > > it's such pain to install plugins from vim.org , because every plugin use > its own way to distribute..... and vim.org > doesn't provide any API for application to retrieve structural data.. like > JSON... > > I'm here because I wrote Vimana vim script manager , which detects plugin > content to decide how to install automatically > > http://github.com/c9s/Vimana > > but it's not very reliable because there are only 'plugin', 'color scheme', > 'utility', 'syntax' ... in the script type field of plugin on vim.org. > it's hard to detect specific script content. but most mainstream plugin > could be installed by Vimana. > > Here is a way to make script auto-installable from > Vimana.http://c9s.blogspot.com/2010/01/vim-make-your-script-auto-installable... > > Thanks > /Cornelius/ -- You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php
