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

Peek behind Alternate Screen Buffer, like Flip Screen (Alt+F12) in mintty of Git Bash #8954

New Issue
Open
opened 2026-01-31 01:42:20 +00:00 by claunia · 1 comment
claunia commented 2026-01-31 01:42:20 +00:00
Owner
Copy Link

Originally created by @KalleOlaviNiemitalo on GitHub (Jun 10, 2020).

Description of the new feature/enhancement

After a program has activated the alternate screen buffer, I want to view the primary screen buffer and its scrollback and copy some text from them to the clipboard.

For example, I run some other commands and then git commit, which starts the nano editor to edit the commit message. The editor activates the alternate screen buffer of the terminal. I then want to look at the output of the previous commands and copy parts of it to the commit message, but the last page of output is hidden behind the editor's screen.

Proposed technical implementation details (optional)

Add a command similar to Flip Screen (Alt+F12) in mintty of Git Bash, and let me bind that to a key combination. The command makes the primary screen buffer temporarily visible but keeps the alternate screen buffer active. It does not report this change to applications. I can then scroll back and forth, select text, and copy it to the clipboard. If I run the same command again or type something, then the alternate screen buffer becomes visible again. (If a program outputs something to the alternate screen buffer, I think the primary screen buffer should remain visible, but that is not very important.)

Implementing https://github.com/microsoft/terminal/issues/3492 first might make this easier.

Originally created by @KalleOlaviNiemitalo on GitHub (Jun 10, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> # Description of the new feature/enhancement <!-- A clear and concise description of what the problem is that the new feature would solve. Describe why and how a user would use this new functionality (if applicable). --> After a program has activated the alternate screen buffer, I want to view the primary screen buffer and its scrollback and copy some text from them to the clipboard. For example, I run some other commands and then `git commit`, which starts the `nano` editor to edit the commit message. The editor activates the alternate screen buffer of the terminal. I then want to look at the output of the previous commands and copy parts of it to the commit message, but the last page of output is hidden behind the editor's screen. # Proposed technical implementation details (optional) <!-- A clear and concise description of what you want to happen. --> Add a command similar to Flip Screen (Alt+F12) in mintty of Git Bash, and let me bind that to a key combination. The command makes the primary screen buffer temporarily visible but keeps the alternate screen buffer active. It does not report this change to applications. I can then scroll back and forth, select text, and copy it to the clipboard. If I run the same command again or type something, then the alternate screen buffer becomes visible again. (If a program outputs something to the alternate screen buffer, I think the primary screen buffer should remain visible, but that is not very important.) Implementing <https://github.com/microsoft/terminal/issues/3492> first might make this easier.
claunia added the Issue-FeatureProduct-TerminalArea-TerminalControl labels 2026-01-31 01:42:20 +00:00
claunia commented 2026-01-31 01:42:21 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jun 10, 2020):

I think this is a fine idea, probably requires #381 even before #3492 😉

@zadjii-msft commented on GitHub (Jun 10, 2020): I think this is a fine idea, probably requires #381 even before #3492 😉
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-TerminalControl Issue-Feature Product-Terminal
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#8954
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?