diff options
| author | Craig Jennings <c@cjennings.net> | 2026-06-06 12:32:59 -0500 |
|---|---|---|
| committer | Craig Jennings <c@cjennings.net> | 2026-06-06 12:32:59 -0500 |
| commit | 7e9ce3c072b41a68350998672a4df3bf9114e41f (patch) | |
| tree | 82d2bb9d3f458536049be895799f29946c881e74 /modules/coverage-core.el | |
| parent | d27fbf1b4e5450184b8564ca422d193647123558 (diff) | |
| download | dotemacs-7e9ce3c072b41a68350998672a4df3bf9114e41f.tar.gz dotemacs-7e9ce3c072b41a68350998672a4df3bf9114e41f.zip | |
fix(signal): register C-; M prefix via canonical helper
The C-; M Signal prefix didn't take effect on a fresh Emacs launch. signal-config.el was the only feature module that bound into cj/custom-keymap directly, wrapped in (with-eval-after-load 'keybindings (when (boundp 'cj/custom-keymap) ...)). The boundp guard turned a load-order miss into a silent no-op, so the binding never landed at startup. A later live-reload always papered over it because keybindings was loaded by then.
I switched to the documented cj/register-prefix-map helper and added (require 'keybindings) at the top, matching every other prefix map. The require guarantees keybindings loads before registration, so the guard is gone.
I verified at a full emacs --batch init.el launch, the actual failing scenario, that C-; M resolves to the signel prefix. I added a contract test asserting the registration, since the boundp guard was robust under unit timings and only failed at full launch.
Diffstat (limited to 'modules/coverage-core.el')
0 files changed, 0 insertions, 0 deletions
