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.

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

Closed
VictorXLR opened this issue Jul 13, 2017 · 10 comments
Closed

Clear the Screen should do Exactly That #30638

VictorXLR opened this issue Jul 13, 2017 · 10 comments
Assignees
Labels
*duplicate Issue identified as a duplicate of another issue(s) terminal Integrated terminal issues under-discussion Issue is under discussion for relevance, priority, approach upstream Issue identified as 'upstream' component related (exists outside of VS Code) windows VS Code on Windows issues
Milestone

Comments

@VictorXLR
Copy link

  • VSCode Version: Latest
  • OS Version: Windows 10

Steps to Reproduce:

  1. Open VSCODE terminal CMD
  2. Run a few Commands,
  3. Type 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

@vscodebot vscodebot bot added the terminal Integrated terminal issues label Jul 13, 2017
@Tyriar
Copy link
Member

Tyriar commented Jul 13, 2017

This is being discussed upstream xtermjs/xterm.js#106

@Tyriar Tyriar added under-discussion Issue is under discussion for relevance, priority, approach upstream Issue identified as 'upstream' component related (exists outside of VS Code) labels Jul 13, 2017
@Tyriar Tyriar added this to the Backlog milestone Jul 13, 2017
@ghiscoding
Copy link

Not sure if this is exactly the same behavior as what the issue was opened with but here's my observations.

Doing a cls does clear the screen but it's annoying to see the previous history coming back after running another command. For example, if I run a Unit Test and do a cls, I don't expect to see previous tests coming back after a cls but they do and this makes the terminal a little hard to follow. I'm running version 1.18.0-insiders which has the new terminal rendering engine.

@Spown
Copy link

Spown commented Dec 25, 2017

eyep, have to destroy terminal before every test call. upstream or not this is ridiculous.

@suadev
Copy link

suadev commented Jan 26, 2018

same here!

I have to create a new instance of terminal after every 'dotnet test' command!

@TheKojukinator
Copy link

TheKojukinator commented May 1, 2018

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:
Version 1.22.2
Commit 3aeede7
Date 2018-04-12T16:38:45.278Z
Shell 1.7.12
Renderer 58.0.3029.110
Node 7.9.0
Architecture x64

@ogarvey
Copy link

ogarvey commented Jun 29, 2018

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.

@juancrl
Copy link

juancrl commented Jul 25, 2018

Any update ?
The console cannot provide wrong information !

@TheKojukinator
Copy link

xtermjs/xterm.js#106 got closed on June 1st, as the problem appears to be with https://github.com/rprichard/winpty.
#45693 lists all the winpty issues affecting vscode, and this one is among them.

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?

@Tyriar
Copy link
Member

Tyriar commented Jul 25, 2018

@TheKojukinator #45693 will be looking at an alternative to winpty.

@Tyriar
Copy link
Member

Tyriar commented Sep 12, 2018

This is likely related to winpty, tracking in #45693

@Tyriar Tyriar closed this as completed Sep 12, 2018
@Tyriar Tyriar added the *duplicate Issue identified as a duplicate of another issue(s) label Sep 12, 2018
@vscodebot vscodebot bot locked and limited conversation to collaborators Oct 27, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*duplicate Issue identified as a duplicate of another issue(s) terminal Integrated terminal issues under-discussion Issue is under discussion for relevance, priority, approach upstream Issue identified as 'upstream' component related (exists outside of VS Code) windows VS Code on Windows issues
Projects
None yet
Development

No branches or pull requests

8 participants