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

Scrolling doesn't work properly in latest insider beta #155

New Issue
Closed
opened 2026-01-30 21:44:07 +00:00 by claunia · 8 comments
claunia commented 2026-01-30 21:44:07 +00:00
Owner
Copy Link

Originally created by @bitcrazed on GitHub (Feb 16, 2018).

Originally assigned to: @zadjii-msft on GitHub.

From @warpdesign on April 22, 2017 10:22

This bug-tracker is monitored by developers and other technical types. We like detail! So please use this form and tell us, concisely but precisely, what's up. Please fill out ALL THE FIELDS!

If you have a feature request, please post to the UserVoice. If you're reporting a BSOD, don't post here! Instead, e-mail "secure@microsoft.com", and if possible attach the minidump from "C:\Windows\minidump".

  • Your Windows build number: (Type ver at a Windows Command Prompt)
    10.0.16179

  • What you're doing and what's happening: (Copy&paste specific commands and their output, or include screen shots)
    I ran npm installed which produced lots of output text and wanted to scroll up to read the text I missed.

  • What's wrong / what should be happening instead:
    Instead of seeing the output from the command I just typed, I saw output from a command I ran hours ago.

  • Strace of the failing command, if applicable: (If <cmd> is failing, then run strace -o strace.txt -ff <cmd>, and post the strace.txt output here)

Copied from original issue: Microsoft/WSL#1984

Originally created by @bitcrazed on GitHub (Feb 16, 2018). Originally assigned to: @zadjii-msft on GitHub. _From @warpdesign on April 22, 2017 10:22_ This bug-tracker is monitored by developers and other technical types. We like detail! So please use this form and tell us, concisely but precisely, what's up. Please fill out ALL THE FIELDS! If you have a feature request, please post to [the UserVoice](https://wpdev.uservoice.com/forums/266908). If you're reporting a BSOD, don't post here! Instead, e-mail "secure@microsoft.com", and if possible attach the minidump from "C:\Windows\minidump\". * Your Windows build number: (Type `ver` at a Windows Command Prompt) 10.0.16179 * What you're doing and what's happening: (Copy&paste specific commands and their output, or include screen shots) I ran npm installed which produced lots of output text and wanted to scroll up to read the text I missed. * What's wrong / what should be happening instead: Instead of seeing the output from the command I just typed, I saw output from a command I ran hours ago. * Strace of the failing command, if applicable: (If `<cmd>` is failing, then run `strace -o strace.txt -ff <cmd>`, and post the strace.txt output here) _Copied from original issue: Microsoft/WSL#1984_
claunia added the Product-ConhostResolution-Fix-Committed labels 2026-01-30 21:44:07 +00:00
claunia commented 2026-01-30 21:44:07 +00:00
Author
Owner
Copy Link

@bitcrazed commented on GitHub (Feb 16, 2018):

From @zadjii-msft on April 24, 2017 15:39

Gonna go out on a limb and say this has to do with the scroll margins, again.

MSFT:11647773 currently tracks what I think is this issue, though I'll add this to that bug to make sure they're the same.

@warpdesign any chance that before you ran npm install ..., you had run apt install ...? I'm pretty sure that apt is a reliable repro for this behavior, but I don't know if npm is yet.

@bitcrazed commented on GitHub (Feb 16, 2018): _From @zadjii-msft on April 24, 2017 15:39_ Gonna go out on a limb and say this has to do with the scroll margins, again. MSFT:11647773 currently tracks what I think is this issue, though I'll add this to that bug to make sure they're the same. @warpdesign any chance that before you ran `npm install ...`, you had run `apt install ...`? I'm pretty sure that `apt` is a reliable repro for this behavior, but I don't know if `npm` is yet.
claunia commented 2026-01-30 21:44:08 +00:00
Author
Owner
Copy Link

@bitcrazed commented on GitHub (Feb 16, 2018):

From @Po-wei on May 12, 2017 5:52

I have the same scrolling problem, too. What's more, when I encounter this issue, typing "clear" would let me cannot scroll up(The scrolling bar was fixed on the top, and the previous information was gone.)

@bitcrazed commented on GitHub (Feb 16, 2018): _From @Po-wei on May 12, 2017 5:52_ I have the same scrolling problem, too. What's more, when I encounter this issue, typing "clear" would let me cannot scroll up(The scrolling bar was fixed on the top, and the previous information was gone.)
claunia commented 2026-01-30 21:44:08 +00:00
Author
Owner
Copy Link

