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

New tab in Windows Terminal is missing content #20347

New Issue
Closed
opened 2026-01-31 07:11:00 +00:00 by claunia · 9 comments
claunia commented 2026-01-31 07:11:00 +00:00
Owner
Copy Link

Originally created by @konnorandrews on GitHub (Aug 9, 2023).

Windows Terminal version

1.17.11461.0

Windows build number

10.0.22621

Other Software

rustup - all versions including newest https://rustup.rs/

Steps to reproduce

See https://github.com/rust-lang/rustup/issues/3430 for reproduction steps.

Expected Behavior

rustup's installer has a setup menu it prints. This should be displayed when rustup-init.exe is run.

Example shown below is when rebuilding the rustup-init.exe binary to wait 5 seconds before outputting anything.
image

Actual Behavior

The menu does not appear and the content seems to be duplicated on top of it. Scrolling only shows a blank section at the top of the buffer.
image

Originally created by @konnorandrews on GitHub (Aug 9, 2023). ### Windows Terminal version 1.17.11461.0 ### Windows build number 10.0.22621 ### Other Software `rustup` - all versions including newest https://rustup.rs/ ### Steps to reproduce See https://github.com/rust-lang/rustup/issues/3430 for reproduction steps. ### Expected Behavior `rustup`'s installer has a setup menu it prints. This should be displayed when `rustup-init.exe` is run. Example shown below is when rebuilding the `rustup-init.exe` binary to wait 5 seconds before outputting anything. ![image](https://github.com/microsoft/terminal/assets/25871981/4f8737c0-3e00-4b6d-936d-07f2b0baf01e) ### Actual Behavior The menu does not appear and the content seems to be duplicated on top of it. Scrolling only shows a blank section at the top of the buffer. ![image](https://github.com/microsoft/terminal/assets/25871981/1a8eb0aa-7539-4340-bfdf-dec38db5b48e)
claunia added the Needs-TriageIssue-BugResolution-Duplicate labels 2026-01-31 07:11:00 +00:00
claunia commented 2026-01-31 07:11:02 +00:00
Author
Owner
Copy Link

@konnorandrews commented on GitHub (Aug 9, 2023):

This seems to happen only when a new tab/window is created. If I run rustup-init.exe from a powershell instance in Windows Terminal it works as expected.

@konnorandrews commented on GitHub (Aug 9, 2023): This seems to happen only when a new tab/window is created. If I run `rustup-init.exe` from a powershell instance in Windows Terminal it works as expected.
claunia commented 2026-01-31 07:11:04 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 9, 2023):

I bet this is #14512. Can you try Terminal Preview (v1.18), and set that as your Default Terminal, and try again/?

@zadjii-msft commented on GitHub (Aug 9, 2023): I bet this is #14512. Can you try [Terminal Preview](https://aka.ms/terminal-preview) (v1.18), and set that as your Default Terminal, and try again/?
claunia commented 2026-01-31 07:11:04 +00:00
Author
Owner
Copy Link

@ryanavella commented on GitHub (Aug 13, 2023):

I can confirm that the problem is not reproducible with Terminal Preview (v1.18).

Given that the rustup folks would probably like a workaround for v1.17 and earlier, is there a straightforward way for an application to detect the version of Windows Terminal it was spawned from?

@ryanavella commented on GitHub (Aug 13, 2023): I can confirm that the problem is not reproducible with Terminal Preview (v1.18). Given that the rustup folks would probably like a workaround for v1.17 and earlier, is there a straightforward way for an application to detect the version of Windows Terminal it was spawned from?
claunia commented 2026-01-31 07:11:05 +00:00
Author
Owner
Copy Link

@ryanavella commented on GitHub (Aug 13, 2023):

Also I am struggling to find information on the usual release cycle for Terminal, any idea when 1.18 will be stabilized?

@ryanavella commented on GitHub (Aug 13, 2023): Also I am struggling to find information on the usual release cycle for Terminal, any idea when 1.18 will be stabilized?
claunia commented 2026-01-31 07:11:05 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 15, 2023):

