1.1 KiB
1.1 KiB
Modules
Modules are made up of three (optional) parts:
- A
config.el
file, automatically loaded when the module is loaded (through@doom
or@require
). It uses@def-package
calls (thin wrappers arounduse-package
) to configure packages. - A
packages.el
file filled with@package
and@depends-on
declarations. These are purely declarative macros. They populatedoom-packages
anddoom-modules
for the package management system. - Either an
autoload.el
file orautoload/*.el
files, which are scanned bydoom/reload-autoloads
and lazily loaded.
The convention for extra config files is to prefix them with a plus
(+git.el
). These are not automatically loaded.
What modules aren't
Modules loosely take after Spacemacs' notion of layers, but are not meant to be interchangeable. Their purpose is almost purely organizational.
The only exception to this are completion modules. Other modules make
no assumptions about which completion modules are enabled. If company
isn't installed, company plugins will silently refuse to install, and
their respective @def-package
blocks will be ignored.