fix: all packages seen as disabled

In v3, doom-module data is stored in symbol plists, but in v2, it's
stored in a hash table. Some v3 code snuck into 45a66cd, which made Doom
try to read module data from plists that hadn't been initialized yet, so
Doom could no longer see your module settings.

Fix: #6769
Amend: 45a66cda60
This commit is contained in:
Henrik Lissner 2022-09-10 20:00:12 +02:00
parent 7a2fa1e313
commit c80fa2efdf
No known key found for this signature in database
GPG key ID: B60957CA074D39A3

View file

@ -463,11 +463,10 @@ ones."
(let (doom-packages) (let (doom-packages)
(doom--read-packages private-packages nil 'noerror)) (doom--read-packages private-packages nil 'noerror))
(cl-loop for key being the hash-keys of doom-modules (cl-loop for key being the hash-keys of doom-modules
for plist = (get (car key) (cdr key)) for path = (doom-module-path (car key) (cdr key) packages-file)
for doom--current-flags = (plist-get plist :flags)
for doom--current-module = key for doom--current-module = key
for file = (doom-path (plist-get plist :path) packages-file) for doom--current-flags = (doom-module-get (car key) (cdr key) :flags)
do (doom--read-packages file nil 'noerror))) do (doom--read-packages path nil 'noerror)))
(doom--read-packages private-packages all-p 'noerror))) (doom--read-packages private-packages all-p 'noerror)))
(cl-remove-if-not (cl-remove-if-not
(if core-only-p (if core-only-p