doomemacs/lisp
Henrik Lissner b121c5e1c6
refactor(lib): provide doom-libs as subfeatures
This allows us to load them via doom-require. Why not use normal
features? Because Doom's libraries are designed to be loaded as part of
Doom, and will openly rely on Doom state if needed; this is a contract I
want to enforce by ensuring their only entry points are through
`doom-require` or autoloading.

I will add them to the rest of the libraries later.

Site-node: this also adds Commentary+Code to the comment headings, as I
want a space to use that space to describe the library, when I get
around to it.
2022-09-08 00:20:26 +02:00
..
cli fix(cli): void-variable doom-dir on 'doom doctor' 2022-09-06 23:31:01 +02:00
lib refactor(lib): provide doom-libs as subfeatures 2022-09-08 00:20:26 +02:00
doom-cli.el refactor(lib): provide doom-libs as subfeatures 2022-09-08 00:20:26 +02:00
doom-editor.el refactor: deprecate doom-etc-dir for doom-data-dir 2022-08-14 20:43:35 +02:00
doom-keybinds.el refactor: deprecate featurep! for modulep! 2022-08-14 20:43:35 +02:00
doom-lib.el feat(lib): add doom-{require,load} 2022-09-07 23:19:37 +02:00
doom-modules.el fix: remove use-package-font-lock-keywords reference 2022-09-06 22:55:46 +02:00
doom-packages.el tweak: disable ahead-of-time native compilation 2022-09-06 22:55:47 +02:00
doom-projects.el fix: validate fd --version output 2022-09-07 01:48:37 +02:00
doom-start.el refactor: move gcmh config to doom-start 2022-09-06 22:55:47 +02:00
doom-ui.el refactor: deprecate doom-private-dir for doom-user-dir 2022-08-14 20:43:35 +02:00
doom.el release(modules): 22.09.0-dev 2022-09-07 01:48:37 +02:00
packages.el bump: :core 2022-09-06 22:55:47 +02:00