History

Henrik Lissner ce49f94bbe Remove doom-bootstrap system (will be replaced)		2017-05-20 18:40:13 +02:00
..
app
completion	disable ivy magic slash non-match action	2017-05-19 05:45:11 -04:00
feature	Improve rule for flycheck popups	2017-05-19 17:07:32 +02:00
lang	Remove doom-bootstrap system (will be replaced)	2017-05-20 18:40:13 +02:00
private	Remap evil-record-macro in tabulated-list-mode popup	2017-05-20 18:40:13 +02:00
tools	tools/gist: make gists private by default	2017-05-17 21:07:58 +02:00
ui	General cleanup & refactor; update TODO	2017-05-19 17:21:52 +02:00
README.md

README.md

Modules

Modules are made up of four parts, all of which are optional:

modules/category/submodule/
modules/category/submodule/config.el
modules/category/submodule/packages.el
modules/category/submodule/autoload.el
modules/category/submodule/autoload/*.el

config.el

The main configuration file and the first loaded when the module is activated (using doom! or require!).

packages.el

How modules inform DOOM what packages to install and where from. These should be declarative, pure and idempotent. That means running them directly should have no side-effects (besides affecting the variables doom-modules and doom-packages) and whose results should alway be deterministic.

By default, packages are retrieved from ELPA. Otherwise, a MELPA-style recipe can determine how to fetch it:

;; from modules/tools/rotate-text/packages.el
(package! rotate-text :recipe (:fetcher github :repo "debug-ito/rotate-text.el"))

Other modules' packages.el files can be depended on, through depends-on!:

;; from modules/feature/file-templates/packages.el
(depends-on! :feature snippets)

autoload.el OR autoload/*.el

These are scanned by doom/reload-autoloads, whose functions are lazily-loaded, given that they're marked with an ;;;###autoload cookie:

;; from modules/lang/org/autoload/org.el
;;;###autoload
(defun +org/toggle-checkbox ()
  (interactive)
  [...])

;; from modules/lang/org/autoload/evil.el
;;;###autoload (autoload '+org:attach "lang/org/autoload/evil" nil t)
(evil-define-command +org:attach (&optional uri)
  (interactive "<a>")
  [...])

Other files

My convention for extra configuration files is a + prefix, e.g. modules/feature/version-control/+git.el. These are not automatically loaded, and must be loaded manually with load! from within config.el:

;; from modules/feature/version-control/config.el
(load +git)

What modules aren't

Modules loosely take after Spacemacs' notion of layers, but are not intended to be interchangeable. Their purpose is almost purely organizational.

Use featurep! to check for module availability:

;; from modules/lang/go/packages.el
(when (featurep! :completion company)
  (package! company-go))

;; from modules/lang/go/config.el
(def-package! company-go
  :when (featurep! :completion company)
  [...])