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

Terminal shows previous mangled buffer text when scrolling up after a resize action #20935

New Issue
Closed
opened 2026-01-31 07:28:16 +00:00 by claunia · 2 comments
claunia commented 2026-01-31 07:28:16 +00:00
Owner
Copy Link

Originally created by @AmerM137 on GitHub (Dec 1, 2023).

Windows Terminal version

1.18.3181.0

Windows build number

10.0.19045.3693

Other Software

micro text editor 2.0.13 -- https://github.com/zyedidia/micro
nano for windows 7.2-22.1 -- https://github.com/okibcn/nano-for-windows
Capture

Steps to reproduce

Scrollbar visibility == Hidden, History size == 9001
Launch windows terminal, launch micro text editor. Write a few lines, resize terminal (larger->smaller or smaller->larger). Resizing unlocks ability to scroll up using keyboard bindings or using mouse select. Previous buffer shows with characters jumbled up / misaligned.

Same issue using windows terminal with nano editor.
Same issue using wezterm with both micro and nano.
Same issue using alacritty with both micro and nano.
Tested with nvim. No issue with nvim on all terminal emulators (cannot scroll back after resizing). This should be actual behavior for all editors.

Expected Behavior

Text should be redrawn normally and inability to scroll back should be maintained.

Actual Behavior

Resizing "unlocks" scrolling again, causing previous ghost text/buffers to show up. Particularly annoying when trying to drag-select with the mouse near the top of the file. Very confusing when seeing the previous buffers, especially when the text is all misaligned.

Originally created by @AmerM137 on GitHub (Dec 1, 2023). ### Windows Terminal version 1.18.3181.0 ### Windows build number 10.0.19045.3693 ### Other Software micro text editor 2.0.13 -- https://github.com/zyedidia/micro nano for windows 7.2-22.1 -- https://github.com/okibcn/nano-for-windows ![Capture](https://github.com/microsoft/terminal/assets/37887075/709b6388-2c09-4f67-afd6-1f3f6d779cd7) ### Steps to reproduce Scrollbar visibility == Hidden, History size == 9001 Launch windows terminal, launch micro text editor. Write a few lines, resize terminal (larger->smaller or smaller->larger). Resizing unlocks ability to scroll up using keyboard bindings or using mouse select. Previous buffer shows with characters jumbled up / misaligned. Same issue using windows terminal with nano editor. Same issue using wezterm with both micro and nano. Same issue using alacritty with both micro and nano. Tested with nvim. **No issue with nvim on all terminal emulators** (cannot scroll back after resizing). This should be actual behavior for all editors. ### Expected Behavior Text should be redrawn normally and inability to scroll back should be maintained. ### Actual Behavior Resizing "unlocks" scrolling again, causing previous ghost text/buffers to show up. Particularly annoying when trying to drag-select with the mouse near the top of the file. Very confusing when seeing the previous buffers, especially when the text is all misaligned.
claunia added the Needs-TriageIssue-BugResolution-External labels 2026-01-31 07:28:17 +00:00
claunia commented 2026-01-31 07:28:18 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Dec 2, 2023):

(I'm about to leave for the day, so just dropping some notes in here.)

This typically happens when a text editor is not properly using the "Xterm Alternate Screen Buffer". That's a mode that (1) restricts all scrolling and (2) ensures that nothing on the screen gets put into the scrollback buffer.

I wonder if applications are not aware that it exists on Windows, or perhaps their language runtimes don't allow them to use it.

@DHowett commented on GitHub (Dec 2, 2023): (I'm about to leave for the day, so just dropping some notes in here.) This typically happens when a text editor is not properly using the "Xterm Alternate Screen Buffer". That's a mode that (1) restricts all scrolling and (2) ensures that nothing on the screen gets put into the scrollback buffer. I wonder if applications are not aware that it exists on Windows, or perhaps their language runtimes don't allow them to use it.
claunia commented 2026-01-31 07:28:18 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Dec 13, 2023):

Thanks for filing! Looks like this is being handled over in https://github.com/zyedidia/micro/issues/3073 so I'm going to close this as external.

@carlos-zamora commented on GitHub (Dec 13, 2023): Thanks for filing! Looks like this is being handled over in https://github.com/zyedidia/micro/issues/3073 so I'm going to close this as external.
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-Bug Needs-Triage 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#20935
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?