-
-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Invalid git URI when calling :PlugStatus or :PlugClean #12
Comments
Thanks for the report. Strangely, I can't seem to reproduce the problem. I even tried with your configuration, but it worked fine. So, you mean, those commands fail only when the current directory is a git repository? " So this fails
:cd ~/.vim | PlugStatus
" But this works
:cd ~ | PlugStatus Am I right? |
As I understand, it takes URI from It could possibly be side effect of another plugin or some peculiar system settings. I'll try to experiment some more and report back. |
Basically when running execute 'cd '.values(g:plugs)[0].dir
let remote =
\ substitute(
\ split(
\ system('git rev-parse --abbrev-ref HEAD && git config remote.origin.url'),
\ "\n")[-1], 'git:@', '', '')
echom remote
cd - |
It appears to get correct URI for plugin only if I use execute '!cd '.values(g:plugs)[0].dir Otherwise, it will try to call git command on system pwd. |
Hmm, that's interesting. Could you tell me more about your environment so I can further investigate on the issue? (OS, Vim version, shell) |
ArchLinux, kernel 3.13.6-1 |
Okay thanks! I'll try to test it on a similar environment tomorrow. |
Thanks a lot. I'll try some different environment too. |
Okay, I've set up an Arch Linux VM with a similar environment as yours. :cd /tmp
" /tmp
:pwd
" /tmp
:!pwd Have you tried |
Yes, it works! I had my shell set to zsh, actually. Setting it to |
When calling one of those commands,
vim-plug
confuses all plugins URIs with the URI of the current folder.For example, running
PlugStatus
when in~/.vim
(which contains its own git repository) results in this:PlugInstall
andPlugUpdate
work perfectly well.The text was updated successfully, but these errors were encountered: