starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

clear command - Windows Terminal in VSCode #1711

New Issue
Closed
opened 2026-01-30 22:34:19 +00:00 by claunia · 8 comments
claunia commented 2026-01-30 22:34:19 +00:00
Owner
Copy Link

Originally created by @dash-mode on GitHub (Jun 16, 2019).

About the device

VSCode version

Summary of the bug

I deployed the windows terminal dev build and then started working on a separate project on VScode. I opened the VScode terminal and then after typing a couple of commands, I hit clear
app js - factbotAzure - Visual Studio Code 6_16_2019 5_43_18 PM
After hitting clear, the cursor just moves to the top, but the contents of the terminal aren't cleared. In fact, everytime I write a command after clearing, it just writes over the previous command as if it were an empty line.
app js - factbotAzure - Visual Studio Code 6_16_2019 5_44_01 PM

I am not sure if this is a bug in VSCode or the windows terminal, so I have posted this issue in the vscode github page too.

Originally created by @dash-mode on GitHub (Jun 16, 2019). # About the device <img width="283" alt="VSCode version" src="https://user-images.githubusercontent.com/32212134/59569990-2515f680-905f-11e9-9751-b0bc090008d8.png"> # Summary of the bug I deployed the windows terminal dev build and then started working on a separate project on VScode. I opened the VScode terminal and then after typing a couple of commands, I hit clear <img width="960" alt="app js - factbotAzure - Visual Studio Code 6_16_2019 5_43_18 PM" src="https://user-images.githubusercontent.com/32212134/59570061-314e8380-9060-11e9-8a25-0fbe705f10c1.png"> After hitting clear, the cursor just moves to the top, but the contents of the terminal aren't cleared. In fact, everytime I write a command after clearing, it just writes over the previous command as if it were an empty line. <img width="960" alt="app js - factbotAzure - Visual Studio Code 6_16_2019 5_44_01 PM" src="https://user-images.githubusercontent.com/32212134/59570105-fc8efc00-9060-11e9-86c9-0478cc1b6a56.png"> I am not sure if this is a bug in VSCode or the windows terminal, so I have posted this issue in the vscode github page too.
claunia added the Area-OutputIssue-BugResolution-ExternalProduct-Conpty labels 2026-01-30 22:34:19 +00:00
claunia commented 2026-01-30 22:34:20 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Jun 18, 2019):

I can't get VSCode or putty-wincon to reproduce this behavior. Would you mind running clear|xxd and pasting the output here?

VSCode and putty-wincon are using the same technology under the hood. If I can't get it to reproduce in putty-wincon, chances are it's a VSCode issue ... but if I can't get it to reproduce in VSCode, I'm questioning whether I'm doing the right thing.

@DHowett-MSFT commented on GitHub (Jun 18, 2019): I can't get VSCode _or_ putty-wincon to reproduce this behavior. Would you mind running `clear|xxd` and pasting the output here? VSCode and putty-wincon are using the same technology under the hood. If I can't get it to reproduce in putty-wincon, chances are it's a VSCode issue ... but if I can't get it to reproduce in VSCode, I'm questioning whether I'm doing the right thing.
claunia commented 2026-01-30 22:34:20 +00:00
Author
Owner
Copy Link

@dash-mode commented on GitHub (Jun 18, 2019):

clear|xxd command ran in VSCode
Annotation 2019-06-18 075241

@dash-mode commented on GitHub (Jun 18, 2019): `clear|xxd` command ran in VSCode <img width="449" alt="Annotation 2019-06-18 075241" src="https://user-images.githubusercontent.com/32212134/59679929-2d288000-919e-11e9-88d2-427c823aff6f.png">
claunia commented 2026-01-30 22:34:21 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jun 18, 2019):

@dash-mode did you enable conpty in VSCode, or are you still using winpty?

I believe the setting is "terminal.integrated.windowsEnableConpty": true

@zadjii-msft commented on GitHub (Jun 18, 2019): @dash-mode did you enable conpty in VSCode, or are you still using winpty? I believe the setting is `"terminal.integrated.windowsEnableConpty": true`
claunia commented 2026-01-30 22:34:21 +00:00
Author
Owner
Copy Link

@dash-mode commented on GitHub (Jun 18, 2019):

@zadjii-msft
Yes, it is enabled.
Annotation 2019-06-18 125701

@dash-mode commented on GitHub (Jun 18, 2019): @zadjii-msft Yes, it is enabled. <img width="796" alt="Annotation 2019-06-18 125701" src="https://user-images.githubusercontent.com/32212134/59703791-afc63500-91c8-11e9-91a1-f42c755f26c1.png">
claunia commented 2026-01-30 22:34:21 +00:00
Author
Owner
Copy Link

@dash-mode commented on GitHub (Jun 18, 2019):

https://github.com/microsoft/vscode/issues/72130
Similar issue being tackled here. ^
I also wanted to point out that I am not facing this issue in my mac. This is happening in my windows machine,

@dash-mode commented on GitHub (Jun 18, 2019): https://github.com/microsoft/vscode/issues/72130 Similar issue being tackled here. ^ I also wanted to point out that I am not facing this issue in my mac. This is happening in my windows machine,
claunia commented 2026-01-30 22:34:21 +00:00
Author
Owner
Copy Link

@Tyriar commented on GitHub (Jun 19, 2019):

This is already fixed in v1.36, see https://github.com/microsoft/vscode/issues/72130#issuecomment-503390207 for the details.

In the future issues in VS Code's terminal should be created over on microsoft/vscode as there's many different parts that things can go wrong and I like to avoid getting the console team involved until I'm pretty sure conpty/conhost is the cause.

@Tyriar commented on GitHub (Jun 19, 2019): This is already fixed in v1.36, see https://github.com/microsoft/vscode/issues/72130#issuecomment-503390207 for the details. In the future issues in VS Code's terminal should be created over on [microsoft/vscode](https://github.com/Microsoft/vscode) as there's many different parts that things can go wrong and I like to avoid getting the console team involved until I'm pretty sure conpty/conhost is the cause.
claunia commented 2026-01-30 22:34:22 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Jun 19, 2019):

Thanks again, @Tyriar!

@DHowett-MSFT commented on GitHub (Jun 19, 2019): Thanks again, @Tyriar!
claunia commented 2026-01-30 22:34:22 +00:00
Author
Owner
Copy Link

@dash-mode commented on GitHub (Jun 19, 2019):

This is already fixed in v1.36, see microsoft/vscode#72130 (comment) for the details.

In the future issues in VS Code's terminal should be created over on microsoft/vscode as there's many different parts that things can go wrong and I like to avoid getting the console team involved until I'm pretty sure conpty/conhost is the cause.

Hey @Tyriar . I did post the exact same issue in microsoft/vscode/issues/75607 . But I have closed it now since it has been fixed. Thanks

@dash-mode commented on GitHub (Jun 19, 2019): > This is already fixed in v1.36, see [microsoft/vscode#72130 (comment)](https://github.com/microsoft/vscode/issues/72130#issuecomment-503390207) for the details. > > In the future issues in VS Code's terminal should be created over on [microsoft/vscode](https://github.com/Microsoft/vscode) as there's many different parts that things can go wrong and I like to avoid getting the console team involved until I'm pretty sure conpty/conhost is the cause. Hey @Tyriar . I did post the exact same issue in microsoft/vscode/issues/75607 . But I have closed it now since it has been fixed. Thanks
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Area-Output Issue-Bug Product-Conpty Resolution-External
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#1711
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?