Wrong printed/parsed characters on Terminal

[D3vil0p3r]

Windows Terminal version

1.16.10262.0

Windows build number

Microsoft Windows NT 10.0.22621.0

Other Software

python 3.10.10

Steps to reproduce

By using Windows Terminal with WSL, the \001 and \002 Python characters are not parsed correctly.

Open WSL container of Ubuntu or Arch Linux. Run:

if Ubuntu:

python3

if Arch:

python

Once Python is run, type the following:

MAIN = '\001\033[38;5;85m\002'
END = '\001\033[0m\002'
INFO = f'{MAIN}Info{END}'
print(f'\r[{INFO}] Core server started on')

The result will be:

The reason of using \001 and \002 when colors should be used is described in https://bugs.python.org/msg208948

This issue seems to appear only on Windows Terminal with and without WSL (with different displaying characters output).

Issue opened here as agreed in microsoft/WSL#9870

Expected Behavior

The result should be:

[Info] Core server started on

Note that the real output has Info string colored.

Actual Behavior

The wrong result is:

[j4james]

Thanks for the detailed report, but we do already have an issue for this. It's being tracked in #10786.

[D3vil0p3r]

Thanks for the detailed report, but we do already have an issue for this. It's being tracked in #10786.

Thank you for the answer. I hope it will fix soon. The linked issue was opened on July 2021.

[zadjii-msft]

Thanks!

/dup #10786

[microsoft-github-policy-service]

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

[microsoft-github-policy-service]

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

[microsoft-github-policy-service]

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!