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

Ctrl-L leaves the screen dirty #160

New Issue
Closed
opened 2026-01-30 21:44:11 +00:00 by claunia · 3 comments
claunia commented 2026-01-30 21:44:11 +00:00
Owner
Copy Link

Originally created by @bitcrazed on GitHub (Feb 16, 2018).

From @Alebat on April 21, 2017 18:0

Microsoft Windows [Version 10.0.14393]

When I press Ctrl-L after scrolling up in BashOnWindows the text in the window view is canceled but not the part hidden after the last line.

When I need to clear the screen I often press Ctrl-L instead of calling the clear command (https://ss64.com/bash/syntax-keyboard.html). This issue does not show up with clear due to the window scroll after pressing enter.

I think that when Ctrl-L is pressed the window should scroll to the prompt before doing anything else. Now it is the prompt that moves to the top of the window, without any scrolling.

This issue may or not be realted to #1756

Copied from original issue: Microsoft/WSL#1978

Originally created by @bitcrazed on GitHub (Feb 16, 2018). _From @Alebat on April 21, 2017 18:0_ Microsoft Windows [Version 10.0.14393] **When I press Ctrl-L after scrolling up** in BashOnWindows the text in the window view is canceled but not the part hidden after the last line. When I need to clear the screen I often press **Ctrl-L** instead of calling the `clear` command (https://ss64.com/bash/syntax-keyboard.html). This issue does not show up with `clear` due to the window scroll after pressing enter. I think that when **Ctrl-L** is pressed the window **should scroll to the prompt before** doing anything else. Now it is the prompt that moves to the top of the window, without any scrolling. This issue may or not be realted to #1756 _Copied from original issue: Microsoft/WSL#1978_
claunia added the Product-ConhostResolution-Fix-Available labels 2026-01-30 21:44:11 +00:00
claunia commented 2026-01-30 21:44:12 +00:00
Author
Owner
Copy Link

@bitcrazed commented on GitHub (Feb 16, 2018):

From @sunilmut on April 21, 2017 21:2

@Alebat - Thanks for your post. Looks console related. We have done some significant investments in console + WSL in the CU build (15063). Looks like you are still on AU (build 14393). Are you able to move to CU and try this out again? I played around with Ctrl+L a little in CU and it seems to be consistent with native Ubuntu experience.

@bitcrazed commented on GitHub (Feb 16, 2018): _From @sunilmut on April 21, 2017 21:2_ @Alebat - Thanks for your post. Looks console related. We have done some significant investments in console + WSL in the CU build (15063). Looks like you are still on AU (build 14393). Are you able to move to CU and try this out again? I played around with Ctrl+L a little in CU and it seems to be consistent with native Ubuntu experience.
claunia commented 2026-01-30 21:44:13 +00:00
Author
Owner
Copy Link

@bitcrazed commented on GitHub (Feb 16, 2018):

From @zadjii-msft on April 24, 2017 15:51

@Alebat Yea, I see what you're seeing, even on CU. I've filed MSFT:11765830 on our internal work tracker to make sure this gets investigated.

I did add support for CSI 3 J (clear scrollback) last release, but I can't remember off the top of my head if that is what C-l emits in bash. IIRC, it only emits CSI 2 J (Clear screen), which would make this the "working as intended" behavior. I'd be cautious to try and change that behavior to include scrolling to the cursor position, this may just be one of those cases where the inherent differences between a Windows and Linux console aren't entirely reconcilable.

That being said, it could be something else. We'll see.

@bitcrazed commented on GitHub (Feb 16, 2018): _From @zadjii-msft on April 24, 2017 15:51_ @Alebat Yea, I see what you're seeing, even on CU. I've filed MSFT:11765830 on our internal work tracker to make sure this gets investigated. I did add support for `CSI 3 J` (clear scrollback) last release, but I can't remember off the top of my head if that is what `C-l` emits in bash. IIRC, it only emits `CSI 2 J` (Clear screen), which would make this the "working as intended" behavior. I'd be cautious to try and change that behavior to include scrolling to the cursor position, this may just be one of those cases where the inherent differences between a Windows and Linux console aren't entirely reconcilable. That being said, it could be something else. We'll see.
claunia commented 2026-01-30 21:44:13 +00:00
Author
Owner
Copy Link

@bitcrazed commented on GitHub (Feb 16, 2018):

From @zadjii-msft on June 8, 2017 23:14

Hey, I submitted a fix for this earlier this week. Should be out to Insiders in about a month :)

@bitcrazed commented on GitHub (Feb 16, 2018): _From @zadjii-msft on June 8, 2017 23:14_ Hey, I submitted a fix for this earlier this week. Should be out to Insiders in about a month :)
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 Product-Conhost Resolution-Fix-Available
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#160
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?