fix: preserve IME input in iTerm2 - #20
Merged
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
2 participants
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.
Background
Textual enables Kitty keyboard reporting for the full-screen TUI. In iTerm2, ordinary keys continue to work, but committed CJK input-method text is dropped while that mode is active. Disabling Kitty reporting restores IME input in native Textual.
FrontierAgent also defaults to Docker on macOS, but its container launcher only forwarded TERM and COLORTERM. As a result, neither the iTerm2 identity nor TEXTUAL_DISABLE_KITTY_KEY reached the TUI inside the container.
In this PR
Related to #16