 
 ;; We load evil-collection ourselves for these reasons:
 ;;
-;; 1. To truly lazy load it. Some of its modules, like the elisp-mode and
-;;    buff-menu ones are loaded immediately, because Emacs loads them
-;;    immediately, pulling in all of evil-collection and sometimes other
-;;    packages.
+;; 1. To truly lazy load it. Some of its modules, like
+;;    evil-collection-{elisp-mode,buff-menu} are loaded immediately, because
+;;    Emacs loads their packages immediately, which pulls in all of
+;;    evil-collection (and other packages with it, sometimes).
 ;; 2. This ensures a predictable load order, versus lazy loading using :defer or
 ;;    :after-call. This means users can use (after! org ...) and be sure that
 ;;    their changes will override evil-collection's.

  "A list of `evil-collection' modules to ignore. See the definition of this
variable for an explanation of the defaults (in comments). See
`evil-collection-mode-list' for a list of available options.")

;; This has to be defined here since evil-collection doesn't autoload its own.
;; It must be updated whenever evil-collection updates theirs.

    (pdf pdf-view)
    popup
    proced
    process-menu
    prodigy
    profiler
    python
