diff options
| author | Craig Jennings <c@cjennings.net> | 2026-06-05 05:43:43 -0500 |
|---|---|---|
| committer | Craig Jennings <c@cjennings.net> | 2026-06-05 05:43:43 -0500 |
| commit | 2da53f4cbcc5a325f8f9ae4f7cc6eede64af2628 (patch) | |
| tree | c666e1fd69c0fd6500758f001059d19ba3d2a16e /modules/prog-python.el | |
| parent | a46d21d54d33637bcc14090082ba4716b08d8767 (diff) | |
| download | dotemacs-2da53f4cbcc5a325f8f9ae4f7cc6eede64af2628.tar.gz dotemacs-2da53f4cbcc5a325f8f9ae4f7cc6eede64af2628.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/prog-python.el')
0 files changed, 0 insertions, 0 deletions
