Henrik Lissner 45a66cda60 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.		2022-09-10 19:11:03 +02:00
..
make	refactor!: restructure Doom core	2022-07-30 22:41:13 +02:00
autoloads.el	refactor: move file-name-handler-alist hack to early-init	2022-09-06 22:55:46 +02:00
ci.el	feat!(cli): load project .doomrc instead of ci.el	2022-08-07 19:43:28 +02:00
compile.el	refactor: deprecate doom-private-dir for doom-user-dir	2022-08-14 20:43:35 +02:00
doctor.el	fix: ensure module state is in scope for modulep!	2022-09-10 19:11:03 +02:00
env.el	feat(cli): deny XDG, Wayland, Sway, + socket envvars	2022-09-10 18:36:24 +02:00
help.el	refactor!: restructure Doom core	2022-07-30 22:41:13 +02:00
info.el	refactor!: restructure Doom core	2022-07-30 22:41:13 +02:00
install.el	refactor: deprecate doom-private-dir for doom-user-dir	2022-08-14 20:43:35 +02:00
make.el	feat(cli): generalize 'doom make codeowners'	2022-08-07 19:43:28 +02:00
packages.el	fix(cli): nativecomp error writing to read-only fs	2022-09-10 12:08:16 +02:00
run.el	refactor!: restructure Doom core	2022-07-30 22:41:13 +02:00
sync.el	refactor!(cli): remove 'doom {refresh,re}'	2022-09-06 23:08:55 +02:00
test.el	refactor!: restructure Doom core	2022-07-30 22:41:13 +02:00
upgrade.el	fix(cli): more future resistant 'doom upgrade'	2022-07-31 00:58:36 +02:00