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

Issue when activating https://raw.github.com/LucHermitte/vim-clang/master/vim-clang-addon-info.txt #127

Closed byzhang closed 11 years ago

byzhang commented 11 years ago

My vimrc call VAM like the following: fun SetupVAM() let c = get(g:, 'vim_addon_manager', {}) let g:vim_addon_manager = c let c.plugin_root_dir = expand('$HOME', 1) . '/.vim/vim-addons' let &rtp.=(empty(&rtp)?'':',').c.plugin_root_dir.'/vim-addon-manager' let g:vim_addon_manager.debug_activation = 1 if !isdirectory(c.plugin_root_dir.'/vim-addon-manager/autoload') execute '!git clone --depth=1 git://github.com/MarcWeber/vim-addon-manager ' \ shellescape(c.plugin_root_dir.'/vim-addon-manager', 1) endif call vam#ActivateAddons(["https://raw.github.com/LucHermitte/vim-clang/master/vim-clang-addon-info.txt"], {'auto_install' : 1}) " Also See "plugins-per-line" below endfun call SetupVAM()

In the first run, the vim-clang and its dependencies are cloned to the local, no errors happened. But in the second run, it reports the following error: I turned on the debug_activation, but still don't show me the details of "some reason".

Error detected while processing function SetupVAM..vam#ActivateAddons: line 129: E605: Exception not caught: These plugins could not be activated for some reason: ['https://raw.github.com/LucHermitte/vim-clang/master/vim-clang-addon-info.txt']

MarcWeber commented 11 years ago

Error detected while processing function SetupVAM..vam#ActivateAddons: line 129: E605: Exception not caught: These plugins could not be activated for some reason: ['https://raw.github.com/LucHermitte/vim-clang/master/vim-clang-addon-info.txt']

I forgot which ways of installing by addon-info.json we support. (If you care I'll look it up).

Try 'github:/LucHermitte/vim-clang' instead of the https url. The dependencies should still work.

Consider commenting about your C/C++ support solution experiences here: http://vim-wiki.mawercer.de/wiki/languages/c-cpp-like.html

ZyX-I commented 11 years ago

I forgot which ways of installing by addon-info.json we support. (If you care I'll look it up).

The way referenced here works. Problem is that OP wants not to install something, but to use already installed plugin with the same string. I guess all we need is better error message and documentation update that user must not use http:// URLs in the vimrc and only use it for installation.

byzhang commented 11 years ago

@MarcWeber, I guess you meant "github:LucHermitte/vim-clang", but it seems doesn't auto install the dependencies. @ZyX-I , yes, it's easier to maintain if we could use the same string to install and to activate installed plugins.

byzhang commented 11 years ago

@MarcWeber , and it also doesn't activate installed dependencies.

MarcWeber commented 11 years ago

It does not for historical reasons. The addon-info file should be called "addon-info.json" today. Now because you tried intsalling by 'github:' name, the name does not match the deprecated ways to name the addon-info.json file.

There are two possible fixes: 1) Install by name, latest version vim-clang can be installed by VAM-known-repositories. 2) ask the author to rename the addon-info file to addon-info.json

Because 1) works I think we're done? If not reopen

byzhang commented 11 years ago

When I used call vam#ActivateAddons(["vim-clang"], {'auto_install' : 1}) The error is: svn: E170000: Unrecognized URL scheme for 'git://github.com/LucHermitte/vim-clang'

shell returned 1

byzhang commented 11 years ago

It's because this line in vim-addons/vim-addon-manager-known-repositories/db/scmsources.vim let scm['vim-clang'] = {'type': 'svn', 'url': 'git://github.com/LucHermitte/vim-clang'} It works after I change to let scm['vim-clang'] = {'type': 'git', 'url': 'git://github.com/LucHermitte/vim-clang'}

Could you fix it?

MarcWeber commented 11 years ago

Excerpts from byzhang's message of Mon Jul 01 02:08:29 +0200 2013:

Could you fix it? Done 7 hours ago. That's what I meant by "latest version". I agree that my wording was not clear.