Reset more state on doom/module initialization

Makes `doom/reload` a little more reliable and the side effects of
`doom-initialize`/`doom-initialize-modules` a little more deterministic.
This commit is contained in:
Henrik Lissner 2019-04-09 03:43:13 -04:00
parent defd60b24b
commit 31eb845f6b
No known key found for this signature in database
GPG key ID: 5F6C0EA160557395
3 changed files with 22 additions and 5 deletions

View file

@ -33,11 +33,11 @@ Runs `doom-reload-hook' afterwards."
(when (getenv "DOOMENV")
(doom-reload-env-file 'force))
(doom-reload-autoloads force-p)
(setq load-path doom-site-load-path)
(let (doom-init-p)
(doom-initialize))
(with-demoted-errors "PRIVATE CONFIG ERROR: %s"
(doom-initialize-modules 'force))
(let (doom-init-modules-p)
(doom-initialize-modules)))
(when (bound-and-true-p doom-packages)
(doom/reload-packages))
(run-hook-wrapped 'doom-reload-hook #'doom-try-run-hook))