update subcommand does not actually update package #501
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
zplug updatecommand does not work correctly for gh-r, I guess. It only rewrites INDEX, but leave executable file old.Assuming that we have already installed peco/peco according to Wiki,
and we update it by
zplug update peco/peco. However our command version won't change.In case of update, the replacement of executable in
__zplug::utils::releases::index()do nothing as a result. For example, the variablebinariesaboutpeco/pecocontains the following;the first
pecois the version currently in use, so nothing happens bymv -f "$binaries[1]" "$cmd". (mv -f "peco" "peco").I fix code to push newly downloaded file to binaries as priority.