Conversation
Also note that kitty-keys-terminal.sh cannot run under the regress Makefile, which uses env -i and so removes DISPLAY and HOME, and make the Kitty test file modes match the rest of regress.
|
I've tried using this under Ghostty and pressing Shift+Space writes ";2u". edit: |
|
@gabehowe try this: Add these lines to test.conf: then start tmux. Run these commands and let me know what they output: Then press shift-space. Asuming you are in the directory where you compiled this branch, you need to run the tmux you compiled, hence ./tmux. You should see the mode "Kitty 1" and you should see "S-space". Note, I am currently trying to see if I can get each client to discover if it supports kitty or xterm or csi-u or just plain ascii, so you may not need to specificy set the extended-keys-format to kitty if I can figure that out. |
|
Both kitty and Ghostty return I've just tested this on kitty and it doesn't have this behavior, so perhaps it's somehow Ghostty specific?. |
|
Huh, it's not what I see. Are you reattaching to an existing tmux server? Also, you can't turn on kitty after you reattach, you need to start your tmux -f test.conf or start tmux like this: |
|
I have added autodetection for kitty in this PR: #5615 |
Looks like I was attaching to an existing server. Now I get client = Kitty 1 and tmux got: S-Space and shift-space doesn't paste ;2u. I'm sorry to have taken up your time. |
Add kitty keyboard protocol support (KKP).
(https://sw.kovidgoyal.net/kitty/keyboard-protocol/); no Kitty source code was
used.
This PR follows #5405 (Add kitty keyboard protocol support (finish #4912). All the comments were hopefully addressed.
This work adds the new extended-keys-format
kittywhich now supportsxterm,csi-u, and nowkitty.This PR uses the emacs style naming convention:
S-= ShiftC-= ControlM-= Meta/Alts-= SuperH-= Hyper