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

Console selection via arrow keys doesn't work when code is multiple pages/scrollable #12538

New Issue
Closed
opened 2026-01-31 03:18:16 +00:00 by claunia · 3 comments
claunia commented 2026-01-31 03:18:16 +00:00
Owner
Copy Link

Originally created by @nkasco on GitHub (Feb 12, 2021).

Regardless of your window size (maximized or any other size) you cannot use the left arrow key to move the input cursor to the beginning of the pipeline. It appears to be bound to the first visible line within your current window size.

Powershell 5, not sure if happens on other consoles.

Example: Paste a multi-lined function into Windows Terminal and hit left arrow (or ctl+left arrow) and you will get an audible beep noise when it cannot scroll back further.

Expected behavior: Should be able to go back to the beginning of your command, not being stuck at the window bound. This works properly from a regular Windows PowerShell window.

image
(Cannot left arrow past the top line)

Originally created by @nkasco on GitHub (Feb 12, 2021). Regardless of your window size (maximized or any other size) you cannot use the left arrow key to move the input cursor to the beginning of the pipeline. It appears to be bound to the first visible line within your current window size. Powershell 5, not sure if happens on other consoles. Example: Paste a multi-lined function into Windows Terminal and hit left arrow (or ctl+left arrow) and you will get an audible beep noise when it cannot scroll back further. Expected behavior: Should be able to go back to the beginning of your command, not being stuck at the window bound. This works properly from a regular Windows PowerShell window. ![image](https://user-images.githubusercontent.com/1930697/107783372-2efe6a00-6d18-11eb-8676-b181d02500af.png) (Cannot left arrow past the top line)
claunia commented 2026-01-31 03:18:17 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Feb 12, 2021):

Does this work on Powershell 7?

This sounds like an issue exacerbated by conpty's buffer being exclusively the size of the terminal window. Probably repros in regular old conhost if you set the buffer height to the viewport height. Sounds like they're not gracefully handling the case where the command takes more lines than the height of the entire buffer.

That being said this would probably also repro with any other terminal emulator too. Hence why I'm thinking this might be fixed in newer versions of powershell. Since newer versions of powershell need to run on other platforms, maybe they found a way to gracefully handle this scenario.

@zadjii-msft commented on GitHub (Feb 12, 2021): Does this work on Powershell 7? This sounds like an issue exacerbated by conpty's buffer being exclusively the size of the terminal window. Probably repros in regular old conhost if you set the buffer height to the viewport height. Sounds like they're not gracefully handling the case where the command takes more lines than the height of the entire buffer. That being said this would probably also repro with any other terminal emulator too. Hence why I'm thinking this might be fixed in newer versions of powershell. Since newer versions of powershell need to run on other platforms, maybe they found a way to gracefully handle this scenario.
claunia commented 2026-01-31 03:18:18 +00:00
Author
Owner
Copy Link

@nkasco commented on GitHub (Feb 12, 2021):

Does this work on Powershell 7?

This sounds like an issue exacerbated by conpty's buffer being exclusively the size of the terminal window. Probably repros in regular old conhost if you set the buffer height to the viewport height. Sounds like they're not gracefully handling the case where the command takes more lines than the height of the entire buffer.

That being said this would probably also repro with any other terminal emulator too. Hence why I'm thinking this might be fixed in newer versions of powershell. Since newer versions of powershell need to run on other platforms, maybe they found a way to gracefully handle this scenario.

Unfortunately it has the same behavior if I open a PS 7 tab in Windows Terminal.

I eluded to this before a bit, but if I open a regular Windows PowerShell window when I do this it gracefully scrolls and moves the cursor as it should. The same with pwsh.

There definitely have been improvements with multi-line commands in Terminal, but this piece does need a bit of work. Otherwise loving it!

@nkasco commented on GitHub (Feb 12, 2021): > Does this work on Powershell 7? > > This sounds like an issue exacerbated by conpty's buffer being exclusively the size of the terminal window. Probably repros in regular old conhost if you set the buffer height to the viewport height. Sounds like they're not gracefully handling the case where the command takes more lines than the height of the entire buffer. > > That being said this would probably also repro with any other terminal emulator too. Hence why I'm thinking this might be fixed in newer versions of powershell. Since newer versions of powershell need to run on other platforms, maybe they found a way to gracefully handle this scenario. Unfortunately it has the same behavior if I open a PS 7 tab in Windows Terminal. I eluded to this before a bit, but if I open a regular Windows PowerShell window when I do this it gracefully scrolls and moves the cursor as it should. The same with pwsh. There definitely have been improvements with multi-line commands in Terminal, but this piece does need a bit of work. Otherwise loving it!
claunia commented 2026-01-31 03:18:18 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Feb 18, 2021):

This is one of the unfortunate side effects of how Terminal has become more compatible with other terminals and less compatible with the Windows Console¹. PSReadline does not properly handle constrained height buffers, and it's something they're slowly working on fixing. It's very, very similar to the cause of https://github.com/PowerShell/PSReadLine/issues/1417.

¹ this also reproduces on the windows console if the buffer height is set to the window height.

Gotta mark this one external, sadly. Sorry!

@DHowett commented on GitHub (Feb 18, 2021): This is one of the unfortunate side effects of how Terminal has become more compatible with _other terminals_ and less compatible with the Windows Console¹. PSReadline does not properly handle constrained height buffers, and it's something they're slowly working on fixing. It's very, very similar to the cause of https://github.com/PowerShell/PSReadLine/issues/1417. ¹ this also reproduces on the windows console if the buffer height is set to the window height. Gotta mark this one external, sadly. Sorry!
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 Needs-Attention Needs-Tag-Fix Needs-Triage Product-Conpty Product-Powershell 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#12538
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?