Split pane from command prompt yields inconsistent results #6237

Closed
opened 2026-01-31 00:33:07 +00:00 by claunia · 5 comments
Owner

Originally created by @tedhudek on GitHub (Jan 31, 2020).

Environment

Windows build number: 10.0.18363.0
Windows Terminal version: 0.9.271.0

Steps to reproduce

  1. Create desktop shortcut with wt.exe ; split-pane ; split-pane.
  2. Run shortcut, observe Terminal's pane layout, close Terminal. Repeat several times.
  3. For me this has resulted in all of the following at different times
    • 3 panes with half vertical left and two quarters on the right
    • 3 panes with two quarters on left, half vertical on right
    • 2 vertical panes
    • once I even got a single pane

Expected behavior

Expecting first bullet under step 3 above. Absent changes in screen dimension, command line invocation should produce same results each time.

Actual behavior

Getting variable results rather than consistent results. I do seem to get the expected one most often, but not 100% of the time.

Originally created by @tedhudek on GitHub (Jan 31, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number: 10.0.18363.0 Windows Terminal version: 0.9.271.0 ``` # Steps to reproduce 1. Create desktop shortcut with `wt.exe ; split-pane ; split-pane`. 2. Run shortcut, observe Terminal's pane layout, close Terminal. Repeat several times. 3. For me this has resulted in all of the following at different times * 3 panes with half vertical left and two quarters on the right * 3 panes with two quarters on left, half vertical on right * 2 vertical panes * once I even got a single pane # Expected behavior Expecting first bullet under step 3 above. Absent changes in screen dimension, command line invocation should produce same results each time. # Actual behavior Getting variable results rather than consistent results. I do seem to get the expected one most often, but not 100% of the time.
Author
Owner

@DHowett-MSFT commented on GitHub (Feb 10, 2020):

This one fortunately has a quick workaround: specify -V or -H explicitly. 😄 Thanks for the report.

@DHowett-MSFT commented on GitHub (Feb 10, 2020): This one fortunately has a quick workaround: specify `-V` or `-H` explicitly. :smile: Thanks for the report.
Author
Owner

@FRANK3NST31N commented on GitHub (Feb 16, 2020):

I have observed inconsistent results as well while specifying the -V or -H

OS Name: Microsoft Windows 10 Pro
OS Version: 10.0.18363 N/A Build 18363
wt Version: 0.9.433.0

I followed the same procedure but used a script.

I created : test-terminal-split.CMD

File : test-terminal-split.CMD
Contents :

wt ; split-pane -V ; split-pane -H

then i execute this script several times.

run 1 : two panes
run 2 : three panes OK
run 3 : two panes
run 4 : two panes
run 5 : three panes OK

@FRANK3NST31N commented on GitHub (Feb 16, 2020): I have observed inconsistent results as well while specifying the -V or -H OS Name: Microsoft Windows 10 Pro OS Version: 10.0.18363 N/A Build 18363 wt Version: 0.9.433.0 I followed the same procedure but used a script. I created : test-terminal-split.CMD File : test-terminal-split.CMD Contents : wt ; split-pane -V ; split-pane -H then i execute this script several times. run 1 : two panes run 2 : three panes OK run 3 : two panes run 4 : two panes run 5 : three panes OK
Author
Owner

@DHowett-MSFT commented on GitHub (Apr 3, 2020):

I think this was fixed with #5090, for 0.11 (and soon, internal selfhost)

@DHowett-MSFT commented on GitHub (Apr 3, 2020): I think this was fixed with #5090, for 0.11 (and soon, internal selfhost)
Author
Owner

@DHowett-MSFT commented on GitHub (Apr 3, 2020):

/dup #4618 (sorry to dupe you to a higher number, but that's the one closed by the PR 😄)

@DHowett-MSFT commented on GitHub (Apr 3, 2020): /dup #4618 (sorry to dupe you to a higher number, but that's the one closed by the PR :smile:)
Author
Owner

@ghost commented on GitHub (Apr 3, 2020):

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!

@ghost commented on GitHub (Apr 3, 2020): 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!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#6237