fix: tmux extended-keys-format csi-u for Pi modified keys - #26
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pi warns:
tmux extended-keys-format is xterm. Pi works best with csi-u. ExitBox's generated tmux config enabledextended-keys onand advertised theextkeysfeature, but never setextended-keys-format, so tmux used its defaultxtermencoding for modified keys. Pi (and other Kitty-protocol agents) can't decode that encoding, so Shift+Enter was lost — while agents that tolerate the xterm encoding kept working (explains "all other agents fine, just not Pi").Fix
Add
set -g extended-keys-format csi-uto the generated tmux config (the fixterms/CSI-u encoding Pi expects). Pairs with the existingextended-keys on+terminal-features "*:extkeys".Tests
Added a
write_tmux_confassertion forextended-keys-format csi-u. Entrypoint suite: 106 pass, 2 pre-existing failures (codex session-storage env leakage onmain, unrelated).Note: entrypoint ships in the base image — needs an image rebuild to take effect. If
exitboxis run from inside another (host) tmux, that outer tmux must carry the sameextended-keys on/extended-keys-format csi-u/terminal-features *:extkeyssettings, or it strips modified keys before they reach the container.