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

Documentation: installation with vim-plug to get the latest release #2974

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Documentation: installation with vim-plug to get the latest release #2974

wants to merge 1 commit into from

Conversation

etnnth
Copy link

@etnnth etnnth commented Aug 7, 2020

After installing the plugin with vim-plug i realized that it got the master branch and not the latest release.
I changed the documentation so that the recommended way to install vim-go with vim-plug install the latest release.
I don't really know what could be the solution for Pathogen, Vim 8, I guess we could use :

git clone -b v1.23 https://github.com/fatih/vim-go

but this will requires to be change for each release.
I have no idea how to do the same with Vundle

@bhcleek
Copy link
Collaborator

bhcleek commented Aug 7, 2020

How does plug's tag option work? How does it determine which tag to use?

@etnnth
Copy link
Author

etnnth commented Aug 7, 2020

Documentation on vim-plug says that { 'tag': '*' } option will point to the latest tagged release: https://github.com/junegunn/vim-plug/releases/tag/0.9.0 and line 169-170 of https://github.com/junegunn/vim-plug/blob/master/doc/plug.txt

@bhcleek
Copy link
Collaborator

bhcleek commented Aug 7, 2020

Thanks for contributing!

In general, I try to keep master working well. I use it daily, though there can sometimes be issues.

@teleivo
Copy link

teleivo commented May 5, 2021

@etnnth thank you for this suggestion! Just in case someone else is also experiencing this: when I do a :PlugUpdate plug will always run the Post-update hook and thus reinstall all vim-go related binaries like gopls, guru, ... Even though I am on the latest release of vim-go already. That behavior is unexpected to me. I would expect plug not to do anything if I am already on the latest release. Like it does when I am just relying on master.

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

Successfully merging this pull request may close these issues.

3 participants