Excerpts from James's message of Fri Feb 14 02:34:13 +0000 2014:
> 1) To be simple and easy to use rather than featureful.
What for? Vim is featureful, not simple, you are happily using it by
ignoring some features.
> 2) To focus more on dynamicly and quickly finding and trying out
> plugins on the fly, instead of storing a static list in the vimrc.
Those are exactly the goals of VAM, too. (Providing useful features).
What is complicated about "storing static" lists?
Its fast to restart Vim and its the only clean way to have a
reproducable setup - thus you want it - because unloading plugins
doesn't make sense for many reasons (yes, I've tried !)
Otherwise both NeoBundle, VAM (and vundle in some way) support loading
at runtime.
:VAMActivate always
1) checks whether dir is there
2) if not, installs the package
3) activates it
(regardless when its called)
It is the most simple interface I've seen - and it already provides
completion. What else do you need ?
Except a search with more info - and we should collaborate on that
Vundle users want such, too - we all want it. Why have 10 solutions?
2 days ago I've reviewed all issues in Vundle - which also "wants to be
simple" - and I've found about 3 issuen telling the author about simple
bugs that vimfiles should be used instead of .vim - so I guess there are
additional important properties such as "being maintained" well - which is
why I'd like to collaborate with all parties to see whether we can join
to delegate sub tasks - so that we all have less work - and still can
make everyone happy.
> Vim-pi looks like it will be pretty useful, but probably outside the
> scope of Vizardry. Vizardry uses a github api search to find plugins,
> which allows for the simplicity of having github do all the heavy
> lifting while working very well for all my (and hopefully other
> people's) use cases.
And what if you want to one of drchips plugins? You'll not even know
they exist then. Maybe its what you want.
I think the community needs more than "a github search" - a lot of
people found the old Sander's snipmate - which never got updated - had
tons of forks - and people join irc having problems - I got tired of
telling them "fix is to use upstream at github/garbas"- which is why I
started vim-wiki.mawercer.de (to tell people about upstream solutions).
Let me try your search (one example is enough to illustrate my point):
:Scry snipmate
0: msanders/snipmate.vim <<<<<<<<<<<< OUTDATED !!!
(snipMate.vim aims to be a concise vim script that implements some of
TextMate's snippets features in Vim. )
1: honza/vim-snippets <<<<<<<<<<<< this will point to garbas/snipmate, so
you might be lucky ..
(vim-snipmate default snippets (Previously snipmate-snippets))
[... 3 more matches below, they are unimportant ]
Upstream garbas/snipmate does not even appear.
:Scry commenting
does miss my plugin github.com/MarcWeber/vim-addon-commenting which I
consider to be the most simple yet somewhat featureful solution
(which is what you like: being simple)
Do you think those two samples is enough to point out that
a simple github search does eventually miss the jewels ?
Maybe thats what you want. Otherwise join vim-wiki.mawercer.de (You'll
get commit access if you want)
If you search for snipmate there you'll be pointed to:
http://vim-wiki.mawercer.de/wiki/topic/text-snippets-skeletons-templates.html
which should provide a nice overview (the more people join, the more
comprehensive it'll get)
Of course you can do whatever you want - its only my point of view (as
always)
Marc Weber
[3]:
2: robhudson/snipmate_for_django
(Django snippets for SnipMate, the excellent Vim plugin)
3: kaichen/vim-snipmate-ruby-snippets
(Some snippets of vim' plugin snipMate.vim.)
4: jamescarr/snipmate-nodejs
(Various snippets for developing node.js from vim)
5: evidens/vim-twig
(Twig syntax highlighting, snipMate, etc.)
6: theunraveler/Drupal-Snippets-for-Vim
(Provides a bunch of autocomplete snippets for Vim using snipMate.)
7: mklabs/vim-backbone
(Lightweight bag of Vim utilities for Backbone - snipmate snippets,
templates and omnicompletion)
8: bonsaiben/bootstrap-snippets
(Twitter Bootstrap snippets for vim-snipmate)
9: juhasz/drupal_sublime-snippets
(Drupal snippets for Sublime Editor, converted from Vim snipMate
drupal-snippets)
--
--
You received this message from the "vim_dev" 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
---
You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
