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 rendering fails unless a 1ms delay is inserted into echo statement #22441

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

Originally created by @ClaireCJS on GitHub (Oct 21, 2024).

Windows Terminal version

1.20.11781.0

Windows build number

10.0.19045.5011

Other Software

No response

Steps to reproduce

I think this may be a new bug that just creep in.

BACKGROUND: I have an "askyn.bat" that asks Yes/no questions. It has a "big" option to use VT100 double-height text. Starting this week, my "big" double-height questions started getting a newline inserted in between.... But only if I was at the very lowest row of the console when calling it. It looked like this:
Image

THE FIX: After some rather extensive testing, the solution was the very last thing I'd ever expect.

It was inserting a 1ms delay prior to the newline!!!!!!!!

Image

Literally, remarking out the delay /m 1 (one millisecond delay) changes the rendering from aforementioned screenshot to correct output:
Image

I sincerely doubt this is by design.

I sincerely doubt that a 1 millisecond delay before outputting a newline should somehow change the ANSI rendering such that there is a phantom extra newline that appears out of nowhere.

And one of the reasons for my sincere doubt is —— This is a script i've been using for a year. It just broke today. Consistently.

FOR REFERENCE: "echos" is the same as echo, but without a newline at the end. "delay" is like unix's sleep, but accepts millisecond delays with the /m option. "big_top" and "big_bot" are the ansi codes for double-height text, top line and bottom line. Ansi_clear_to_end is simply to clear any screen garbage off from the right of the line. Ansi_save_position is the ansi code to save screen position, which I use to write "yes" "no" in the correct place once the user has responded to the Y/N prompt.

Expected Behavior

(See above)

Actual Behavior

(see above)

Originally created by @ClaireCJS on GitHub (Oct 21, 2024). ### Windows Terminal version 1.20.11781.0 ### Windows build number 10.0.19045.5011 ### Other Software _No response_ ### Steps to reproduce I think this may be a new bug that just creep in. BACKGROUND: I have an "askyn.bat" that asks Yes/no questions. It has a "big" option to use VT100 double-height text. Starting this week, my "big" double-height questions started getting a newline inserted in between.... But only if I was at the very lowest row of the console when calling it. It looked like this: ![Image](https://github.com/user-attachments/assets/e7e91b19-4f22-400b-9f4b-47b6a072ca64) THE FIX: After some rather extensive testing, the solution was the very last thing I'd ever expect. **It was inserting a 1ms delay prior to the newline!!!!!!!!** ![Image](https://github.com/user-attachments/assets/ae378d58-eb87-4683-b4eb-39aa44426e11) Literally, remarking out the ```delay /m 1``` (one millisecond delay) changes the rendering from aforementioned screenshot to correct output: ![Image](https://github.com/user-attachments/assets/170bb39c-5450-4e60-98f8-6aff6b2b9f17) I sincerely doubt this is by design. I sincerely doubt that a 1 millisecond delay before outputting a newline should somehow change the ANSI rendering such that there is a phantom extra newline that appears out of nowhere. And one of the reasons for my sincere doubt is —— This is a script i've been using for a year. It just broke today. Consistently. FOR REFERENCE: "echos" is the same as echo, but without a newline at the end. "delay" is like unix's sleep, but accepts millisecond delays with the /m option. "big_top" and "big_bot" are the ansi codes for double-height text, top line and bottom line. Ansi_clear_to_end is simply to clear any screen garbage off from the right of the line. Ansi_save_position is the ansi code to save screen position, which I use to write "yes" "no" in the correct place once the user has responded to the Y/N prompt. ### Expected Behavior (See above) ### Actual Behavior (see above)
claunia added the Product-ConhostArea-OutputNeeds-TriageIssue-BugArea-VT labels 2026-01-31 08:13:16 +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 Area-Output Area-VT Issue-Bug Needs-Triage Product-Conhost
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#22441
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?