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 | 707472b5afebd8c4ec0fced007ef26ef188148a7 (patch) | |
| tree | 28fa40f3f8c316d03afdd66d9a4596693353fa89 /tests/test-prog-python--format-wiring.el | |
| parent | 518d6f7a656c76dfdbae7951a9476baa149450ed (diff) | |
| download | dotemacs-707472b5afebd8c4ec0fced007ef26ef188148a7.tar.gz dotemacs-707472b5afebd8c4ec0fced007ef26ef188148a7.zip | |
fix(keys): revert 5bfd74fd, restore the M-S- launcher bindings
5bfd74fd 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 'tests/test-prog-python--format-wiring.el')
0 files changed, 0 insertions, 0 deletions