diff options
| author | Craig Jennings <c@cjennings.net> | 2026-06-05 09:55:41 -0500 |
|---|---|---|
| committer | Craig Jennings <c@cjennings.net> | 2026-06-05 09:55:41 -0500 |
| commit | 81ececd67b23e42163c970edb4e9a4c0d824612e (patch) | |
| tree | 66c6558000c8675ed63c8b0e2ae9518e383d581c /ai-prompts/quality-engineer.org | |
| parent | 854aa53a96476ccaae0c93bd9af0493ef8431e4b (diff) | |
| download | dotemacs-81ececd67b23e42163c970edb4e9a4c0d824612e.tar.gz dotemacs-81ececd67b23e42163c970edb4e9a4c0d824612e.zip | |
fix(term): forward C-SPC and window-nav keys in ghostel buffers
Two keystrokes weren't reaching Emacs inside a ghostel terminal, both because of how ghostel routes keys in semi-char mode.
C-SPC was the worse one. ghostel forwards the `C-@' event but not the distinct `C-SPC' event GUI Emacs produces, so C-Space fell through to the global `set-mark-command' and set an Emacs region in the terminal buffer. That region followed point as output streamed (a stuck "selection" Escape and C-g couldn't clear), and it meant tmux copy-mode's begin-selection never started, so M-w copied nothing. I bind C-SPC to cj/term-send-C-SPC, which forwards NUL like a terminal key.
The C-M-arrows (buffer-move, window swap) were being forwarded to the terminal program the same way the F9 family was. I added the windmove S-arrows and buffer-move C-M-arrows to ghostel-keymap-exceptions and rebuilt the semi-char map. The S-arrows already reached Emacs by keymap precedence, but listing them makes the window-nav contract explicit rather than accidental.
Regression tests cover all three: C-SPC bound to the forwarder, and the window-nav keys in the exceptions with the semi-char map no longer forwarding them.
Diffstat (limited to 'ai-prompts/quality-engineer.org')
0 files changed, 0 insertions, 0 deletions
