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 | f284244126f6b7c1cead9c8cd70ce5385cfecc08 (patch) | |
| tree | 21f4b8c0c31a8df58d370633951516493f1b25b0 /modules/prog-webdev.el | |
| parent | 0c7fccfb251957b022eda0ba5e9b1c7c27102202 (diff) | |
| download | dotemacs-f284244126f6b7c1cead9c8cd70ce5385cfecc08.tar.gz dotemacs-f284244126f6b7c1cead9c8cd70ce5385cfecc08.zip | |
fix(keys): revert 00b22a66, restore the M-S- launcher bindings
00b22a66 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/prog-webdev.el')
0 files changed, 0 insertions, 0 deletions