2.1 KiB
2.1 KiB
SKILL: Dotemacs Configuration (Universal Literate Note)
- Overview
- Phase A: Demand (PRD)
- Phase B: Blueprint (PROTOCOL)
- Phase D: Build (Implementation)
- Phase E: Chaos (Verification)
Overview
The Dotemacs project represents the "Operating System" configuration. It transforms Emacs into the primary computing tool by leveraging modular, literate Org-mode files that tangle into a high-performance environment.
Phase A: Demand (PRD)
1. Purpose
Define the requirements for a modular, optimized, and fully documented Emacs environment.
2. User Needs
- Modularity: Split the monolithic `emacs.org` into functional modules (core, ui, gtd, ai, etc.).
- Literate Mandate: Every significant setting must be justified and explained in prose.
- Integration: Seamless connectivity with `opencortex`, `org-roam`, and `org-gtd`.
- Bootstrapping: Fast startup using `early-init.el` and lazy-loading.
3. Success Criteria
TODO Monolithic modularization completion
TODO Standardize all paths to ~/memex/
TODO Ensure Org 10.0-pre bootstrap compatibility
TODO Document all major package configurations
Phase B: Blueprint (PROTOCOL)
1. Architectural Intent
The configuration is structured as a collection of feature-specific Org files that tangle into the `~/.emacs.d/` directory.
2. Semantic Interfaces
(defun dotemacs-tangle-module (module-name)
"Tangels a specific module Org file into its .el counterpart.")
(defun dotemacs-verify-load-path ()
"Ensures all Memex paths are correctly registered in the load-path.")
Phase D: Build (Implementation)
The implementation is distributed across the `emacs-*.org` files in `projects/dotemacs/`.
Core Module Tangle
;; Example tangle header
;; #+PROPERTY: header-args:elisp :tangle ~/.emacs.d/lisp/core.el
Phase E: Chaos (Verification)
Verification involves `M-x benchmark-init` and ensuring zero warnings during the byte-compilation phase.