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

ANSI double-height 2️⃣ lines line-wrap several columns too early ❗ #22536

New Issue
Open
opened 2026-01-31 08:16:06 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 08:16:06 +00:00
Owner
Copy Link

Originally created by @ClaireCJS on GitHub (Nov 12, 2024).

Windows Terminal version

1.21.2911.0

Windows build number

10.0.19045.5011

Other Software

TCC command line 31.01.15 x64

Steps to reproduce

First off, I don't know how to change my cmd.exe profile in WT to make ANSI render in CMD, so i can only make this bug happen in TCC.
If someone can tell me how to get CMD to render ANSI, i could reproduce this in CMD.

set BIG_TOP=%@char[27]#3
set BIG_BOT=%@char[27]#4
set message=foo bar baz hello world
echo %BIG_TOP%%message%  %+  echo %BIG_BOT%%message%

^ This displays double-height message:
Image

The bug manifestation depends on how many columns you have in your terminal, so it has to be "found" by repeating this:

set message=%message% 1234567890
echo %BIG_TOP%%message% ^ echo %BIG_BOT%%message%

Image

Eventually, the bug will manifest once you've reached what i call "The cursed column".
(It's a column near the last column, but not the last column, and the offset seems to change based on # of columns)

Image

Basically, there exists a message length such that a blank line occurs PRIOR to reaching the last column, and it happens at a specific column.
One column less, and it doesn't happen. Here is an example of me adding one character to a message ("!") to manifest the bug:

![Image](https://github.com/user-attachments/assets/998d22d2-a786-4e ]6d-8593-d1c88940312d)

[ Now honestly, this may be a TCC bug. But if it is, how can I explain it to them in a way they will understand and accept? They're a bit stubborn over there. They've been in their own non-windows-terminal world for almost 40 years and aren't as deep into it as me. ]

Expected Behavior

For the line to not actually wrap into a blank line unless we actually manage to get our cursor past the end of the line, which was not happening here :)

Actual Behavior

See above.

Originally created by @ClaireCJS on GitHub (Nov 12, 2024). ### Windows Terminal version 1.21.2911.0 ### Windows build number 10.0.19045.5011 ### Other Software TCC command line 31.01.15 x64 ### Steps to reproduce First off, I don't know how to change my cmd.exe profile in WT to make ANSI render in CMD, so i can only make this bug happen in TCC. If someone can tell me how to get CMD to render ANSI, i could reproduce this in CMD. ``` set BIG_TOP=%@char[27]#3 set BIG_BOT=%@char[27]#4 set message=foo bar baz hello world echo %BIG_TOP%%message% %+ echo %BIG_BOT%%message% ``` ^ This displays double-height message: ![Image](https://github.com/user-attachments/assets/e8479b1f-259a-45a9-8988-5dda2d5701dd) The bug manifestation depends on how many columns you have in your terminal, so it has to be "found" by repeating this: ``` set message=%message% 1234567890 echo %BIG_TOP%%message% ^ echo %BIG_BOT%%message% ``` ![Image](https://github.com/user-attachments/assets/df4eb6fb-cbe4-4849-ba23-3eb9b0d27c02) Eventually, the bug will manifest once you've reached what i call "The cursed column". (It's a column near the last column, but not the last column, and the offset seems to change based on # of columns) ![Image](https://github.com/user-attachments/assets/97ae290d-045c-40c0-b2e7-0e3a9ce456e4) Basically, there exists a message length such that a blank line occurs PRIOR to reaching the last column, and it happens at a _specific_ column. One column less, and it doesn't happen. Here is an example of me adding one character to a message ("!") to manifest the bug: ![Image](https://github.com/user-attachments/assets/998d22d2-a786-4e ]6d-8593-d1c88940312d) [ Now honestly, this may be a TCC bug. But if it is, how can I explain it to them in a way they will understand and accept? They're a bit stubborn over there. They've been in their own non-windows-terminal world for almost 40 years and aren't as deep into it as me. ] ### Expected Behavior For the line to not actually wrap into a blank line unless we actually manage to get our cursor past the end of the line, which was not happening here :) ### Actual Behavior See above.
claunia added the Needs-TriageIssue-Bug labels 2026-01-31 08:16:06 +00:00
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
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#22536
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?