Question: Is it possible to checkout a revision (SHA) instead of tag

[junegunn]

Question: Is it possible to checkout a revision (SHA) instead of tag

[seb-mueller]

Just in case someone still comes across this issue. This now seems to be resolved , there is an commit option along with branch and tag as described in https://github.com/junegunn/vim-plug#plug-options

Below is an example on how checkout a specific commit (SHA) only :

Plug 'kassio/neoterm', { 'commit': '6389a24c42572020e0978600e632fd90094fe642' }

README.md says that

Freezing plugin version with commit hash

vim-plug does not allow you to freeze the version of a plugin with its commit hash. This is by design. I don't believe a user of a plugin should be looking at its individual commits. Instead, one should be choosing the right version using release tags or versioned branches (e.g. 1.2.3, stable, devel, etc.)

Plug 'junegunn/vim-easy-align', '2.9.2'

If the repository doesn't come with such tags or branches, you should think of it as "unstable" or "in development", and always use its latest revision.

If you really must choose a certain untagged revision, consider forking the repository.

[junegunn]

Thanks @opennota. Yes, I'm still skeptical about supporting it. I've never once needed to do so, although I don't use too many plugins. But I'm open to suggestions and discussions. If you need the feature now, you can always go for NeoBundle :)

[wikimatze]

Hi @junegunn, I'm comming right from NeoBundle :) and find your manager doing exactly what I want without any further features. The following sentence:

If the repository doesn't come with such tags or branches, you should think of it as "unstable" or "in > development", and always use its latest revision.

stick in my head and it is right, if the latest master state of a project isn't stable, you should fork it. So updating the README and/or creating a vim-plug.txt documentation file would clear things up. Don't know if I can help you with this?

[junegunn]

@wikimatze Thanks, glad to hear that you agree with the idea. Currently vim-plug is distributed as a single vim file (https://raw.github.com/junegunn/vim-plug/master/plug.vim) to put in autoload directory. So although having vim-plug.txt would be nice, it will add another step to the installation process, and I'm not sure if it's really worth it. If you think the README page needs further clarification, let me know. I want to keep the page as short as possible.

[vyp]

(Sorry for the bump, ignore. This is just to help future readers. But imo this ticket should be closed with wontfix label or similar.)

There is however the :PlugSnapshot command documented in the README, for those who haven't read it fully and came here first, like me.