wt -w 0 split-pane creates a new tab instead of splitting the current one #23565

Closed
opened 2026-01-31 08:46:02 +00:00 by claunia · 8 comments
Owner

Originally created by @benbrummer on GitHub (Aug 28, 2025).

Windows Terminal version

1.23.12371.0

Windows build number

10.0.26100.0

Other Software

No response

Steps to reproduce

wt -w 0 split-pane
wt -w 0 split-pane -H
# Afterwards somehow new tabs are created instead of splitting the current one
wt -w 0 split-pane

Expected Behavior

wt -w 0 split-pane and wt -w 0 split-pane -H should split the current window instead of creating a new splitted tab.

Actual Behavior

wt -w 0 split-tab always opens a new Tab, which is than splitted instead of splitting the current tab. Somehow this happened after switching one time to wt -w 0 split-tab -H. Afterwards always a new tab is created with and without -H

At first I was expecting that the upgrade from 1.22.12111.0 caused this issue. But on another Windows 11 PC with 1.23.12371.0 it was working fine until I used -H again

Originally created by @benbrummer on GitHub (Aug 28, 2025). ### Windows Terminal version 1.23.12371.0 ### Windows build number 10.0.26100.0 ### Other Software _No response_ ### Steps to reproduce ``` wt -w 0 split-pane wt -w 0 split-pane -H # Afterwards somehow new tabs are created instead of splitting the current one wt -w 0 split-pane ``` ### Expected Behavior `wt -w 0 split-pane` and `wt -w 0 split-pane -H` should split the current window instead of creating a new splitted tab. ### Actual Behavior `wt -w 0 split-tab` always opens a new Tab, which is than splitted instead of splitting the current tab. Somehow this happened after switching one time to `wt -w 0 split-tab -H`. Afterwards always a new tab is created with and without `-H` At first I was expecting that the upgrade from 1.22.12111.0 caused this issue. But on another Windows 11 PC with 1.23.12371.0 it was working fine until I used `-H` again
claunia added the Issue-BugResolution-Duplicate labels 2026-01-31 08:46:02 +00:00
Author
Owner

@benbrummer commented on GitHub (Aug 29, 2025):

Image Image
@benbrummer commented on GitHub (Aug 29, 2025): <img width="1092" height="506" alt="Image" src="https://github.com/user-attachments/assets/7be9e5f7-04ed-4c8f-be0b-7de098a378ca" /> <img width="1097" height="502" alt="Image" src="https://github.com/user-attachments/assets/7c95cd1f-ec2e-4bae-9490-1d2d78e33373" />
Author
Owner

@eddiezato commented on GitHub (Aug 30, 2025):

I remember a couple of versions ago I switched from preview to stable because of this. Now it's in stable. Man...

@eddiezato commented on GitHub (Aug 30, 2025): I remember a couple of versions ago I switched from preview to stable because of this. Now it's in stable. Man...
Author
Owner

@lhecker commented on GitHub (Sep 1, 2025):

@eddiezato I hope you aren't surprised that the preview version became stable over time. 😅 Did you report this? If so, I apologize that we missed it.

@lhecker commented on GitHub (Sep 1, 2025): @eddiezato I hope you aren't surprised that the preview version became stable over time. 😅 Did you report this? If so, I apologize that we missed it.
Author
Owner

@eddiezato commented on GitHub (Sep 1, 2025):

@lhecker it was reported a couple of times by other users. 🫠

@eddiezato commented on GitHub (Sep 1, 2025): @lhecker it was reported a couple of times by other users. 🫠
Author
Owner

@lhecker commented on GitHub (Sep 1, 2025):

Oh, so this issue is a duplicate? Do you remember where you saw those prior reports? I must be using the wrong search terms. 🥲

@lhecker commented on GitHub (Sep 1, 2025): Oh, so this issue is a duplicate? Do you remember where you saw those prior reports? I must be using the wrong search terms. 🥲
Author
Owner

@eddiezato commented on GitHub (Sep 1, 2025):

I think this #18815

@eddiezato commented on GitHub (Sep 1, 2025): I think this #18815
Author
Owner

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

Thanks @eddiezato for finding the duplicate. You're right.

/dup #18815

@DHowett commented on GitHub (Sep 3, 2025): Thanks @eddiezato for finding the duplicate. You're right. /dup #18815
Author
Owner

@microsoft-github-policy-service[bot] commented on GitHub (Sep 3, 2025):

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!

@microsoft-github-policy-service[bot] commented on GitHub (Sep 3, 2025): 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! <!-- Policy app identification https://img.shields.io/static/v1?label=PullRequestIssueManagement. -->
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#23565