fix: ensure module state is in scope for modulep!
Otherwise, doom-module-from-path (and modulep!) would fail to detect the module they're in, or at least, modulep! would incorrectly return nil, even for enabled modules. This issue is what would've caused the package list or the doctor to include/consider packages in disabled modules or behind disabled flags.
This commit is contained in:
parent
ce0e3a04b6
commit
45a66cda60
3 changed files with 14 additions and 7 deletions
|
@ -156,7 +156,9 @@ return NULL-VALUE."
|
|||
(insert-file-contents file nil 0 256)
|
||||
(if (re-search-forward (format "^;;;###%s " (regexp-quote (or cookie "if")))
|
||||
nil t)
|
||||
(let ((load-file-name file))
|
||||
(let* ((load-file-name file)
|
||||
(doom--current-module (doom-module-from-path file))
|
||||
(doom--current-flags (doom-module-get (car doom--current-module) (cdr doom--current-module) :flags)))
|
||||
(eval (sexp-at-point) t))
|
||||
null-value)))
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue