New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PlugInstall is trying to clone into a path composed of cygwin + windows paths concatenated together? #713
Comments
Yes. |
I use Windows x64 Gvim and Cygwin shell and utilities. I'm not particularly attached to cygwin other than it took awhile to get it working the way I want and I've been using it a long time. I suppose I should switch to the linux subsystem, but I haven't really had time to figure it out. |
It's cool, I can use msys2 git just for vim-plug. I have it on my system, but I disabled it by removing it from my path. I can just add it to the path before running PlugUpdate or whatever. |
Did it work? |
Yeah, it worked. So, I guess the issue is that vim-plug is incompatible with Cygwin git. I was going to try and fix it, but I don't think it's currently possible to determine if git is the cygwin git. If you could determine that, then you could run cygpath on the paths to convert them to cygwin paths before passing them to git. At least I think that would fix it. |
What's the output of |
Cygwin git:
Msys2 git:
|
Cygwin git doesn't have |
Oh, you think the process of elimination would be enough? Which cygpath? I'm not sure what you mean. |
You can't mix up the cygpath and git on each msys2/cygwin installation. |
Well there is no cygpath for msys2, is there? |
There is one each on my system from https://git-for-windows.github.io/, mingw, and cygwin. |
I'm having a bizarre problem with some part of vim-plug concatenating paths together, and it's preventing the plugins from installing:
Any ideas where this extra "/home/Matt/dotfiles/vimfiles/plugged/" string is coming from?
Well, the git is cygwin git, so I guess vim-plug is presuming I'm using Windows git?
The text was updated successfully, but these errors were encountered: