You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Presently, the README instructs to do something like this at the end of setup:
zplug check || zplug install
zplug load
But this only checks for new additions (because it's cheap and fast) and ignores any packages that may have been updated. A similar check to the above for updates could be:
zplug check || zplug install
### NEW WEEKLY REMINDER
if [[ ! -f $TMPDIR/zplugstamp ]]; then
print "Creating new zplug timestamp update tracking file."
touch $TMPDIR/zplugstamp
fi
if (( ( $(date %s) - $(date %s -r $TMPDIR/zplugstamp) ) / 86400 > 7 )); then
print "Detected that it's been over a week since updating your zsh plugins."
print "Run this now to update:\nzplug update; touch $TMPDIR/zplugstamp"
fi
zplug load #--verbose
This uses a timestamped temp file to remind you ~weekly that you haven't updated in a while.
It'd be nice if zplug had a built-in way to do this for users.
The text was updated successfully, but these errors were encountered:
I'm not certain this is a great idea -- building it into zplug -- but I wanted to hear feedback. An alternative is to make users have a calendar reminder to check for editor plugin, OS, Zsh, etc updates. I naturally update my OSs and Emacs packages weekly but don't think to update my Zshs regularly, and I should.
Could also do this as a cron job that emails weekly if there are updates (as I've relied on from Yum in the past)
Presently, the README instructs to do something like this at the end of setup:
But this only checks for new additions (because it's cheap and fast) and ignores any packages that may have been updated. A similar check to the above for updates could be:
This uses a timestamped temp file to remind you ~weekly that you haven't updated in a while.
It'd be nice if zplug had a built-in way to do this for users.
The text was updated successfully, but these errors were encountered: