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

[discussion] Disable/pause automatic scroll down #10293

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

Originally created by @vadimkantorov on GitHub (Aug 26, 2020).

A usecase: a long-running build process that prints occasionally noteworthy things to terminal. I scroll up and want to read them or copy them. However when new output from build appears on screen, the terminal automatically scrolls down (even if I'm still dragging scrollbar by mouse).

In this usecase we would like to disable automatic scroll down and let the user inspect the previous output. Some options to support this usecase: disable this altogether (the user should scroll down themselves to resume auto-scroll-down); provide some keyboard/UI shortcut to enable this.

I think Gnome Terminal doesn't do this, but I don't remember for sure.

Originally created by @vadimkantorov on GitHub (Aug 26, 2020). A usecase: a long-running build process that prints occasionally noteworthy things to terminal. I scroll up and want to read them or copy them. However when new output from build appears on screen, the terminal automatically scrolls down (even if I'm still dragging scrollbar by mouse). In this usecase we would like to disable automatic scroll down and let the user inspect the previous output. Some options to support this usecase: disable this altogether (the user should scroll down themselves to resume auto-scroll-down); provide some keyboard/UI shortcut to enable this. I think Gnome Terminal doesn't do this, but I don't remember for sure.
claunia added the Issue-QuestionNeeds-TriageNeeds-Tag-FixResolution-Answered labels 2026-01-31 02:17:31 +00:00
claunia commented 2026-01-31 02:17:32 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Aug 26, 2020):

Thanks! So, there’s a couple issues at play here.

We recently (1.2) implemented scroll locking when you are scrolled up or have an active selection. That part is automatic and unconfigurable. Scrolling will snap back when you press Print Screen a key that sends input (😉).

We had (fixed in #7247) a bug where we would let the buffer roll underneath the locked scroll region. The fix is about to come out with 1.2.2381.0.

We also have a critical lack of support for infinite scrollback, so you have between 9001 and 32k lines, depending on how you configured Terminal, to print out before the locked scroll region will age out. I can’t pull that issue up in quicksearch on my phone.

With those two things noted, do we need further discussion? 😄

@DHowett commented on GitHub (Aug 26, 2020): Thanks! So, there’s a couple issues at play here. We recently (1.2) implemented scroll locking when you are scrolled up or have an active selection. That part is automatic and unconfigurable. Scrolling will snap back when you press ~Print Screen~ a key that sends input (😉). We had (fixed in #7247) a bug where we would let the buffer roll underneath the locked scroll region. The fix is about to come out with 1.2.2381.0. We also have a critical lack of support for infinite scrollback, so you have between 9001 and 32k lines, depending on how you configured Terminal, to print out before the locked scroll region will age out. I can’t pull that issue up in quicksearch on my phone. With those two things noted, do we need further discussion? 😄
claunia commented 2026-01-31 02:17:33 +00:00
Author
Owner
Copy Link

@vadimkantorov commented on GitHub (Aug 26, 2020):

No, I think we're good :) It would be fantastic to have this scenario to added on your functional testing usecase list or something like that :)

One minor detail is that it can be hard to re-enable back auto-scrolling when the scrollbar became small enough or new text appears fast - so some slack/docking there would be good

@vadimkantorov commented on GitHub (Aug 26, 2020): No, I think we're good :) It would be fantastic to have this scenario to added on your functional testing usecase list or something like that :) One minor detail is that it can be hard to re-enable back auto-scrolling when the scrollbar became small enough or new text appears fast - so some slack/docking there would be good
claunia commented 2026-01-31 02:17:33 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 26, 2020):

Oh don't worry, we've already got the test covered.

Thanks for following up!

@zadjii-msft commented on GitHub (Aug 26, 2020): Oh don't worry, we've already [got the test covered](https://github.com/microsoft/terminal/blob/master/src/cascadia/UnitTests_TerminalCore/TerminalBufferTests.cpp#L155). Thanks for following up!
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 Issue-Question Needs-Tag-Fix Needs-Triage Resolution-Answered
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#10293
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?