-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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.
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
Clear the Screen should do Exactly That #30638
Comments
This is being discussed upstream xtermjs/xterm.js#106 |
Not sure if this is exactly the same behavior as what the issue was opened with but here's my observations. Doing a |
eyep, have to destroy terminal before every test call. upstream or not this is ridiculous. |
same here! I have to create a new instance of terminal after every 'dotnet test' command! |
Just ran in to this issue myself. Every time I F5 my PowerShell script, all the previous output that used to be in the terminal returns, along with the new output. If I perform cls/Clear-Host it goes away until I F5 again, and the old content returns with new output appended. And so on... Here's my about window: |
In case it helps anyone else, while it doesn't solve the issue properly, ctrl+k with the terminal focused should do the same job as cls would normally. |
Any update ? |
xtermjs/xterm.js#106 got closed on June 1st, as the problem appears to be with https://github.com/rprichard/winpty. I checked the winpty repo for open issues mentioning "cls" or "clear" but nothing stands out as related to this. I don't have enough expertise to open an issue with winpty and provide details that would be relevant, but maybe that's what needs to be done to move forward on this? |
@TheKojukinator #45693 will be looking at an alternative to winpty. |
This is likely related to winpty, tracking in #45693 |
Steps to Reproduce:
CMD
CLS
it should clear the screen and not put everything on a new line.
Might not be a serious issue but it bugs the hell out of me :)
Reproduces without extensions: Yes
The text was updated successfully, but these errors were encountered: