dotemacs/tests/test-launcher-meta-shift-keys.el, branch main My Emacs configuration https://git.cjennings.net/dotemacs/atom?h=main 2026-06-13T05:56:38+00:00 fix(keys): revert 4a1ecf64, restore the M-S- launcher bindings 2026-06-13T05:56:38+00:00 Craig Jennings c@cjennings.net 2026-06-13T05:56:38+00:00 urn:sha1:a631938c95ee7974a1d5489ad3aba713c4f0a0d5 4a1ecf64 rebound eww/elfeed/calibredb from M-S-e/r/b to the uppercase Meta events M-E/M-R/M-B, on the theory that the keyboard emits the uppercase event and the lowercase-shift spec never matched. It was wrong. keyboard-compat.el installs a key-translation-map entry (M-E -> M-S-e, etc.) in GUI frames, so the original M-S- bindings did reach the launchers. Binding M-E directly while that translation stayed in place rewrote the keypress to the now-unbound M-S-e, breaking all three in GUI on the next restart. The audit and the review missed it because they checked key-binding, which ignores key-translation-map, and the running daemon still held the pre-fix bindings as stale state. This restores M-S-e/r/b, deletes the key-binding-only test that certified the broken config, and reclassifies the task as not-a-bug. The real problem, that these chords are dead outside GUI, is the subject of the keybinding-console-safety spec. fix(keys): bind eww/elfeed/calibredb launchers to the uppercase Meta event 2026-06-12T15:07:09+00:00 Craig Jennings c@cjennings.net 2026-06-12T15:07:09+00:00 urn:sha1:4a1ecf647270e49da1a185f4d52c2553e1fedba8 Meta+Shift+<letter> emits the uppercase event (M-E/M-R/M-B), so the M-S-e/M-S-r/M-S-b :bind specs on lowercase letters were never reached by the keychord and the three launchers were dead. Rebind them to M-E/M-R/M-B. Three ERT tests assert each chord resolves to eww, cj/elfeed-open, and calibredb respectively.