You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Windows build number: 10.0.18363.628
Windows Terminal version (if applicable): 0.8.10261.0
Any other software?
Steps to reproduce
run command like ls in powershell session or dir in cmd session and then try to use cls to clear the screen, you will find the history while scrolling up.
Expected behavior
no history anymore after cls was executed.
Actual behavior
history output is not cleared.
The text was updated successfully, but these errors were encountered:
ghost
added
Needs-Triage
It's a new issue that the core contributor team needs to triage at the next triage meeting
Needs-Tag-Fix
Doesn't match tag requirements
labels
Feb 5, 2020
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!
ghost
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-Tag-Fix
Doesn't match tag requirements
labels
Feb 5, 2020
Environment
Steps to reproduce
run command like ls in powershell session or dir in cmd session and then try to use cls to clear the screen, you will find the history while scrolling up.
Expected behavior
no history anymore after cls was executed.
Actual behavior
history output is not cleared.
The text was updated successfully, but these errors were encountered: