aboutsummaryrefslogtreecommitdiff
path: root/tests/test-keyboard-compat-setup.el
Commit message (Collapse)AuthorAgeFilesLines
* fix(keyboard-compat): register terminal arrow-key setup on tty-setup-hookCraig Jennings29 hours1-0/+8
| | | | The arrow-key decodings ran on emacs-startup-hook, but input-decode-map is terminal-local and a daemon's startup hook fires once with no tty. So every emacsclient -t frame opened later missed the decodings, and arrow keys broke in terminal frames. tty-setup-hook runs for each new tty frame, daemon and non-daemon alike. The GUI half already frame-scopes itself. A test pins the hook so a regression back to emacs-startup-hook fails.
* test(keyboard-compat): cover the terminal and GUI setup functionsCraig Jennings2026-05-121-0/+101
`cj/keyboard-compat-terminal-setup` (8 `define-key`s into `input-decode-map` for arrow escape sequences) and `cj/keyboard-compat-gui-setup` (18 `M-<UPPER>` → `M-S-<lower>` translations into `key-translation-map`) had no tests — that's the bulk of the module's executable lines. I added `tests/test-keyboard-compat-setup.el` — 7 ERT tests that `let`-bind those keymaps to fresh copies, stub `env-terminal-p` / `env-gui-p`, and check the decode/translate entries land, with completeness loops over all 8 arrow sequences and all 18 Meta-Shift letters, plus the gate-off boundary for each. `cj/--icon-blank-in-terminal` was already covered. `lookup-key` on an ESC-prefixed string can return a meta-prefix event count instead of nil, so the "no-op when not on a terminal" case asserts the keymap is still empty rather than checking individual lookups.