Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
KalleOlaviNiemitalo opened this issue Jun 10, 2020 · 1 comment
Labels
Area-TerminalControl Issues pertaining to the terminal control (input, selection, keybindings, mouse interaction, etc.) Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Product-Terminal The new Windows Terminal.
Milestone

Comments

@KalleOlaviNiemitalo
Copy link

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 #3492 first might make this easier.

@KalleOlaviNiemitalo KalleOlaviNiemitalo added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Jun 10, 2020
@ghost ghost added Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Jun 10, 2020
@zadjii-msft
Copy link
Member

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

@zadjii-msft zadjii-msft added Area-TerminalControl Issues pertaining to the terminal control (input, selection, keybindings, mouse interaction, etc.) Product-Terminal The new Windows Terminal. labels Jun 10, 2020
@ghost ghost removed the Needs-Tag-Fix Doesn't match tag requirements label Jun 10, 2020
@zadjii-msft zadjii-msft added this to the Terminal Backlog milestone Jun 10, 2020
@DHowett DHowett removed the Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting label Jun 11, 2020
@zadjii-msft zadjii-msft modified the milestones: Terminal Backlog, Backlog Jan 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-TerminalControl Issues pertaining to the terminal control (input, selection, keybindings, mouse interaction, etc.) Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Product-Terminal The new Windows Terminal.
Projects
None yet
Development

No branches or pull requests

3 participants