Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

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

Closed
towel42-com opened this issue Jul 26, 2023 · 9 comments
Closed

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

towel42-com opened this issue Jul 26, 2023 · 9 comments
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@towel42-com
Copy link

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.
@towel42-com towel42-com added Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Jul 26, 2023
@zadjii-msft
Copy link
Member

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

@zadjii-msft zadjii-msft added the Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something label Jul 26, 2023
@towel42-com
Copy link
Author

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

@microsoft-github-policy-service microsoft-github-policy-service bot added Needs-Attention The core contributors need to come back around and look at this ASAP. and removed Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something labels Jul 27, 2023
@zadjii-msft
Copy link
Member

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

@microsoft-github-policy-service microsoft-github-policy-service bot added Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something and removed Needs-Attention The core contributors need to come back around and look at this ASAP. labels Jul 27, 2023
@towel42-com
Copy link
Author

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

@microsoft-github-policy-service microsoft-github-policy-service bot added Needs-Attention The core contributors need to come back around and look at this ASAP. and removed Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something labels Jul 27, 2023
@zadjii-msft
Copy link
Member

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 zadjii-msft added Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something and removed Needs-Attention The core contributors need to come back around and look at this ASAP. labels Jul 27, 2023
@towel42-com
Copy link
Author

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

@microsoft-github-policy-service microsoft-github-policy-service bot added Needs-Attention The core contributors need to come back around and look at this ASAP. and removed Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something labels Jul 27, 2023
@zadjii-msft
Copy link
Member

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

@microsoft-github-policy-service
Copy link
Contributor

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 microsoft-github-policy-service bot added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Attention The core contributors need to come back around and look at this ASAP. labels Jul 27, 2023
@robbrink-rightware
Copy link

This is still happening for me with Windows Terminal 1.19.10573.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@towel42-com @zadjii-msft @robbrink-rightware