Prevent void-variable errors on 'doom upgrade'
If Doom is up-to-date, certain Doom package state doesn't get initialized for the 'doom update' that occurs directly after, causing these errors.
This commit is contained in:
parent
af63b0eb7a
commit
8d112fdca8
1 changed files with 5 additions and 3 deletions
|
@ -13,9 +13,11 @@ following shell commands:
|
|||
bin/doom refresh
|
||||
bin/doom update"
|
||||
:bare t
|
||||
(and (doom-cli-upgrade doom-auto-accept force-p)
|
||||
(doom-cli-packages-update)
|
||||
(doom-cli-reload-package-autoloads 'force-p)))
|
||||
(when (doom-cli-upgrade doom-auto-accept force-p)
|
||||
(doom-initialize)
|
||||
(doom-initialize-packages)
|
||||
(when (doom-cli-packages-update)
|
||||
(doom-cli-reload-package-autoloads 'force-p))))
|
||||
|
||||
|
||||
;;
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue