From 2305b9532fd8a6384d80e90e0cb93e17e3f8022f Mon Sep 17 00:00:00 2001 From: Craig Jennings Date: Fri, 22 May 2026 15:07:32 -0500 Subject: docs(languages): tighten elisp coding and testing rules Two audit fixes. elisp.md's "prefer Write over Edits" advice was tool-specific. It's now framed around intent: edit cohesively, then run paren and byte-compile checks immediately, whatever the editing mechanism. elisp-testing.md gains batch-mode reproducibility (emacs --batch as source of truth, no interactive state, no blocking prompts), state isolation (temp user-emacs-directory, explicit load-path, declared deps only), and byte-compile/native-comp warning handling, with native-comp gated on availability and kept opt-in. --- languages/elisp/claude/rules/elisp.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'languages/elisp/claude/rules/elisp.md') diff --git a/languages/elisp/claude/rules/elisp.md b/languages/elisp/claude/rules/elisp.md index e641058..ea9bdc2 100644 --- a/languages/elisp/claude/rules/elisp.md +++ b/languages/elisp/claude/rules/elisp.md @@ -72,4 +72,4 @@ Then `(require 'foo-config)` in `init.el` (or a config aggregator). - A PostToolUse hook runs `check-parens` and `byte-compile-file` on every `.el` save - If it blocks, read the error — don't retry blindly -- Prefer Write over repeated Edits for nontrivial new code; incremental edits accumulate subtle paren mismatches +- Edit cohesively, then verify parens/byte-compile right away. For nontrivial Elisp, land a function as one complete, coherent change rather than dribbling it in over many tiny partial edits — incremental fragments accumulate subtle paren mismatches. Run the paren-balance and byte-compile checks immediately after editing, whatever editing mechanism the environment uses. -- cgit v1.2.3