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

Feature request: automatic splits similar to tiling window managers #5559

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

Originally created by @ericist on GitHub (Dec 13, 2019).

Originally assigned to: @zadjii-msft on GitHub.

Description of the new feature/enhancement

Creating new splits could be made easier by providing a keybinding that automatically splits the currently active pane based on the current split type, similar to tiling window managers such as bspwm.

When activating the keybinding (e.g. Alt+Shift+Enter) following would happen:
If no split exists yet, the terminal would be split vertically. If a split exists and the currently active pane is part of a vertical split, it would be split horizontally and vice versa.

This is also visualized in the documentation of bspwm
Additionally, other schemes such as a spiral scheme could also be implemented

Proposed technical implementation details (optional)

The implementation could in theory be very simple: Just query the split type of the active pane
(vertical/horizontal) and create a new split of the other type when pressing the keybinding.

I would try to implement this feature myself but unfortunatley do not have the time at the moment.

Originally created by @ericist on GitHub (Dec 13, 2019). Originally assigned to: @zadjii-msft on GitHub. <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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 Creating new splits could be made easier by providing a keybinding that automatically splits the currently active pane based on the current split type, similar to tiling window managers such as bspwm. When activating the keybinding (e.g. Alt+Shift+Enter) following would happen: If no split exists yet, the terminal would be split vertically. If a split exists and the currently active pane is part of a vertical split, it would be split horizontally and vice versa. This is also visualized in [the documentation of bspwm](https://github.com/baskerville/bspwm#longest-side-scheme) Additionally, other schemes such as a [spiral scheme](https://github.com/baskerville/bspwm#spiral-scheme) could also be implemented <!-- 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). --> # Proposed technical implementation details (optional) The implementation could in theory be very simple: Just query the split type of the active pane (vertical/horizontal) and create a new split of the other type when pressing the keybinding. I would try to implement this feature myself but unfortunatley do not have the time at the moment. <!-- A clear and concise description of what you want to happen. -->
claunia commented 2026-01-31 00:16:05 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Dec 13, 2019):

Okay so this sounds like two different requests here

  1. Use the current profile for creating a new split. This is already tracked by #1756, so let's direct that discussion to that thread.
  2. "automatic" or "spiral" split mode - I don't hate this. And with horizontal and vertical already being parameters for splitPane, we could totally extend that to split in automatic ways like this.
@zadjii-msft commented on GitHub (Dec 13, 2019): Okay so this sounds like _two_ different requests here 1. Use the current profile for creating a new split. This is already tracked by #1756, so let's direct that discussion to that thread. 2. "automatic" or "spiral" split mode - I don't hate this. And with `horizontal` and `vertical` already being parameters for `splitPane`, we could totally extend that to split in automatic ways like this.
claunia commented 2026-01-31 00:16:05 +00:00
Author
Owner
Copy Link

@ericist commented on GitHub (Dec 13, 2019):

You're right, I didn't think about different profiles because I currently only use one.

Simply alternating the split types would propably be way easier to implement than
something more complex like a spiral (sometimes also called fibonacci) mode (which personally
I find not very useful anyway, I just wanted to give another example).

If this would be implemented there could also be a split ratio parameter (also found in bspwm)
which decides if a new split should split the current pane in the middle (ratio 50%) or at another point.

@ericist commented on GitHub (Dec 13, 2019): You're right, I didn't think about different profiles because I currently only use one. Simply alternating the split types would propably be way easier to implement than something more complex like a spiral (sometimes also called fibonacci) mode (which personally I find not very useful anyway, I just wanted to give another example). If this would be implemented there could also be a split ratio parameter (also found in bspwm) which decides if a new split should split the current pane in the middle (ratio 50%) or at another point.
claunia commented 2026-01-31 00:16:05 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jan 14, 2020):

:tada:This issue was addressed in #4025, which has now been successfully released as Windows Terminal Preview v0.8.10091.0.🎉

Handy links:

@ghost commented on GitHub (Jan 14, 2020): :tada:This issue was addressed in #4025, which has now been successfully released as `Windows Terminal Preview v0.8.10091.0`.:tada: Handy links: * [Release Notes](https://github.com/microsoft/terminal/releases/tag/v0.8.10091.0) * [Store Download](https://www.microsoft.com/store/apps/9n0dx20hk701?cid=storebadge&ocid=badge)
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-UserInterface Issue-Task Product-Terminal Resolution-Fix-Committed
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#5559
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?