fix: strip OSC sequences from Aether output (fixes #25) - #30
Open
m4tinbeigi-official wants to merge 4 commits into
Open
fix: strip OSC sequences from Aether output (fixes #25)#30m4tinbeigi-official wants to merge 4 commits into
m4tinbeigi-official wants to merge 4 commits into
Conversation
2 tasks
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.
Fixes #25. On Windows 11, ConPTY translates console title changes into ANSI OSC sequences (e.g.
\x1b]0;Title\x07). The existingstrip_ansifunction only stripped CSI sequences (starting with[), so OSC sequences were left in the log output, breaking the string matching for prompt headers (likeProtocol:) and causing the setup sequence to hang indefinitely.