My Emacs configuration https://git.cjennings.net/dotemacs/atom?h=main 2026-05-25T23:29:32+00:00 2026-05-25T23:29:32+00:00 Craig Jennings c@cjennings.net 2026-05-25T23:29:32+00:00 urn:sha1:9b1d563cad3a1484d294896ddbf09689d95b3b5b custom-file points at a throwaway temp file so Customize edits never persist — deliberate, since config lives in Elisp, but silent. A user who clicks "Save for Future Sessions" loses the edit on exit with no hint. I advise custom-save-all (the chokepoint both customize-save-variable and the Customize button funnel through) with a one-shot :before warning that explains the discard and points at the Elisp init files. The advice removes itself after firing, so it warns once per session, and the body never runs at load, so startup stays quiet. 2026-05-25T22:00:15+00:00 Craig Jennings c@cjennings.net 2026-05-25T22:00:15+00:00 urn:sha1:c83b13ea891d034190b7b8582ce45f2bfaf84f40 system-defaults.el had no coverage for its settings, only its functions (in test-system-defaults-functions.el) and the vc-follow-symlinks default. I added three settings smoke tests: custom-file is redirected to a temp trashbin rather than the repo, backups land under user-emacs-directory/backups, and the minibuffer GC hooks are actually wired onto the minibuffer hooks. I pulled the sandbox loader the vc-follow-symlinks test had inline into tests/testutil-system-defaults.el so both files share one copy. The backups test clears cj/backup-directory before loading — it's a defvar, so once an earlier test loads the module it keeps that first sandbox path and won't recompute, which made the assertion fail until I forced the recompute.