diff options
| author | Craig Jennings <c@cjennings.net> | 2026-05-12 12:53:11 -0500 |
|---|---|---|
| committer | Craig Jennings <c@cjennings.net> | 2026-05-12 12:53:11 -0500 |
| commit | 0bbd09338215699863b826fee13deabdb1e409b3 (patch) | |
| tree | 961858c03355d1af2c348f3076e05088a6ee12c3 /tests/test-keyboard-compat-setup.el | |
| parent | e764dfd4a5e70e4956ad61b12869cea7f54d95d1 (diff) | |
| download | dotemacs-0bbd09338215699863b826fee13deabdb1e409b3.tar.gz dotemacs-0bbd09338215699863b826fee13deabdb1e409b3.zip | |
fix(ai-vterm): make F9 toggle the agent from inside an agent buffer
vterm binds `<f1>`..`<f12>` to `vterm--self-insert`, so a plain `<f9>` typed while point is in an agent buffer goes to the terminal program instead of the global toggle. That's invisible most of the time — you press F9 from another window — but it bites when the agent buffer is the only window in the frame, because there's nowhere else to press it from.
I re-bound the F9 family in `vterm-mode-map` (via `with-eval-after-load 'vterm`) so that `<f9>`, `C-<f9>`, and `M-<f9>` reach `cj/ai-vterm`, `cj/ai-vterm-pick-project`, and `cj/ai-vterm-pick-buffer` from there too. The C-/M- variants aren't actually in vterm's intercept set, but binding them keeps things uniform. New `tests/test-ai-vterm--f9-in-vterm.el`: 4 ERT tests over the `vterm-mode-map` and global bindings. F12's `cj/vterm-toggle` has the same shape of bug and isn't touched here.
Diffstat (limited to 'tests/test-keyboard-compat-setup.el')
0 files changed, 0 insertions, 0 deletions