feature request VAM prefix (suffix) and or gui? #25

Open
MarcWeber opened this Issue Jan 27, 2011 · 5 comments

Projects

None yet

4 participants

@MarcWeber
Owner

(1)
13:32 Hi. Some suggestions to VAM: prefix all vam commands with vam to have an easier command completion.

(2)
I'd find it useful to have a simple browser for name and summaries of addons.
Maybe keeping an eye on the vim version and the addon version (maybe impossible right now).
13:33 Autoloading at startup could be easier, maybe a minimal gui or generated config without editing vimrc every time.
13:33 Finally, thank you very much, it's awesome useful. I think about dropping gentoo ebuilds and completely manage vim addons by VAM.

comments (1)
See d38e93d

comments (2)
VAM prefix? There are two commands: UpdateAddons and ActivateAddons.
You don't need more. I hope you can remember those two.
If you still want VAM.. (which is more to type - So I'd suggest :ActivateAddonsVAM so that you can use tab completion on two instead of 4 chars) .. you can copy paste those lines into your .vimrc file.

How do other think about those topics?
I'll keep this open for now and I"m not going to work on any of those for the given reasons.

@Silex
Collaborator
Silex commented Jan 29, 2011

About 2), I think it'd be possible to write a ruby/bash/python/vim script that uses vim-addon-manager-known-repositories and generate a file containing plugin's name and plugin documentation url (even tho that cannot be made for some plugins that aren't on github or vim.org).

From there it's easy to imagine piping it in a browser etc... however I don't see any real need for it because this is exactly what http://www.vim.org/scripts/script_search_results.php?order_by=creation_date&direction=descending does already. Just use that page and check the script you're interesting in, then install them in VAM.

Maybe what could be done is put this url somewhere in the doc tho.

@bubbl3gum
13:33 Autoloading at startup could be easier, maybe a minimal gui or generated config without editing vimrc every time.

Something like :ActivateAddons -p (p for persistent) to automatically add the newely activated Addon to vimrc would be very convenient in my opinion.

@MarcWeber
Owner

Excerpts from bubbl3gum's message of Thu Mar 31 11:22:26 +0200 2011:

13:33 Autoloading at startup could be easier, maybe a minimal gui or generated config without editing vimrc every time.

Something like :ActivateAddons -p (p for persistent) to
automatically add the newely activated Addon to vimrc would be very
convenient in my opinion.

I've been slowly switching my mind about this.
If - how should it work?

Use a simple regex to add an item at the ActivateAddon(["foo"]) list?

Require a special layout such as

let vam_managed_names = [
\ ]

call ActivateAddons(vam_managed_names)

Then add name there?

put the list of names into a file (increases IO load).
Could be provided by third party plugin easily.

I know that ZyX cares much about style :)
So let's wait till he comments about it.

Marc Weber

@cheater
cheater commented May 20, 2012

I have to vote for the GUI idea, it would be great to have a list of plugins which you could search, and from which you could get the "call vam#ActivateAddons(['foo'])" line to easily put into your vimrc.

If you go on with an external list for storing what addons should be active, please make sure doing "call vam#ActivateAddons" from vimrc still works.

@MarcWeber
Owner

#146 is related, alternative names prefixed by VAM are there now (but not documented yet)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment