Chadmacs/init.el at master · Borderliner/Chadmacs · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
;;; init.el --- Chadmacs main loader -*- no-byte-compile: t; lexical-binding: t; -*-
;;
;; Author: Borderliner
;; URL: https://github.com/Borderliner/Chadmacs
;;
;;; Commentary:
;;
;; Thin orchestrator. Real configuration lives in lisp/chadmacs-*.el modules.
;; Bootstrap order:
;;
;;   1. early-init.el       -> GC tuning, Elpaca bootstrap, paths under var/
;;   2. chadmacs-core       -> sane defaults, persistence, optimisation
;;   3. chadmacs-ui         -> frame, theme, modeline, dashboard, which-key
;;   4. chadmacs-completion -> vertico / consult / corfu / cape / embark
;;   5. chadmacs-editing    -> undo, sessions, snippets, smartparens, ...
;;   6. chadmacs-tools      -> projectile, magit, flycheck, eglot, envrc, ...
;;   7. chadmacs-org        -> org, buffer-terminator
;;   8. chadmacs-navigation -> treemacs, dirvish, popper, ghostel
;;   9. chadmacs-help       -> helpful
;;  10. <lang/*>            -> language-specific (rust, etc.)
;;  11. custom.el           -> user-local overrides (gitignored)
;;
;; No leader key. Keybindings live where their owning package lives, on
;; standard pure-Emacs prefixes: `C-x' for built-ins, `C-c <letter>' for
;; user/package commands, `M-g' for goto, `M-s' for search, `C-h' for
;; help. `which-key' makes every prefix self-documenting.
;;
;;; Code:

(add-to-list 'load-path (expand-file-name "lisp" user-emacs-directory))
(add-to-list 'load-path (expand-file-name "lang" user-emacs-directory))

(require 'chadmacs-core)
(require 'chadmacs-ui)
(require 'chadmacs-completion)
(require 'chadmacs-editing)
(require 'chadmacs-tools)
(require 'chadmacs-org)
(require 'chadmacs-navigation)
(require 'chadmacs-help)

;; Language modules are enabled per-user in custom.el (gitignored).
;; A pre-populated template with every available language is installed
;; on first launch by `create-or-load-custom-file' (see chadmacs-core).
;; This keeps the upstream init.el free of personal selections, so
;; pulling new Chadmacs versions never produces merge conflicts.

(create-or-load-custom-file)

(provide 'init)
;;; init.el ends here