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

Feature: Maximize split keyboard shortcut #6691

New Issue
Closed
opened 2026-01-31 00:44:52 +00:00 by claunia · 2 comments
claunia commented 2026-01-31 00:44:52 +00:00
Owner
Copy Link

Originally created by @IgnusG on GitHub (Mar 2, 2020).

Description of the new feature/enhancement

The shortcut would, on a screen with multiple splits, hide other splits and resize the current split to the whole window. Upon pressing the shortcut again, this would revert the split to its original size and position among the other splits.

What is this for?

Imagine having a split with vim left, build with file watcher on the right. You save your vim file and the build fires up compiling your files. Suddenly a wild bug appears and the whole right split is covered in red. There's too much and the long (multi line) text makes it difficult to read.

Solution now:

  1. Resize the right split up so it covers more of the window - you need multiple key presses and the vim split resizes as well causing a re-render (all kinds of visual annoyances)
  2. Use a tab instead of a split for the build - if you forget to do this you can only restart the build on a new window and close the split (might as well just go with number one)

Solution with this feature:

  1. Press a single key combination. The build split covers the whole window (vim cannot be seen). Debug in peace. Press it again and the split layout is restored. Switch to vim and for added bonus press it again so you can now "maximize" the vim screen to focus on it while fixing the bug.

The problems

  1. How to indicate a split is maximized? (maybe the split's (white/color) border around the inside of whole window? some text or indicator in the tab?)

How it would look like

image

image

References

Something similar just for vim (vim splits) I use: https://github.com/timfeirg/ZoomWin

Proposed technical implementation details (optional)

Not entirely sure how the split mechanism is designed, but if possible place the maximizing split over all other splits and fill window (leave other splits original size behind it) -> transparent background?

I'm not yet familiar with the repository code - my apologies for the lack of further info. And for anyone feel free to add or extend this issue 👍

Originally created by @IgnusG on GitHub (Mar 2, 2020). # Description of the new feature/enhancement The shortcut would, on a screen with multiple splits, hide other splits and resize the current split to the whole window. Upon pressing the shortcut again, this would revert the split to its original size and position among the other splits. ### What is this for? Imagine having a split with vim left, build with file watcher on the right. You save your vim file and the build fires up compiling your files. Suddenly a **wild** bug appears and the whole right split is covered in red. There's too much and the long (multi line) text makes it difficult to read. #### Solution now: 1. Resize the right split up so it covers more of the window - you need multiple key presses and the vim split resizes as well causing a re-render (all kinds of visual annoyances) 2. Use a tab instead of a split for the build - if you forget to do this you can only restart the build on a new window and close the split (might as well just go with number one) #### Solution with this feature: 1. Press a single key combination. The build split covers the whole window (vim cannot be seen). Debug in peace. Press it again and the split layout is restored. Switch to vim and for *added bonus* press it again so you can now "maximize" the vim screen to focus on it while fixing the bug. ### The problems 1. How to indicate a split is maximized? (maybe the split's (white/color) border around the inside of whole window? some text or indicator in the tab?) ### How it would look like ![image](https://user-images.githubusercontent.com/6438760/75665059-d8695e80-5c73-11ea-969e-96e7a8e74d42.png) ![image](https://user-images.githubusercontent.com/6438760/75665125-f767f080-5c73-11ea-933e-48b30c6ae79b.png) ### References Something similar just for vim (vim splits) I use: https://github.com/timfeirg/ZoomWin # Proposed technical implementation details (optional) Not entirely sure how the split mechanism is designed, but if possible place the maximizing split over all other splits and fill window (leave other splits original size behind it) -> transparent background? I'm not yet familiar with the repository code - my apologies for the lack of further info. And for anyone feel free to add or extend this issue 👍 <!-- A clear and concise description of what you want to happen. -->
claunia added the Issue-FeatureResolution-Duplicate labels 2026-01-31 00:44:52 +00:00
claunia commented 2026-01-31 00:44:53 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Mar 2, 2020):

Thanks for the suggestion! This is actually already being tracked by another issue on our repo - please refer to #996 for more discussion.

/dup #996

@zadjii-msft commented on GitHub (Mar 2, 2020): Thanks for the suggestion! This is actually already being tracked by another issue on our repo - please refer to #996 for more discussion. /dup #996
claunia commented 2026-01-31 00:44:53 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Mar 2, 2020):

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 (Mar 2, 2020): 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!
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-Feature 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#6691
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?