Remember why we load customizations so late
So I don't have to ponder on this again the next time I see this …
This commit is contained in:
parent
9132364fb7
commit
2e2b208c23
6
init.el
6
init.el
@ -2926,6 +2926,12 @@ eventuelly be set to nil, however)."
|
|||||||
|
|
||||||
;; * Load customizations
|
;; * Load customizations
|
||||||
|
|
||||||
|
;; We do this late in init.el to really make sure that whatever happened previously can be
|
||||||
|
;; overwritten by user customizations. This might not be strictly necessary, as
|
||||||
|
;; `custom-set-variables' and friends should only install user customizations, without evaluating
|
||||||
|
;; them … but let's better be safe than sorry). One could even think about adding this to
|
||||||
|
;; `db/run-init', but this might be too late.
|
||||||
|
|
||||||
(when (file-exists-p custom-file)
|
(when (file-exists-p custom-file)
|
||||||
(load-file custom-file))
|
(load-file custom-file))
|
||||||
|
|
||||||
|
|||||||
Loading…
Reference in New Issue
Block a user