aboutsummaryrefslogtreecommitdiff
path: root/modules/coverage-core.el
diff options
context:
space:
mode:
authorCraig Jennings <c@cjennings.net>2026-06-05 05:43:43 -0500
committerCraig Jennings <c@cjennings.net>2026-06-05 05:43:43 -0500
commitf84f5d7958288b4a7e2fc6ccda07c77a020e0319 (patch)
tree8d8d7ed543be17f262ce4d2a3fc3481d7f29846e /modules/coverage-core.el
parentd2bb83228daf5301dd06732499312ca310ae1940 (diff)
downloaddotemacs-f84f5d7958288b4a7e2fc6ccda07c77a020e0319.tar.gz
dotemacs-f84f5d7958288b4a7e2fc6ccda07c77a020e0319.zip
fix(term): make F9 and F12 reach Emacs inside ghostel buffers
F9 did nothing in an agent buffer: ghostel's semi-char mode forwards every key not in ghostel-keymap-exceptions to the pty, and ghostel-semi-char-mode-map outranks the major-mode map, so the F9-family and F12 bindings I'd put in ghostel-mode-map never fired. The keys went to Claude/the shell, which ignored them. I added the F9 family (in ai-term) and F12 plus C-; (in term-config) to ghostel-keymap-exceptions and rebuilt the semi-char map with ghostel--rebuild-semi-char-keymap. add-to-list updates the list but not the already-built map, so the rebuild is what actually lets the keys through. C-; had the same latent bug for the same reason. Two regression tests assert the keys are in the exceptions and that the rebuilt semi-char map no longer forwards them. I also corrected the spec note that claimed binding in ghostel-mode-map was enough (true for vterm, wrong for ghostel) and codified the gotcha.
Diffstat (limited to 'modules/coverage-core.el')
0 files changed, 0 insertions, 0 deletions