Emacs Config

You can validate your Emacs configuration by running the included validate.sh script, which checks init-*.el modules for balanced parentheses, correct provide endings, and consistent use-package declarations to prevent startup failures.

Emacs init file errors are often caused by unbalanced parentheses, missing provide forms, or conflicting keybindings. You can check for them automatically by running the validation script across your init-*.el modules to detect these structural issues.

Yes, you can check for conflicting keybindings across multiple Emacs modules. The validation process analyzes all init-*.el files to detect override risks and minimize startup confusion caused by duplicate key assignments.

Yes, the Emacs config validation works with cross-platform guards. It analyzes OS-specific guards in init-platform.el to ensure reliable behavior and consistent startup across macOS, Linux/WSL, and Windows environments.

You can validate a specific Emacs module by passing the module name as an argument to the validation script, such as running validate.sh init-ai. This targets the individual file for structural and syntax checks.

Using shell scripts for Emacs dotfiles validation limits checks to structural rules like balanced parentheses, provide forms, and keybinding conflicts. It does not execute the elisp code, so it cannot catch runtime errors or dynamic loading failures.