starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-09-25 00:15:10 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Windows cannot scroll up or down in Screen mode #18131

New Issue
Closed
opened 2026-01-31 06:04:30 +00:00 by claunia · 9 comments
claunia commented 2026-01-31 06:04:30 +00:00
Owner
Copy Link

Originally created by @hijkzzz on GitHub (Aug 9, 2022).

Windows Terminal version

1.14.1963.0

Windows build number

Win10 or Win11 x64

Other Software

No response

Steps to reproduce

Connect to any ubuntu 20.04 server or WSL2
screen -S test
Enter a lot of commands
You'll find that you can't scroll through commands that are off-screen

Expected Behavior

I can scroll up and down to view the history commands

Actual Behavior

I can't scroll up and down to view the history commands

Originally created by @hijkzzz on GitHub (Aug 9, 2022). ### Windows Terminal version 1.14.1963.0 ### Windows build number Win10 or Win11 x64 ### Other Software _No response_ ### Steps to reproduce Connect to any ubuntu 20.04 server or WSL2 screen -S test Enter a lot of commands You'll find that you can't scroll through commands that are off-screen ### Expected Behavior I can scroll up and down to view the history commands ### Actual Behavior I can't scroll up and down to view the history commands
claunia added the Issue-BugResolution-Duplicate labels 2026-01-31 06:04:30 +00:00
claunia commented 2026-01-31 06:04:31 +00:00
Author
Owner
Copy Link

@j4james commented on GitHub (Aug 9, 2022):

I'm afraid this is just the way screen works. See #13670.

@j4james commented on GitHub (Aug 9, 2022): I'm afraid this is just the way `screen` works. See #13670.
claunia commented 2026-01-31 06:04:31 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 9, 2022):

Yep.

/dup #13670

@zadjii-msft commented on GitHub (Aug 9, 2022): Yep. /dup #13670
claunia commented 2026-01-31 06:04:32 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Aug 9, 2022):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (Aug 9, 2022): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
claunia commented 2026-01-31 06:04:32 +00:00
Author
Owner
Copy Link

@hijkzzz commented on GitHub (Aug 9, 2022):

However, both iTerm2 and VSCode support this feature well~

@hijkzzz commented on GitHub (Aug 9, 2022): However, both iTerm2 and VSCode support this feature well~
claunia commented 2026-01-31 06:04:32 +00:00
Author
Owner
Copy Link

@j4james commented on GitHub (Aug 9, 2022):

@hijkzzz Screen manages the scrollback history itself, since you can have multiple sessions, each with their own history, so it doesn't make much sense to use the terminal's scrollback. But if that's really what you want, you can configure that in your .screenrc as described here:

https://stackoverflow.com/a/1125947

@j4james commented on GitHub (Aug 9, 2022): @hijkzzz Screen manages the scrollback history itself, since you can have multiple sessions, each with their own history, so it doesn't make much sense to use the terminal's scrollback. But if that's really what you want, you can configure that in your .screenrc as described here: https://stackoverflow.com/a/1125947
claunia commented 2026-01-31 06:04:33 +00:00
Author
Owner
Copy Link

@hijkzzz commented on GitHub (Aug 13, 2022):

@hijkzzz Screen manages the scrollback history itself, since you can have multiple sessions, each with their own history, so it doesn't make much sense to use the terminal's scrollback. But if that's really what you want, you can configure that in your .screenrc as described here:

https://stackoverflow.com/a/1125947

Hi, this solution is not easy to use. How can I roll back WS Terminal to a version that supports screen rolling?

@hijkzzz commented on GitHub (Aug 13, 2022): > @hijkzzz Screen manages the scrollback history itself, since you can have multiple sessions, each with their own history, so it doesn't make much sense to use the terminal's scrollback. But if that's really what you want, you can configure that in your .screenrc as described here: > > https://stackoverflow.com/a/1125947 Hi, this solution is not easy to use. How can I roll back WS Terminal to a version that supports screen rolling?
claunia commented 2026-01-31 06:04:33 +00:00
Author
Owner
Copy Link

@kushwavez commented on GitHub (Oct 17, 2022):

Just a note on this:
This issue was affecting my work as I mostly work with screens. After I don't know what release update it suddenly didn't work, I started using Hyper as an alternative, but because it crashed 3 times now in critical times I decided to try and "fix" this issue with the Windows Terminal.

After I rolled back to v1.13.11432.0 the issue was not there, so something is changed around the new releases.
I'll stay on this ver until a fix is developed for this.

@kushwavez commented on GitHub (Oct 17, 2022): Just a note on this: This issue was affecting my work as I mostly work with screens. After I don't know what release update it suddenly didn't work, I started using Hyper as an alternative, but because it crashed 3 times now in critical times I decided to try and "fix" this issue with the Windows Terminal. After I rolled back to v1.13.11432.0 the issue was not there, so something is changed around the new releases. I'll stay on this ver until a fix is developed for this.
claunia commented 2026-01-31 06:04:34 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Oct 17, 2022):

Unfortunately, a fix will not be developed for this. There's a better description of what's up in https://github.com/microsoft/terminal/issues/13670, as well as James' comments here.

We are not intending on breaking alternate screen buffer support, as it is a critical underpinning of any application that wants control over the entire screen... such as screen.

@DHowett commented on GitHub (Oct 17, 2022): Unfortunately, a fix will not be developed for this. There's a better description of what's up in https://github.com/microsoft/terminal/issues/13670, as well as James' comments here. We are not intending on breaking alternate screen buffer support, as it is a critical underpinning of any application that wants control over the entire screen... such as `screen`.
claunia commented 2026-01-31 06:04:34 +00:00
Author
Owner
Copy Link

@urza commented on GitHub (Oct 6, 2023):

https://stackoverflow.com/a/1125947

This has worked for me. I did exactly what the SO answers suggestst and now I can scroll in screen sessions from Windows Trerminal.

@urza commented on GitHub (Oct 6, 2023): https://stackoverflow.com/a/1125947 This has worked for me. I did exactly what the SO answers suggestst and now I can scroll in screen sessions from Windows Trerminal.
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 Resolution-Duplicate
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#18131
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?