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

Screen content does not update in tmux #7130

New Issue
Closed
opened 2026-01-31 00:55:55 +00:00 by claunia · 6 comments
claunia commented 2026-01-31 00:55:55 +00:00
Owner
Copy Link

Originally created by @kasper93 on GitHub (Mar 24, 2020).

Originally assigned to: @miniksa on GitHub.

Environment

Windows 10.0.18363.0
tmux over ssh in cygwin

Steps to reproduce

  1. Attach to tmux session
  2. Fill the screen for example with echo test multiple times
  3. Keep printing test, you should alternate with some different text to see if console is scrolled properly.

Expected behavior

Whole screen buffer is redrawn

Actual behavior

Only first line in terminal is redrawn, the rest of the screen space is static and doesn't update while it should. If the output is one line (i.e without new line). If I do echo 'test\n' whole screen is properly redrawn.

Bisect result

This is regression from this commit ca33d895a3 before that everything was working fine.

// CC @miniksa

Originally created by @kasper93 on GitHub (Mar 24, 2020). Originally assigned to: @miniksa on GitHub. # Environment Windows 10.0.18363.0 tmux over ssh in cygwin # Steps to reproduce 1. Attach to tmux session 2. Fill the screen for example with `echo test` multiple times 3. Keep printing `test`, you should alternate with some different text to see if console is scrolled properly. # Expected behavior Whole screen buffer is redrawn # Actual behavior Only first line in terminal is redrawn, the rest of the screen space is static and doesn't update while it should. If the output is one line (i.e without new line). If I do `echo 'test\n'` whole screen is properly redrawn. ## Bisect result This is regression from this commit https://github.com/microsoft/terminal/commit/ca33d895a359664c337c6482b853489823c216d3 before that everything was working fine. // CC @miniksa
claunia commented 2026-01-31 00:55:57 +00:00
Author
Owner
Copy Link

@miniksa commented on GitHub (Mar 25, 2020):

OK I've managed to reproduce this. I think it's a bug that's been there a while and was just hidden by the fact that the previous invalidation-mechanism would coalesce both invalid regions into repainting the entire display. I need to figure out how to dispatch the appropriate content scrolling from the PTY to the Terminal because the entire point of the til::bitmap change was to not re-emit massive amounts of data that are already on the other side of the fence.

@miniksa commented on GitHub (Mar 25, 2020): OK I've managed to reproduce this. I think it's a bug that's been there a while and was just hidden by the fact that the previous invalidation-mechanism would coalesce both invalid regions into repainting the entire display. I need to figure out how to dispatch the appropriate content scrolling from the PTY to the Terminal because the entire point of the `til::bitmap` change was to not re-emit massive amounts of data that are already on the other side of the fence.
claunia commented 2026-01-31 00:55:57 +00:00
Author
Owner
Copy Link

@skyline75489 commented on GitHub (Mar 26, 2020):

I've encountered a similar issue when using Vim in WSL. The majority of content is not being invalidated while scrolling up and down using keyboard.

图片

The actual content should be line 80 - line 107. But only the first and last line is correctly displayed.

@skyline75489 commented on GitHub (Mar 26, 2020): I've encountered a similar issue when using Vim in WSL. The majority of content is not being invalidated while scrolling up and down using keyboard. ![图片](https://user-images.githubusercontent.com/4710575/77597359-98775d80-6f39-11ea-82a7-dc4a42fafa3a.png) The actual content should be line 80 - line 107. But only the first and last line is correctly displayed.
claunia commented 2026-01-31 00:55:57 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Mar 26, 2020):

@skyline75489 while you've got a local build, would you mind trying out https://github.com/microsoft/terminal/pull/5122? It's the speculative fix 😄

@DHowett-MSFT commented on GitHub (Mar 26, 2020): @skyline75489 while you've got a local build, would you mind trying out https://github.com/microsoft/terminal/pull/5122? It's the speculative fix :smile:
claunia commented 2026-01-31 00:55:57 +00:00
Author
Owner
Copy Link

@skyline75489 commented on GitHub (Mar 26, 2020):

@DHowett-MSFT It's working! Vim is back to normal with the help of #5122.

@skyline75489 commented on GitHub (Mar 26, 2020): @DHowett-MSFT It's working! Vim is back to normal with the help of #5122.
claunia commented 2026-01-31 00:55:57 +00:00
Author
Owner
Copy Link

@kasper93 commented on GitHub (Mar 26, 2020):

I can also confirm, working fine with the fix.

@kasper93 commented on GitHub (Mar 26, 2020): I can also confirm, working fine with the fix.
claunia commented 2026-01-31 00:55:57 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Apr 22, 2020):

:tada:This issue was addressed in #5122, which has now been successfully released as Windows Terminal Preview v0.11.1121.0.🎉

Handy links:

@ghost commented on GitHub (Apr 22, 2020): :tada:This issue was addressed in #5122, which has now been successfully released as `Windows Terminal Preview v0.11.1121.0`.:tada: Handy links: * [Release Notes](https://github.com/microsoft/terminal/releases/tag/v0.11.1121.0) * [Store Download](https://www.microsoft.com/store/apps/9n0dx20hk701?cid=storebadge&ocid=badge)
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-Rendering Issue-Bug Priority-1 Product-Conpty 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#7130
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?