fix: doom/reload not restoring initial envvars
'doom/reload' should and cannot regenerate the user's envvar file, because it's not typically running in your shell, but it should reload your existing envvar file. Fix #5399 Ref #5344
This commit is contained in:
parent
b58fad7eee
commit
0381c7868e
1 changed files with 2 additions and 3 deletions
|
@ -76,9 +76,8 @@ package list, and lastly, reloads your private config.el.
|
|||
Runs `doom-after-reload-hook' afterwards."
|
||||
(interactive)
|
||||
(mapc #'require (cdr doom-incremental-packages))
|
||||
(doom--if-compile (format "%S sync" doom-bin)
|
||||
(let ((doom-reloading-p t)
|
||||
doom-env-file)
|
||||
(doom--if-compile (format "%S sync -e" doom-bin)
|
||||
(let ((doom-reloading-p t))
|
||||
(doom-run-hooks 'doom-before-reload-hook)
|
||||
(doom-initialize 'force)
|
||||
(with-demoted-errors "PRIVATE CONFIG ERROR: %s"
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue