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

wt -w 0 sp -s 0.4 pwsh opens a new tab and THEN splits it #23176

New Issue
Closed
opened 2026-01-31 08:34:27 +00:00 by claunia · 4 comments
claunia commented 2026-01-31 08:34:27 +00:00
Owner
Copy Link

Originally created by @daxian-dbw on GitHub (Apr 18, 2025).

Originally assigned to: @lhecker on GitHub.

Windows Terminal version

1.23.10732.0

Windows build number

10.0.26100.0

Other Software

No response

Steps to reproduce

When both WT stable and WT preview are both installed, running wt -w 0 sp -s 0.4 pwsh in WT preview will start a WT stable window (or use an existing WT stable window) and split the tab in it.

Even when using the WT preview specific wt.exe, it still doesn't work properly -- it starts a new tab in the current WT preview window and split that tab, while the expectation is that it will split the current tab.

& 'C:\Users\<user-name>\AppData\Local\Microsoft\WindowsApps\Microsoft.WindowsTerminalPreview_8wekyb3d8bbwe\wt.exe' -w 0 sp -s 0.4 pwsh

The command wt -w 0 sp -s 0.4 pwsh works as expected when running in WT stable.
For reference, this behavior was reported in https://github.com/PowerShell/AIShell/issues/363

Expected Behavior

Running wt -w 0 sp -s 0.4 pwsh should split the current tab in the current WT window, regardless of in WT stable or WT preview.

Originally created by @daxian-dbw on GitHub (Apr 18, 2025). Originally assigned to: @lhecker on GitHub. ### Windows Terminal version 1.23.10732.0 ### Windows build number 10.0.26100.0 ### Other Software _No response_ ### Steps to reproduce When both WT stable and WT preview are both installed, running `wt -w 0 sp -s 0.4 pwsh` in WT preview will start a WT stable window (or use an existing WT stable window) and split the tab in it. Even when using the WT preview specific `wt.exe`, it still doesn't work properly -- it starts a new tab in the current WT preview window and split that tab, while the expectation is that it will split the current tab. > `& 'C:\Users\<user-name>\AppData\Local\Microsoft\WindowsApps\Microsoft.WindowsTerminalPreview_8wekyb3d8bbwe\wt.exe' -w 0 sp -s 0.4 pwsh` The command `wt -w 0 sp -s 0.4 pwsh` works as expected when running in WT stable. For reference, this behavior was reported in https://github.com/PowerShell/AIShell/issues/363 ### Expected Behavior Running `wt -w 0 sp -s 0.4 pwsh` should split the current tab in the current WT window, regardless of in WT stable or WT preview.
claunia commented 2026-01-31 08:34:29 +00:00
Author
Owner
Copy Link

@daxian-dbw commented on GitHub (Apr 18, 2025):

This could be related to https://github.com/microsoft/terminal/issues/18459

@daxian-dbw commented on GitHub (Apr 18, 2025): This could be related to https://github.com/microsoft/terminal/issues/18459
claunia commented 2026-01-31 08:34:29 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Apr 23, 2025):

When both WT stable and WT preview are both installed, running wt -w 0 sp -s 0.4 pwsh in WT preview will start a WT stable window (or use an existing WT stable window) and split the tab in it.

This is expected when the setting in "Manage App Execution Aliases" gives precedence to Terminal Stable

Even when using the WT preview specific wt.exe, it still doesn't work properly -- it starts a new tab in the current WT preview window and split that tab, while the expectation is that it will split the current tab.

This is a bug. I can reproduce it on Canary as well. Thanks!

@DHowett commented on GitHub (Apr 23, 2025): > When both WT stable and WT preview are both installed, running wt -w 0 sp -s 0.4 pwsh in WT preview will start a WT stable window (or use an existing WT stable window) and split the tab in it. This is expected when the setting in "Manage App Execution Aliases" gives precedence to Terminal Stable > Even when using the WT preview specific wt.exe, it still doesn't work properly -- it starts a new tab in the current WT preview window and split that tab, while the expectation is that it will split the current tab. This is a bug. I can reproduce it on Canary as well. Thanks!
claunia commented 2026-01-31 08:34:29 +00:00
Author
Owner
Copy Link

@daxian-dbw commented on GitHub (Apr 23, 2025):

This is expected when the setting in "Manage App Execution Aliases" gives precedence to Terminal Stable

@DHowett My settings for "Terminal" and "Terminal Preview" are shown below. Does it give precedence to Terminal Stable or Terminal Preview?

Image

@daxian-dbw commented on GitHub (Apr 23, 2025): > This is expected when the setting in "Manage App Execution Aliases" gives precedence to Terminal Stable @DHowett My settings for "Terminal" and "Terminal Preview" are shown below. Does it give precedence to Terminal Stable or Terminal Preview? ![Image](https://github.com/user-attachments/assets/7d6db4dc-30f1-486e-86e4-1c51c31ae6d9)
claunia commented 2026-01-31 08:34:30 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Sep 3, 2025):

Bumping this one up from p3 to p2 since we're getting more hits

@DHowett commented on GitHub (Sep 3, 2025): Bumping this one up from p3 to p2 since we're getting more hits
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-Commandline Area-Windowing Issue-Bug Needs-Tag-Fix Priority-2 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#23176
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?