"Terminal: Clear" not working as desired #75141
Description
Steps to Reproduce:
- Run a python file using command palette >Python: Run file in terminal window
- Terminal shows the output. Now, clear the terminal using command palette >Terminal: Clear
- Terminal gets clear now. Run the file again in the terminal >Python: Run file in terminal window
- Here is where issue shows up - the terminal still shows all the previous outputs from before the last clear command. IMO, desired should be that terminal should not show any previously cleared outputs.
- Attached below is a gif of the screen reproducing & visualizing this issue
Does this issue occur when all extensions are disabled?:
Yes, the issue reoccurs. (Note: All except the "Python" extension were disabled. Python extension is needed to run the python file in terminal.
I had also posted in Super User forum thinking this was some issue with my system. And then I tried it on a clean build of VS code and it got repeated. Hence, I decided to post it as a bug.
Link to Super User forum question
VS Code version: Code - Insiders 1.36.0-insider (c089daa, 2019-06-07T05:19:15.188Z)
OS version: Windows_NT x64 10.0.18362
System Info
| Item | Value |
|---|---|
| CPUs | Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz (12 x 3696) |
| GPU Status | 2d_canvas: enabled flash_3d: enabled flash_stage3d: enabled flash_stage3d_baseline: enabled gpu_compositing: enabled multiple_raster_threads: enabled_on native_gpu_memory_buffers: disabled_software oop_rasterization: disabled_off protected_video_decode: enabled rasterization: enabled skia_deferred_display_list: disabled_off skia_renderer: disabled_off surface_synchronization: enabled_on video_decode: enabled viz_display_compositor: disabled_off webgl: enabled webgl2: enabled |
| Load (avg) | undefined |
| Memory (System) | 15.68GB (7.71GB free) |
| Process Argv | |
| Screen Reader | no |
| VM | 0% |
Extensions (1)
| Extension | Author (truncated) | Version |
|---|---|---|
| python | ms- | 2019.5.18875 |
Metadata
Metadata
Assignees
Labels
Issue identified by VS Code Team member as probable bugPatch has been released in VS Code InsidersIntegrated terminal issues related to the ConPTY backendIssue identified as 'upstream' component related (exists outside of VS Code)The underlying upstream issue has been fixedThis is an upstream issue that has been reported upstreamVerification succeededVS Code on Windows issues