diff options
| author | Craig Jennings <c@cjennings.net> | 2026-06-13 00:56:38 -0500 |
|---|---|---|
| committer | Craig Jennings <c@cjennings.net> | 2026-06-13 00:56:38 -0500 |
| commit | 5d7633c74dbe47690eb837946ca9f17453dbe13f (patch) | |
| tree | 2a14fb2aee3db7fa37f268ef0b57b2c60e0fb095 /modules/system-defaults.el | |
| parent | 72bcdede09ddecc21a6ac7e0c97b2e80ecef6ba1 (diff) | |
| download | dotemacs-5d7633c74dbe47690eb837946ca9f17453dbe13f.tar.gz dotemacs-5d7633c74dbe47690eb837946ca9f17453dbe13f.zip | |
fix(keys): revert 936c9fd2, restore the M-S- launcher bindings
936c9fd2 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.
Diffstat (limited to 'modules/system-defaults.el')
0 files changed, 0 insertions, 0 deletions