fix(tui): handle OSC 133 click events in editor#2074
Open
mitsuhiko wants to merge 1 commit intobadlogic:mainfrom
Open
fix(tui): handle OSC 133 click events in editor#2074mitsuhiko wants to merge 1 commit intobadlogic:mainfrom
mitsuhiko wants to merge 1 commit intobadlogic:mainfrom
Conversation
Owner
|
without asking my clanker, what is this good for? |
Contributor
Author
|
It lets you click around in the multi-line edit fields to change the cursor position. |
badlogic
added
the
possibly-openclaw-clanker
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.
This commit adds editor support for OSC 133
click_events=1prompt-click (supported by Ghostty and some others) by changing the focused TUI editor to emit click-enabled OSC 133 semantic prompt markers.This teaches the TUI to parse and dispatch incoming mouse click events to the focused component, and teaching the editor to map those terminal click coordinates back to logical cursor positions across single-line, explicit multi-line, and wrapped inputs.
This is sloppier than I think it could be, but it took me a few attempts to make it work at all.