starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Wrong printed/parsed characters on Terminal #19611

New Issue
Closed
opened 2026-01-31 06:48:41 +00:00 by claunia · 6 comments
claunia commented 2026-01-31 06:48:41 +00:00
Owner
Copy Link

Originally created by @D3vil0p3r on GitHub (Mar 30, 2023).

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:
image

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 https://github.com/microsoft/WSL/issues/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:
image

Originally created by @D3vil0p3r on GitHub (Mar 30, 2023). ### 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: ```python 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: ![image](https://user-images.githubusercontent.com/83867734/228796299-c31d6307-6a2f-46bf-9de7-9a64f7f6ffdf.png) 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 https://github.com/microsoft/WSL/issues/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: ![image](https://user-images.githubusercontent.com/83867734/228796392-6fb1a02a-9e5d-4a79-962a-cc53aa717ef3.png)
claunia added the Needs-TriageIssue-BugResolution-Duplicate labels 2026-01-31 06:48:41 +00:00
claunia commented 2026-01-31 06:48:42 +00:00
Author
Owner
Copy Link

@j4james commented on GitHub (Mar 30, 2023):

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

@j4james commented on GitHub (Mar 30, 2023): Thanks for the detailed report, but we do already have an issue for this. It's being tracked in #10786.
claunia commented 2026-01-31 06:48:42 +00:00
Author
Owner
Copy Link

@D3vil0p3r commented on GitHub (Mar 30, 2023):

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.

@D3vil0p3r commented on GitHub (Mar 30, 2023): > 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.
claunia commented 2026-01-31 06:48:42 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Mar 30, 2023):

Thanks!

/dup #10786

@zadjii-msft commented on GitHub (Mar 30, 2023): Thanks! /dup #10786
claunia commented 2026-01-31 06:48:43 +00:00
Author
Owner
Copy Link

@microsoft-github-policy-service[bot] commented on GitHub (Mar 30, 2023):

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[bot] commented on GitHub (Mar 30, 2023): 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!
claunia commented 2026-01-31 06:48:43 +00:00
Author
Owner
Copy Link

@microsoft-github-policy-service[bot] commented on GitHub (Mar 30, 2023):

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[bot] commented on GitHub (Mar 30, 2023): 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!
claunia commented 2026-01-31 06:48:43 +00:00
Author
Owner
Copy Link

@microsoft-github-policy-service[bot] commented on GitHub (Mar 30, 2023):

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[bot] commented on GitHub (Mar 30, 2023): 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!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Issue-Bug Needs-Triage Resolution-Duplicate
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#19611
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?