-
Notifications
You must be signed in to change notification settings - Fork 9.2k
wt command-line cannot consistently parse more than one argument #4618
Copy link
Copy link
Closed
Labels
Area-Commandlinewt.exe's commandline argumentswt.exe's commandline argumentsIssue-BugIt either shouldn't be doing this or needs an investigation.It either shouldn't be doing this or needs an investigation.Needs-Tag-FixDoesn't match tag requirementsDoesn't match tag requirementsPriority-1A description (P1)A description (P1)Product-TerminalThe new Windows Terminal.The new Windows Terminal.Resolution-Fix-CommittedFix is checked in, but it might be 3-4 weeks until a release.Fix is checked in, but it might be 3-4 weeks until a release.
Milestone
Metadata
Metadata
Assignees
Labels
Area-Commandlinewt.exe's commandline argumentswt.exe's commandline argumentsIssue-BugIt either shouldn't be doing this or needs an investigation.It either shouldn't be doing this or needs an investigation.Needs-Tag-FixDoesn't match tag requirementsDoesn't match tag requirementsPriority-1A description (P1)A description (P1)Product-TerminalThe new Windows Terminal.The new Windows Terminal.Resolution-Fix-CommittedFix is checked in, but it might be 3-4 weeks until a release.Fix is checked in, but it might be 3-4 weeks until a release.
Bottom line: the more arguments I put on
wtthe less likely it is to work. This is currently unusable even for launching the app clean.Something like this, in a run dialog:
Seems to work less than one time in five on my computer. Most of the time I get two panes, not three, and occasionally only one.
Environment
Steps to reproduce
Run the command above from a run dialog a half dozen times
Expected behavior
The window should open the same way every time, with three panes, one for each of the shells I have in Windows...
Actual behavior
Sometimes just PowerShell Core, sometimes both PowerShells, rarely all three including cmd.