If I open a terminal in VS Code, any terminal (powershell, bash, cmd, etc), typing “cls” clears the currently visible lines, but I can scroll up to see that it didn’t clear any of the lines that weren’t visible on screen. This is a minor annoyance in manual terminal sessions, but a complete showstopper when it comes to running code. If I have my code (any language) output to a re-used terminal (which for example, is the only possible way to output to the terminal with rust and codeLLDB), the lines that were offscreen aren’t cleared on the second run and suddenly I’m seeing old data, like this, which is extremely confusing.
Visual depiction of bug, where old output is in the same terminal as new output:
I’ve searched around for a while and seen many various threads saying arguing whether it’s a vscode issue or a windows 10 conhost issue or whatever else (the verdict seems to be it’s win10 conhost and doesn’t happen in win11?), but none of the threads give an answer, only weird workarounds that don’t actually solve the issue (like custom keybinds to clear the terminal in a special vs-code only way).
Is there any way to fix this that isn’t “upgrade to windows 11”? Using software that isn’t vscode also fixes this issue because their terminals don’t require conhost, but I need the VSCode ecosystem
