fix: autoloads load order in profile bootstrap
Package autoloads should be assembled in the order they're
installed/built, so that dependencies between them (such as the case
where geiser-* packages call geiser-activate-implementation, which is
defined in geiser.el's autoloads file -- see #7472) don't throw errors.
Fix: #7472
Amend: 87f6f7ab91
This commit is contained in:
parent
87f6f7ab91
commit
f9c2397a3c
1 changed files with 2 additions and 2 deletions
|
@ -449,8 +449,8 @@ Defaults to the profile at `doom-profile-default'."
|
||||||
(defun doom-profile--generate-package-autoloads ()
|
(defun doom-profile--generate-package-autoloads ()
|
||||||
(doom-autoloads--scan
|
(doom-autoloads--scan
|
||||||
(mapcar #'straight--autoloads-file
|
(mapcar #'straight--autoloads-file
|
||||||
(seq-difference (hash-table-keys straight--build-cache)
|
(nreverse (seq-difference (hash-table-keys straight--build-cache)
|
||||||
doom-autoloads-excluded-packages))
|
doom-autoloads-excluded-packages)))
|
||||||
doom-autoloads-excluded-files
|
doom-autoloads-excluded-files
|
||||||
'literal))
|
'literal))
|
||||||
|
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue