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

Invoking "screen" from Ubuntu bash shell causes scrollbar (and buffer?) to disappear. #18100

New Issue
Closed
opened 2026-01-31 06:03:38 +00:00 by claunia · 4 comments
claunia commented 2026-01-31 06:03:38 +00:00
Owner
Copy Link

Originally created by @ossumpossum on GitHub (Aug 4, 2022).

Windows Terminal version

1.14.1962.0

Windows build number

10.0.19044.1826

Other Software

Screen version 4.08.00 (GNU) 05-Feb-20

Steps to reproduce

Start a new Ubuntu bash shell in Windows Terminal.

run "ls -la" several times until the content scrolls off the screen. Note the presence of the scrollbar on the right, and the ability to use the mouse wheel or the scrollbar to scroll back through the content.

Start "screen" via "screen -D -RR".

In the screen session, perform the same "ls -la" steps above. Note the absence of the scrollbar on the right, and the inability to use the mouse wheel or the scrollbar to scroll back through the content.

Expected Behavior

One should be able to scroll back through content independent of the program being run or the TERM environment variable setting (normal bash: xterm-256color; screen: screen.xterm-256color).

Actual Behavior

One loses the ability to scroll back through content once inside "screen".

Originally created by @ossumpossum on GitHub (Aug 4, 2022). ### Windows Terminal version 1.14.1962.0 ### Windows build number 10.0.19044.1826 ### Other Software Screen version 4.08.00 (GNU) 05-Feb-20 ### Steps to reproduce Start a new Ubuntu bash shell in Windows Terminal. run "ls -la" several times until the content scrolls off the screen. Note the presence of the scrollbar on the right, and the ability to use the mouse wheel or the scrollbar to scroll back through the content. Start "screen" via "screen -D -RR". In the screen session, perform the same "ls -la" steps above. Note the absence of the scrollbar on the right, and the inability to use the mouse wheel or the scrollbar to scroll back through the content. ### Expected Behavior One should be able to scroll back through content independent of the program being run or the TERM environment variable setting (normal bash: xterm-256color; screen: screen.xterm-256color). ### Actual Behavior One loses the ability to scroll back through content once inside "screen".
claunia commented 2026-01-31 06:03:40 +00:00
Author
Owner
Copy Link

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

Yep, that's just how the alternate screen buffer (\x1b[?1049h) works. You'll see this is pretty consistent in most terminal emulators - for example, gnome-terminal:

gh-13670

Admittedly, Windows Terminal didn't support this correctly at all until very recently.

@zadjii-msft commented on GitHub (Aug 4, 2022): Yep, that's just how the alternate screen buffer (`\x1b[?1049h`) works. You'll see this is pretty consistent in most terminal emulators - for example, `gnome-terminal`: ![gh-13670](https://user-images.githubusercontent.com/18356694/182870300-8d7c5049-cd95-47f3-91ad-84902c0360b7.gif) Admittedly, Windows Terminal didn't support this correctly at all until very recently.
claunia commented 2026-01-31 06:03:40 +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:03:40 +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.

@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.
claunia commented 2026-01-31 06:03:40 +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 Issue-Question Needs-Tag-Fix Needs-Triage Resolution-Answered
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#18100
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?