Skip to content
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

vim-plug downloads old commit of distinguished.vim from Lokaltog/vim-distinguished repo #257

Closed
kazarmy opened this issue Jul 14, 2015 · 5 comments
Labels

Comments

@kazarmy
Copy link

kazarmy commented Jul 14, 2015

On my computer, the latest vim-plug (commit 69d6c9d) downloads an old commit of colors/distinguished.vim from the Lokaltog/vim-distinguished repo when it should be downloading the latest commit. Apparently, the commit downloaded is Lokaltog/vim-distinguished@395d32b (I say "apparently" because I have not checked whether there is a later commit that results in an identical distinguished.vim). There were no previous downloads of the plugin.

I'm using gVim 7.4.11 from the Cream project on Windows 8.1. The installed version of git is 2.4.0.windows.2.

I have only the following in my vimrc:

call plug#begin('~/vimfiles/bundle')
Plug 'Lokaltog/vim-distinguished'
call plug#end()

Apart from vim-plug, no other customizations have been made to gVim.

@junegunn
Copy link
Owner

Plug 'Lokaltog/vim-distinguished', { 'branch': 'develop' }

:)

@kazarmy
Copy link
Author

kazarmy commented Jul 15, 2015

Fyi, Vundle has different behavior in this case.

Thanks for the answer! :)

@junegunn
Copy link
Owner

Vundle does not support branches and only picks up the default one. vim-plug, on the other hand, allows you to choose any branch and verifies if the right branch is being used. So it can be confusing if the default branch can change over time, so it defaults to master when not specified.

@kazarmy
Copy link
Author

kazarmy commented Jul 15, 2015

Thanks for the info. I think it's best if it was also stated in the FAQ.

@junegunn
Copy link
Owner

Thanks. Will see if there's a better way to address the default branch issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants