emenel/doomemacs
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Don't delete autoloads file

Browse source 
Turns out to be more error prone. Better to just ignore the existing one
when force-initializing Doom.
This commit is contained in:
Henrik Lissner 2018-06-10 19:07:37 +02:00
parent 8d4971d02b
commit f144691157
No known key found for this signature in database
GPG key ID: 5F6C0EA160557395
1 changed files with 1 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

7
core/core-packages.el
View file

@ -276,15 +276,10 @@ to least)."
(when (or force-p (not doom-init-p)) (when (or force-p (not doom-init-p))
;; Set this to prevent infinite recursive calls to `doom-initialize' ;; Set this to prevent infinite recursive calls to `doom-initialize'
(setq doom-init-p t) (setq doom-init-p t)
;; Delete autoloads file so we can regenerate them later.
(when force-p
(mapc #'doom-delete-autoloads-file
(list doom-autoload-file
doom-package-autoload-file)))
;; `doom-autoload-file' tells Emacs where to load all its autoloaded ;; `doom-autoload-file' tells Emacs where to load all its autoloaded
;; functions from. This includes everything in core/autoload/*.el and all ;; functions from. This includes everything in core/autoload/*.el and all
;; the autoload files in your enabled modules. ;; the autoload files in your enabled modules.
(unless (doom-initialize-autoloads doom-autoload-file) (unless (or force-p (doom-initialize-autoloads doom-autoload-file))
(doom-ensure-core-directories) (doom-ensure-core-directories)
(doom-ensure-same-emacs-version-p) (doom-ensure-same-emacs-version-p)
(doom-ensure-packages-initialized force-p) (doom-ensure-packages-initialized force-p)