Open spapanik opened 3 months ago
As there are plugins that clobber the
latest
orstable
or similar tags, they fail at update (for examplecatppuccin/nvim
).
It's not clear why they fail to update. Can you be more specific? You're not specifying the tag
in the Plug
command, so they shouldn't affect the git pull
process.
My global git configuration automatically pulls and prunes tags, which is the configuration that makes sense for the repos that I'm working with.
I found an installation that I haven't manually force pulled catpuccin. This is the error I'm getting:
x catppuccin:
From https://github.com/catppuccin/nvim
! [rejected] stable -> stable (would clobber existing tag)
When I go to ~/.local/share/nvim/plugged/catppuccin
and I delete the offending tag, it updates fine.
My global git configuration automatically pulls and prunes tags
Can you show me the config?
The two parts in the config are:
[remote "origin"]
tagOpt = --tags
[fetch]
pruneTags = true
Thanks for the clarification. I think this is a very rare case; an unorthodox use of tags (they should be maintaining stable
branch instead) combined with a non-default global git option of yours.
vim-plug has been extremely stable and is not expected to change much in the near future, so I suggest that you add --force
to your local copy of plug.vim, instead we add an option that few people will use.
As there are plugins that clobber the
latest
orstable
or similar tags, they fail at update (for examplecatppuccin/nvim
). The solution is for me to go to~/.local/share/nvim/plugged/
, find the offending plugin, and do agit pull --force
. I was wondering if there is the option to do it from :PlugUpdate, and if not I would like to make a feature request for this.