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

Commandline: split-pane does not honor focus pane #10041

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

Originally created by @jevad on GitHub (Aug 6, 2020).

Environment

Windows build number: Version 1909 (OS Build 18363.592)
Windows Terminal version (if applicable):  7.0.0

Steps to reproduce

Run the following command:

wt `; split-pane -V `; split-pane -H `; focus-tab -t 0 `; split-pane -H

Screenshot of the command:

what_i_ran

Expected behavior

I expect a Windows Terminal split into four panes of equal size. Pane 0 should have been split down the middle, vertically. Then pane 1 should have been split down the middle horizontally. Then pane 0 should have been split down the middle horizontally.

Screenshot of what I expect:

what_i_expect

Actual behavior

What I actually get is a window with a half-size pane, a quarter size pane and two eighth size panes. The behavior seems to be that the final split-pane command is ignoring the fact that the focus has been reset to pane 0, so it splits pane 2 instead of pane 0.

Screen shot of what actually happened when I ran the command:

what_i_get

Originally created by @jevad on GitHub (Aug 6, 2020). # Environment ```none Windows build number: Version 1909 (OS Build 18363.592) Windows Terminal version (if applicable): 7.0.0 ``` # Steps to reproduce Run the following command: ``` wt `; split-pane -V `; split-pane -H `; focus-tab -t 0 `; split-pane -H ``` Screenshot of the command: ![what_i_ran](https://user-images.githubusercontent.com/1743373/89588005-625fb980-d808-11ea-93d7-f1eee0656883.png) # Expected behavior I expect a Windows Terminal split into four panes of equal size. Pane 0 should have been split down the middle, vertically. Then pane 1 should have been split down the middle horizontally. Then pane 0 should have been split down the middle horizontally. Screenshot of what I expect: ![what_i_expect](https://user-images.githubusercontent.com/1743373/89587814-faa96e80-d807-11ea-97ab-c3b9f39b0f09.png) # Actual behavior What I actually get is a window with a half-size pane, a quarter size pane and two eighth size panes. The behavior seems to be that the final `split-pane` command is ignoring the fact that the focus has been reset to pane 0, so it splits pane 2 instead of pane 0. Screen shot of what actually happened when I ran the command: ![what_i_get](https://user-images.githubusercontent.com/1743373/89588038-773c4d00-d808-11ea-8b31-3276ad00f11d.png)
claunia added the Resolution-Duplicate label 2026-01-31 02:11:05 +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#10041
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?