Fix custom{,theme-}set-faces!, again
custom-theme-set-faces! depends on doom-theme's previous-theme property being non-nil to determine if the theme has been set (and if so, apply its changes immediately), but at startup custom-enabled-themes is empty, so it was never non-nil. Fixes #5009 Fixes #5000
This commit is contained in:
parent
8492e9ba93
commit
4397f0123f
1 changed files with 1 additions and 1 deletions
|
@ -629,7 +629,7 @@ windows, switch to `doom-fallback-buffer'. Otherwise, delegate to original
|
||||||
(prog1 (funcall orig-fn theme no-confirm no-enable)
|
(prog1 (funcall orig-fn theme no-confirm no-enable)
|
||||||
(when (and (not no-enable) (custom-theme-enabled-p theme))
|
(when (and (not no-enable) (custom-theme-enabled-p theme))
|
||||||
(setq doom-theme theme)
|
(setq doom-theme theme)
|
||||||
(put 'doom-theme 'previous-themes last-themes)
|
(put 'doom-theme 'previous-themes (or last-themes 'none))
|
||||||
(doom-run-hooks 'doom-load-theme-hook))))))
|
(doom-run-hooks 'doom-load-theme-hook))))))
|
||||||
|
|
||||||
|
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue