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

WHen used with Visual Studio for debugging, screen doesnt clear #20299

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

Originally created by @towel42-com on GitHub (Jul 26, 2023).

Windows Terminal version

No response

Windows build number

No response

Other Software

Visual Studio 2022 17.6.5

Steps to reproduce

Create a C++ console application
Make sure the debugging option to "Automatically close the console when debugging stops" is unchecked
Run and exit an attached debugging session
Again Run and exit an attached debugging session

Expected Behavior

With the old windows console, it was cleared every time.

This is what should happen

Actual Behavior

When you run a second (or more) debugging session, 99% of the time it just starts at the top of the console screen overwriting existing text

Sometimes it clears it.

This is largely due to VS 2022 (I skipped 2019 so it may be in 2019) ability to leave the console open when debugging ends. If you turn off that option, this is not an issue.

Originally created by @towel42-com on GitHub (Jul 26, 2023). ### Windows Terminal version _No response_ ### Windows build number _No response_ ### Other Software Visual Studio 2022 17.6.5 ### Steps to reproduce Create a C++ console application Make sure the debugging option to "Automatically close the console when debugging stops" is unchecked Run and exit an attached debugging session Again Run and exit an attached debugging session ### Expected Behavior With the old windows console, it was cleared every time. This is what should happen ### Actual Behavior When you run a second (or more) debugging session, 99% of the time it just starts at the top of the console screen overwriting existing text Sometimes it clears it. This is largely due to VS 2022 (I skipped 2019 so it may be in 2019) ability to leave the console open when debugging ends. If you turn off that option, this is not an issue.
claunia added the Issue-BugResolution-Duplicate labels 2026-01-31 07:09:27 +00:00
claunia commented 2026-01-31 07:09:28 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 26, 2023):

Are you using the Windows Terminal, or the vintage windows console (conhost.exe)?

@zadjii-msft commented on GitHub (Jul 26, 2023): Are you using the Windows Terminal, or the vintage windows console (`conhost.exe`)?
claunia commented 2026-01-31 07:09:28 +00:00
Author
Owner
Copy Link

@towel42-com commented on GitHub (Jul 27, 2023):

WT Multiple tabs and all :) Ive noticed this on a couple of machines

@towel42-com commented on GitHub (Jul 27, 2023): WT Multiple tabs and all :) Ive noticed this on a couple of machines
claunia commented 2026-01-31 07:09:29 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 27, 2023):

Which version of the Terminal/? There was something like this that was fixed in 1.18...

@zadjii-msft commented on GitHub (Jul 27, 2023): Which version of the Terminal/? There was something like this that was fixed in 1.18...
claunia commented 2026-01-31 07:09:29 +00:00
Author
Owner
Copy Link

@towel42-com commented on GitHub (Jul 27, 2023):

1.17.11461.0 Ill go to the windows store and update and see if that fixes it

@towel42-com commented on GitHub (Jul 27, 2023): 1.17.11461.0 Ill go to the windows store and update and see if that fixes it
claunia commented 2026-01-31 07:09:29 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 27, 2023):

1.17 is the latest version of Terminal Stable, 1.18 can be found here: https://aka.ms/terminal-preview. You can then set that as the "Default Terminal Application" in the settings app (or settings UI of the Terminal), and have VS launch that one instead.

@zadjii-msft commented on GitHub (Jul 27, 2023): 1.17 is the latest version of Terminal _Stable_, 1.18 can be found here: https://aka.ms/terminal-preview. You can then set that as the "Default Terminal Application" in the settings app (or settings UI of the Terminal), and have VS launch that one instead.
claunia commented 2026-01-31 07:09:29 +00:00
Author
Owner
Copy Link

@towel42-com commented on GitHub (Jul 27, 2023):

I realized that once I went to the store. I installed the preview, it appears to have fixed the issue. However, so Im closing this issue. If I see it again, Ill re-open

@towel42-com commented on GitHub (Jul 27, 2023): I realized that once I went to the store. I installed the preview, it appears to have fixed the issue. However, so Im closing this issue. If I see it again, Ill re-open
claunia commented 2026-01-31 07:09:30 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 27, 2023):

Great, I bet this was /dup #14512. Thanks for confirming!

@zadjii-msft commented on GitHub (Jul 27, 2023): Great, I bet this was /dup #14512. Thanks for confirming!
claunia commented 2026-01-31 07:09:30 +00:00
Author
Owner
Copy Link

@microsoft-github-policy-service[bot] commented on GitHub (Jul 27, 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 (Jul 27, 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 07:09:30 +00:00
Author
Owner
Copy Link

@robbrink-rightware commented on GitHub (Mar 27, 2024):

This is still happening for me with Windows Terminal 1.19.10573.0

@robbrink-rightware commented on GitHub (Mar 27, 2024): This is still happening for me with Windows Terminal 1.19.10573.0
claunia commented 2026-01-31 07:09:30 +00:00
Author
Owner
Copy Link

@Kobi-Blade commented on GitHub (Jan 11, 2025):

This is still happening for me with Windows Terminal 1.19.10573.0

Seems the issue has leaked to Visual Studio Terminal as well, they say was fixed but clearly was not.

@Kobi-Blade commented on GitHub (Jan 11, 2025): > This is still happening for me with Windows Terminal 1.19.10573.0 Seems the issue has leaked to Visual Studio Terminal as well, they say was fixed but clearly was not.
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 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#20299
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?