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

[PR #5122] Correct scrolling invalidation region for tmux in pty w/ bitmap #26120

New Issue
Open
opened 2026-01-31 09:14:04 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 09:14:04 +00:00
Owner
Copy Link

Original Pull Request: https://github.com/microsoft/terminal/pull/5122

State: closed
Merged: Yes

Correct scrolling invalidation region for tmux in pty w/ bitmap

Add tracing for circling and scrolling operations. Fix improper
invalidation within AdjustCursorPosition routine in the subsection about
scrolling down at the bottom with a set of margins enabled.

References

Detailed Description of the Pull Request / Additional comments

  • This occurs when there is a scroll region restriction applied and a
    newline operation is performed to attempt to spin the contents of just
    the scroll region. This is a frequent behavior of tmux.
  • Right now, the Terminal doesn't support any sort of "scroll content"
    operation, so what happens here generally speaking is that the PTY in
    the ConHost will repaint everything when this happens.
  • The PTY when doing AdjustCursorPosition with a scroll region
    restriction would do the following things:
  1. Slide literally everything in the direction it needed to go to take
    advantage of rotating the circular buffer. (This would force a
    repaint in PTY as the PTY always forces repaint when the buffer
    circles.)
  2. Copy the lines that weren't supposed to move back to where they were
    supposed to go.
  3. Backfill the "revealed" region that encompasses what was supposed to
    be the newline.
  • The invalidations for the three operations above were:
  1. Invalidate the number of rows of the delta at the top of the buffer
    (this part was wrong)
  2. Invalidate the lines that got copied back into position (probably
    unnecessary, but OK)
  3. Invalidate the revealed/filled-with-spaces line (this is good).

  • When we were using a simple single rectangle for invalidation, the
    union of the top row of the buffer from 1 and the bottom row of the
    buffer from 2 (and 3 was irrelevant as it was already unioned it)
    resulted in repainting the entire buffer and all was good.

  • When we switched to a bitmap, it dutifully only repainted the top line
    and the bottom two lines as the middle ones weren't a consequence of
    intersect.

  • The logic was wrong. We shouldn't be invalidating rows-from-the-top
    for the amount of the delta. The 1 part should be invalidating
    everything BUT the lines that were invalidated in parts 2 and 3.
    (Arguably part 2 shouldn't be happening at all, but I'm not optimizing
    for that right now.)

  • So this solves it by restoring an entire screen repaint for this sort
    of slide data operation by giving the correct number of invalidated
    lines to the bitmap.

Validation Steps Performed

  • Manual validation with the steps described in #5104
  • Automatic test ConptyRoundtripTests::ScrollWithMargins.

Closes #5104

**Original Pull Request:** https://github.com/microsoft/terminal/pull/5122 **State:** closed **Merged:** Yes --- Correct scrolling invalidation region for tmux in pty w/ bitmap Add tracing for circling and scrolling operations. Fix improper invalidation within AdjustCursorPosition routine in the subsection about scrolling down at the bottom with a set of margins enabled. ## References - Introduced with #5024 ## Detailed Description of the Pull Request / Additional comments - This occurs when there is a scroll region restriction applied and a newline operation is performed to attempt to spin the contents of just the scroll region. This is a frequent behavior of tmux. - Right now, the Terminal doesn't support any sort of "scroll content" operation, so what happens here generally speaking is that the PTY in the ConHost will repaint everything when this happens. - The PTY when doing `AdjustCursorPosition` with a scroll region restriction would do the following things: 1. Slide literally everything in the direction it needed to go to take advantage of rotating the circular buffer. (This would force a repaint in PTY as the PTY always forces repaint when the buffer circles.) 2. Copy the lines that weren't supposed to move back to where they were supposed to go. 3. Backfill the "revealed" region that encompasses what was supposed to be the newline. - The invalidations for the three operations above were: 1. Invalidate the number of rows of the delta at the top of the buffer (this part was wrong) 2. Invalidate the lines that got copied back into position (probably unnecessary, but OK) 3. Invalidate the revealed/filled-with-spaces line (this is good). - When we were using a simple single rectangle for invalidation, the union of the top row of the buffer from 1 and the bottom row of the buffer from 2 (and 3 was irrelevant as it was already unioned it) resulted in repainting the entire buffer and all was good. - When we switched to a bitmap, it dutifully only repainted the top line and the bottom two lines as the middle ones weren't a consequence of intersect. - The logic was wrong. We shouldn't be invalidating rows-from-the-top for the amount of the delta. The 1 part should be invalidating everything BUT the lines that were invalidated in parts 2 and 3. (Arguably part 2 shouldn't be happening at all, but I'm not optimizing for that right now.) - So this solves it by restoring an entire screen repaint for this sort of slide data operation by giving the correct number of invalidated lines to the bitmap. ## Validation Steps Performed - Manual validation with the steps described in #5104 - Automatic test `ConptyRoundtripTests::ScrollWithMargins`. Closes #5104
claunia added the pull-request label 2026-01-31 09:14:04 +00:00
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 pull-request
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#26120
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?