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

wt split-pane & wt new-tab commands open a new window #6719

New Issue
Open
opened 2026-01-31 00:45:36 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 00:45:36 +00:00
Owner
Copy Link

Originally created by @ranyitz on GitHub (Mar 3, 2020).

Environment

Windows build number: Microsoft Windows [Version 10.0.18362.657]
Windows Terminal version (if applicable): Version: 0.9.433.0

Steps to reproduce

For split-pane:
Run wt split-pane

For new-tab:
Run wt new-tab

Expected behavior

For split-pane:
Split the pane of the current window.

For new-tab:
Open a new tab in the current window.

Actual behavior

For split-pane:
Open a new window an split the pane in this window into two.

For new-tab:
Open a new window with a new tab in it.

Context

While this behavior is mentioned in the docs

Opens a new tab with the given customizations. On its first invocation, also opens a new window. Subsequent new-tab commands will all open new tabs in the same window.

It doesn't feel right to me. If those commands would not open a new window, we'll be able to get the same experience through command composition. (Open a new window and then split this one into two)

Now the behavior of programmatically splitting a pane or opening a tab in the current window (which feels like the broad use-case) is something that with the current implementation is not possible to do.

Originally created by @ranyitz on GitHub (Mar 3, 2020). # Environment ```none Windows build number: Microsoft Windows [Version 10.0.18362.657] Windows Terminal version (if applicable): Version: 0.9.433.0 ``` # Steps to reproduce For split-pane: Run `wt split-pane` For new-tab: Run `wt new-tab` # Expected behavior For split-pane: Split the pane of the current window. For new-tab: Open a new tab in the current window. # Actual behavior For split-pane: Open a new window an split the pane in this window into two. For new-tab: Open a new window with a new tab in it. # Context While this behavior is [mentioned in the docs](https://github.com/microsoft/terminal/blob/master/doc/user-docs/UsingCommandlineArguments.md#new-tab) > Opens a new tab with the given customizations. On its first invocation, also opens a new window. Subsequent new-tab commands will all open new tabs in the same window. It doesn't feel right to me. If those commands would not open a new window, we'll be able to get the same experience through command composition. (Open a new window and then split this one into two) Now the behavior of programmatically splitting a pane or opening a tab in the current window (which feels like the broad use-case) is something that with the current implementation is not possible to do.
claunia added the Resolution-Duplicate label 2026-01-31 00:45:36 +00:00
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 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#6719
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?