I honestly wouldn't bother with a workaround for earlier versions. I'm not even sure there is one based off the way the bug manifested. It was a race between the terminal's size and the conpty size, but I'm not even sure that introducing a forced delay before emitting text would always fix this.

I think there was some discussion about servicing that back to 1.17, lemme necro that thread quick.

We've kinda moved to a quarterly ship cycle, so we're starting to button up 1.19 now. I'd guess that 1.18 becomes stable in about a month?

Ultimately, if it were my call, I'd say that this isn't worth the engineering effort to waorkaround, when there's a fix in hand that's just "update to a newer Terminal version". Which should happen automatically for most folks in a month.

@zadjii-msft commented on GitHub (Aug 15, 2023): I honestly wouldn't bother with a workaround for earlier versions. I'm not even sure there is one based off the way the bug manifested. It was a race between the terminal's size and the conpty size, but I'm not even sure that introducing a forced delay before emitting text would always fix this. I think there was some discussion about servicing that back to 1.17, lemme necro that thread quick. We've kinda moved to a quarterly ship cycle, so we're starting to button up 1.19 now. I'd guess that 1.18 becomes stable in about a month? Ultimately, if it were my call, I'd say that this isn't worth the engineering effort to waorkaround, when there's a fix in hand that's just "update to a newer Terminal version". Which should happen automatically for most folks in a month.
claunia commented 2026-01-31 07:11:05 +00:00
Author
Owner
Copy Link

@ryanavella commented on GitHub (Aug 15, 2023):

The reason some want a workaround is that it is fundamentally an accessibility issue. We want to be able to tell Windows users, who have no prior programming experience, "just run rustup-init.exe and you are good to go." But instead some are coming to forums and chat servers and saying Rust isn't working after installing it (note: when the installer menu is trimmed to the first 30 lines, it looks as though it installed successfully)

So if there isn't a workaround for detecting the terminal version, that probably limits us to either a delay-based workaround, or adding an extra installation step to install Windows Terminal Preview. I'm fine with either, I'd just like to better understand our options.

@ryanavella commented on GitHub (Aug 15, 2023): The reason some want a workaround is that it is fundamentally an accessibility issue. We want to be able to tell Windows users, who have no prior programming experience, "just run rustup-init.exe and you are good to go." But instead some are coming to forums and chat servers and saying Rust isn't working after installing it (note: when the installer menu is trimmed to the first 30 lines, it looks as though it installed successfully) So if there isn't a workaround for detecting the terminal version, that probably limits us to either a delay-based workaround, or adding an extra installation step to install Windows Terminal Preview. I'm fine with either, I'd just like to better understand our options.
claunia commented 2026-01-31 07:11:05 +00:00
Author
Owner
Copy Link

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

This issue has been marked as duplicate and has not had any activity for 1 day. It will be closed for housekeeping purposes.

@microsoft-github-policy-service[bot] commented on GitHub (Aug 16, 2023): This issue has been marked as duplicate and has not had any activity for **1 day**. It will be closed for housekeeping purposes.
claunia commented 2026-01-31 07:11:06 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 21, 2023):

We discussed this a bit in team sync today - @DHowett is just going to cut a servicing release of 1.17 that includes that fix. Honestly, that's just the easiest solution here. There's literally no reason for y'all to waste engineering cycles trying to work around an already fixed bug. And it would probably be a collective lot of engineering effort.

Easier to just push an update to the Store 😉

@zadjii-msft commented on GitHub (Aug 21, 2023): We discussed this a bit in team sync today - @DHowett is just going to cut a servicing release of 1.17 that includes that fix. Honestly, that's just the easiest solution here. There's literally no reason for y'all to waste engineering cycles trying to work around an _already fixed bug_. And it would probably be a collective _lot_ of engineering effort. Easier to just push an update to the Store 😉
claunia commented 2026-01-31 07:11:06 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Oct 17, 2023):

(to close the loop - Terminal 1.18 stable is out now, with the aforementioned fix)

@zadjii-msft commented on GitHub (Oct 17, 2023): (to close the loop - Terminal 1.18 stable is out now, with the aforementioned fix)
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#20347
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?