OSC escape sequences received out-of-order in 3rd-party terminals #17314
Labels
Issue-Bug
It either shouldn't be doing this or needs an investigation.
Resolution-Duplicate
There's another issue on the tracker that's pretty much the same thing.
Windows Terminal version
1.19.11213.0
Windows build number
10.0.22631.0
Other Software
No response
Steps to reproduce
ANSI compatibility has been pretty good in ConPTY. We're coming up on some niche cases.
In a 3rd-party terminal, e.g. alacritty, produce some text with an OSC escape sequence interleaved between some text.
Visually, things look pretty OK. The correct text is echo'd and the title is changed.
But, here is the exact data that alacritty read out of ConPTY:
Observe that when the text was produced in the shell, the OSC command to set title was between "hello" and "world". However, when the text was read out of ConPTY by the terminal, the ordering is changed.
Expected Behavior
I expect the ordering of text, including the ANSI escape sequences, to be preserved.
Actual Behavior
ANSI escape sequences are being parsed and re-serialized in a "lossy" way. While this may be necessary when a Windows Terminal is involved, it isn't when the terminal application only receives ANSI sequences. That is, there is no need to try to parse the ANSI. ConPTY does still need to convert console API calls coming from Windows command-line apps, but plain ANSI text doesn't need any conversion.
The text was updated successfully, but these errors were encountered: