Windows 7 gvim cannot use more than one plugin at a time

junegunn / vim-plug

:hibiscus: Minimalist Vim Plugin Manager

https://junegunn.github.io/vim-plug/

MIT License

34.24k stars 1.93k forks source link

Windows 7 gvim cannot use more than one plugin at a time #402

Closed Tabby- closed 8 years ago

Tabby- commented 8 years ago

Happening on most commands, am not getting any errors. Works fine if I only use one plugin, it just wont process anything if I uncomment more than one Plug '___' line.

More than 1 plugin: asfa 1 plugin: dsf

starcraftman commented 8 years ago

@Tabby- Peculiar. If you do :PlugUpdate 1 with all the Plug lines enabled does it work?

If that works, please tell me where you got...

GVim
Git (i.e. GitSDK, msysgit...)
python version and vendor (i.e. python.org, activestate...)

Tabby- commented 8 years ago

@starcraftman :PlugUpdate 1 works perfectly, thanks.

Vim first from https://tuxproject.de/projects/vim/, and then from https://bintray.com/veegee/generic/vim_x64, neither of which worked.
Git version 2.7.0 64 bit from http://www.git-scm.com/
I have version 3.5.1 and 2.7.11 of python installed, both 64 bit versions from https://www.python.org/

starcraftman commented 8 years ago

@Tabby- Alright, I am testing this in one of my VMs but this seems like a standard setup I've run before so it should work. I can only test 32bit in my VM but I don't see architecture as being a problem. I did notice this new step for 2.7.11 regarding regedit. May have to document this annoying registry issue.

To confirm local setup can you do the following commands, report any errors:

:echo system('git --help')
:python import platform; print platform.python_version()
:python3 import platform; print(platform.python_version())

Tabby- commented 8 years ago

@starcraftman the second command came up with an error, so I tried the registry change and it now comes up with 2.7.11 as expected, all of the vim-plug commands now seem to be working as intended. Thanks.

starcraftman commented 8 years ago

@Tabby- Quite a nuisance, just found the bug. Seems a bit disappointing they made a release with this.

Also, when both python 2 and python 3 present, we prefer the 2 interface because a lot of other plugins are not 3 compatible. Hence why it didn't work when 3 installed. So if you had removed 2 entirely, it probably would have worked, though other plugins might not have.

I think we might have to document this, might have been the cause of other Windows python bugs.