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

[powershell] typing a character after scrolling up after Ctrl+L in TerminalScrolling mode will behave wrong #1620

New Issue
Open
opened 2026-01-30 22:32:16 +00:00 by claunia · 0 comments
claunia commented 2026-01-30 22:32:16 +00:00
Owner
Copy Link

Originally created by @zadjii-msft on GitHub (Jun 12, 2019).

Originally assigned to: @zadjii-msft on GitHub.

From MSFT:20137864

see:
Bug 20108529: [host] virtual bottom does weird things with powershell control-L (see gif)

run powershell in a conhost with TerminalScrolling enabled.

run ls
type # foo
press ctrl+L
note that the viewport has moved down so the line with "# foo" is not at the top, and the rest of the viewport is empty. Note the scrollbar size.
scroll up with the mouse so that the cursor is no longer visible.
type a character.

expected:

  • the viewport will snap so that the line with the cursor is now at the top, like it was before scrolling.

actual:

  • the viewport will snap so that the line with the cursor is now at the bottom of the viewport.

This is definitely due to PSReadline, who implements the ^L handling.

I presume they're making the cursor visible manually, but I don't care to dig in too deep right now.

Originally created by @zadjii-msft on GitHub (Jun 12, 2019). Originally assigned to: @zadjii-msft on GitHub. From MSFT:20137864 see: Bug 20108529: [host] virtual bottom does weird things with powershell control-L (see gif) run powershell in a conhost with TerminalScrolling enabled. run `ls` type `# foo` press ctrl+L note that the viewport has moved down so the line with "# foo" is not at the top, and the rest of the viewport is empty. Note the scrollbar size. scroll up with the mouse so that the cursor is no longer visible. type a character. expected: * the viewport will snap so that the line with the cursor is now at the top, like it was before scrolling. actual: * the viewport will snap so that the line with the cursor is now at the bottom of the viewport. ---- This is definitely due to PSReadline, who implements the ^L handling. I presume they're making the cursor visible manually, but I don't care to dig in too deep right now.
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 Priority-2 Product-Conhost Resolution-Fix-Committed
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#1620
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?