@bitcrazed commented on GitHub (Feb 16, 2018):

From @zadjii-msft on May 30, 2017 22:31

Wadda ya know, I fixed this issue this morning. On it's way out to Insider's now :)

@bitcrazed commented on GitHub (Feb 16, 2018): _From @zadjii-msft on May 30, 2017 22:31_ Wadda ya know, I fixed this issue this morning. On it's way out to Insider's now :)
claunia commented 2026-01-30 21:44:08 +00:00
Author
Owner
Copy Link

@bitcrazed commented on GitHub (Feb 16, 2018):

From @Po-wei on June 3, 2017 8:11

@zadjii-msft When can i get this update from regular Windows Update?

@bitcrazed commented on GitHub (Feb 16, 2018): _From @Po-wei on June 3, 2017 8:11_ @zadjii-msft When can i get this update from regular Windows Update?
claunia commented 2026-01-30 21:44:08 +00:00
Author
Owner
Copy Link

@bitcrazed commented on GitHub (Feb 16, 2018):

From @zadjii-msft on June 5, 2017 16:16

If you're not on Insiders, then I think the best I can tell you is SoonTM. It'll come out with the Fall Creator's Update, but I don't know when that will officially be released.

@bitcrazed commented on GitHub (Feb 16, 2018): _From @zadjii-msft on June 5, 2017 16:16_ If you're not on Insiders, then I think the best I can tell you is Soon<sup>TM</sup>. It'll come out with the Fall Creator's Update, but I don't know when that will officially be released.
claunia commented 2026-01-30 21:44:08 +00:00
Author
Owner
Copy Link

@bitcrazed commented on GitHub (Feb 16, 2018):

From @MerkaST on December 6, 2017 23:17

This appears to still happen with the Fall Creator's Update. I'm on build 16299.64 and running an apt install (or remove or autoremove, I'd assume all commands that use the progress bar) command that produces output longer than one window right after opening WSL will exhibit this behaviour, ie. have missing scrollback content.

@bitcrazed commented on GitHub (Feb 16, 2018): _From @MerkaST on December 6, 2017 23:17_ This appears to still happen with the Fall Creator's Update. I'm on build 16299.64 and running an `apt install` (or remove or autoremove, I'd assume all commands that use the progress bar) command that produces output longer than one window right after opening WSL will exhibit this behaviour, ie. have missing scrollback content.
claunia commented 2026-01-30 21:44:08 +00:00
Author
Owner
Copy Link

@bitcrazed commented on GitHub (Feb 16, 2018):

From @zadjii-msft on December 8, 2017 17:32

Hmmm. Okay so i think I get what's happening. Basically, the "scroll margins" that apt sets are at a fixed point in the buffer. So anything that would scrollback off of it, is just lost instead.

The right way to do this is to probably instead shift the whole viewport down a line (including the buffer-relative margin settings), then scroll the contents of the margins up a line, so that the top line is off of the viewport, in the "scrollback".

Filing a new bug to take a look at this later this release cycle.

@bitcrazed commented on GitHub (Feb 16, 2018): _From @zadjii-msft on December 8, 2017 17:32_ Hmmm. Okay so i think I get what's happening. Basically, the "scroll margins" that apt sets are at a fixed point in the buffer. So anything that would scrollback off of it, is just lost instead. The right way to do this is to probably instead shift the whole viewport down a line (including the buffer-relative margin settings), then scroll the contents of the margins up a line, so that the top line is off of the viewport, in the "scrollback". Filing a new bug to take a look at this later this release cycle.
claunia commented 2026-01-30 21:44:09 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 19, 2018):

I just submitted a bug fix that should fix the issue of apt install output not getting moved into scrollback when it scrolls off the top of the viewport.

Should be in whatever the next official Windows release is called (2Fall2CreatorsUpdate)

@zadjii-msft commented on GitHub (Jul 19, 2018): I just submitted a bug fix that should fix the issue of `apt install` output not getting moved into scrollback when it scrolls off the top of the viewport. Should be in whatever the next official Windows release is called (2Fall2CreatorsUpdate)
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 Product-Conhost 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#155
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?