   (run-hooks 'doom-post-init-hook))
 
 (defun doom|run-all-startup-hooks ()
-  "Run all startup Emacs hooks. Meant to follow running Emacs in a vanilla
-session, with a different init.el, like so:
+  "Run all startup Emacs hooks. Meant to be executed after starting Emacs with
+-q or -Q, for example:
 
   emacs -Q -l init.el -f doom|run-all-startup-hooks"
   (run-hooks 'after-init-hook 'delayed-warnings-hook


(autoload 'use-package "use-package-core" nil 'macro)

(after! use-package-core
  (add-to-list 'use-package-deferring-keywords :after-call nil #'eq)


;;; core-packages.el --- package management system -*- lexical-binding: t; -*-

;; Emacs package management is opinionated, and so am I. I've bound together
;; `use-package', `quelpa' and package.el to create my own, rolling-release,
;; lazily-loaded package management system for Emacs.
;;
;; The three key commands are:
;;
;; + `bin/doom install` or `doom//packages-install': Installs packages that are
;;   wanted, but not installed.
;; + `bin/doom update` or `doom//packages-update': Updates packages that are
;;   out-of-date.
;; + `bin/doom autoremove` or `doom//packages-autoremove': Uninstalls packages
;;   that are no longer needed.
;;
;; This system reads packages.el files located in each activated module (and one
;; in `doom-core-dir'). These contain `package!' blocks that tell DOOM what
