search

MarcWeber / vim-addon-manager

manage and install vim plugins (including their dependencies) in a sane way. If you have any trouble contact me. Usually I reply within 24 hours
Other
660 stars 59 forks source link

give script homepage URL in :AddonsInfo #57

Closed stardiviner closed 12 years ago

stardiviner commented 12 years ago

I find that only download URL are available, but no homepage URL. for example: vim.org only has download URL. and github.com plugins only has git:.... In terminal, Click on git:... will not open it. Sometimes, I will find many similar name plugins, I need to find out which one is exactly which I want. like miniexplr and miniexplorer. and more others. I hope VAM can give homepage so that I can open them to figure out which one is which I want.

MarcWeber commented 12 years ago

Excerpts from stardiviner's message of Sun Feb 19 09:18:57 +0100 2012:

Sometimes, I will find many similar name plugins, I need to find out which one is exactly which I want. like miniexplr and miniexplorer. and more others. I hope VAM can give homepage so that I can open them to figure out which one is which I want.

Do you want to contribute the code? I can tell what to do. Should be no more than about 7 lines. Then :AddonInfo will show the homepage.

Marc Weber

ZyX-I commented 12 years ago

All dictionaries with repository information must have vim_script_nr key if plugins were posted to vim.org. Just use custom search engines in your browser to be able to like something like vs 1000 and be redirected to http://www.vim.org/scripts/script.php?script_id=1000.

stardiviner commented 12 years ago

=> On [2012-02-19 04:06:25 -0800]: Marc Weber Said:

Excerpts from stardiviner's message of Sun Feb 19 09:18:57 +0100 2012:

Sometimes, I will find many similar name plugins, I need to find out which one is exactly which I want. like miniexplr and miniexplorer. and more others. I hope VAM can give homepage so that I can open them to figure out which one is which I want.

Do you want to contribute the code? I can tell what to do. Should be no more than about 7 lines. Then :AddonInfo will show the homepage. Yes I want. But I do not know how to contribute code. I know a little about this: fork a repo on VAM. then .... (I should learn in github help about push request)

Marc Weber

Reply to this email directly or view it on GitHub: https://github.com/MarcWeber/vim-addon-manager/issues/57#issuecomment-4041496

stardiviner << =>GPG: 5D9F64D8 Twitter: @numbchild http://stardiviner.dyndns-blog.com/author.html

MarcWeber commented 12 years ago

How should it be implemented?

I'd vote for adding this feature to the code providing the list of "known addons". Adding a simple key "homepage" should be enough because all key value pairs are displayed anyway (at the moment).

Now there are some scripts which have both: a www.vim.org and github "homepage". What to do? Use a list and show both?

Should we change the internal design so that the addon list contains a list of sources for each plugin?

eg addons = { 'snipmate' : [ github_source, www.vim.org_source ]}

then a policy could be to not "drop sources" but only sort them. Then each addon source can have it own homepage url also.

VAM would always pick first source when installing plugins.

Ideas?

as a quick hack only 'homepage' key could be assigned only showing one.

stardiviner commented 12 years ago

=> On [2012-02-19 05:09:46 -0800]: Marc Weber Said:

How should it be implemented?

I'd vote for adding this feature to the code providing the list of "known addons". Adding a simple key "homepage" should be enough because all key value pairs are displayed anyway (at the moment).

Now there are some scripts which have both: a www.vim.org and github "homepage". What to do? Use a list and show both?

Should we change the internal design so that the addon list contains a list of sources for each plugin?

eg addons = { 'snipmate' : [ github_source, www.vim.org_source ]}

then a policy could be to not "drop sources" but only sort them. Then each addon source can have it own homepage url also.

VAM would always pick first source when installing plugins.

Ideas?

as a quick hack only 'homepage' key could be assigned only showing one. You're right. Maybe use vim.org homepage is ok. Because almost all plugins will upload to there even though they have another homepage on github or others. but we still can figure the exactly plugin through vim.org page's author, description or more.

Reply to this email directly or view it on GitHub: https://github.com/MarcWeber/vim-addon-manager/issues/57#issuecomment-4041805

stardiviner << =>GPG: 5D9F64D8 Twitter: @numbchild http://stardiviner.dyndns-blog.com/author.html

ZyX-I commented 12 years ago

Could you check out new better-addon-info branch?

ZyX-I commented 12 years ago

No need to have any “homepage” keys if all you want is to observe script page on vim.org.

MarcWeber commented 12 years ago

Excerpts from ZyX-I's message of Sun Feb 19 14:34:11 +0100 2012:

Could you check out new better-addon-info branch? Make two changes, then merge: a) add a comment that this information should eventually be generated in VAM-kr

b) replace elseif by if only. Then github sources having a script_nr will show both urls

Thanks for your work. Looks like we can close the issue for now then.