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.exe] Help windows are inconsistent #6477

New Issue
Closed
opened 2026-01-31 00:39:51 +00:00 by claunia · 7 comments
claunia commented 2026-01-31 00:39:51 +00:00
Owner
Copy Link

Originally created by @alexandair on GitHub (Feb 16, 2020).

Environment

Microsoft Windows [Version 10.0.18363.535]

Steps to reproduce

# at the moment, this is considered a wrong syntax, so a help window pops up
# and help messages are not the same
PS C:\> wt `; split-pane -h cmd.exe
PS C:\> wt `; split-pane -v cmd.exe

# calling help gives us the third kind of a help message
--help, -h, -?, and /?

Expected behavior

All help windows are the same.

Actual behavior

Help windows contain different help messages dependent of the way how help is triggered.

Originally created by @alexandair on GitHub (Feb 16, 2020). # Environment ```none Microsoft Windows [Version 10.0.18363.535] ``` # Steps to reproduce ``` # at the moment, this is considered a wrong syntax, so a help window pops up # and help messages are not the same PS C:\> wt `; split-pane -h cmd.exe PS C:\> wt `; split-pane -v cmd.exe # calling help gives us the third kind of a help message --help, -h, -?, and /? ``` # Expected behavior All help windows are the same. # Actual behavior Help windows contain different help messages dependent of the way how help is triggered.
claunia added the Resolution-DuplicateProduct-TerminalArea-Commandline labels 2026-01-31 00:39:51 +00:00
claunia commented 2026-01-31 00:39:52 +00:00
Author
Owner
Copy Link

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

For at least the first and second, you’re seeing “split pane with an unknown argument,” “split pane help” (-h is help, so it can’t be repurposed for -H), and the third is “wt global help”.

This seems consistent to me; any ideas how we can be better here?

@DHowett-MSFT commented on GitHub (Feb 16, 2020): For at least the first and second, you’re seeing “split pane with an unknown argument,” “split pane help” (`-h` is help, so it can’t be repurposed for `-H`), and the third is “wt global help”. This seems consistent to me; any ideas how we can be better here?
claunia commented 2026-01-31 00:39:52 +00:00
Author
Owner
Copy Link

@alexandair commented on GitHub (Feb 17, 2020):

wt ; split-pane -v cmd.exe
v

wt ; split-pane -h cmd.exe
h

The first command gives us an error, the second the help for split-pane sub-command, althought both dialog windows are a result of case-sensitivity issue with -H and -V.

Solution is quite simple. Remove -h as a shortcut for help command (--help, -?, and /? are more than enough).
Make horizontal and vertical arguments case-insensitive.

@alexandair commented on GitHub (Feb 17, 2020): `wt ; split-pane -v cmd.exe` <img width="241" alt="v" src="https://user-images.githubusercontent.com/3135708/74615987-782bd600-5125-11ea-8ec9-ab5413f86729.png"> `wt ; split-pane -h cmd.exe` <img width="302" alt="h" src="https://user-images.githubusercontent.com/3135708/74615988-78c46c80-5125-11ea-9770-ca111e5bd91e.png"> The first command gives us an error, the second the help for split-pane sub-command, althought both dialog windows are a result of case-sensitivity issue with -H and -V. Solution is quite simple. Remove -h as a shortcut for help command (--help, -?, and /? are more than enough). Make horizontal and vertical arguments case-insensitive.
claunia commented 2026-01-31 00:39:52 +00:00
Author
Owner
Copy Link

@WSLUser commented on GitHub (Feb 18, 2020):

Make horizontal and vertical arguments case-insensitive.

That would break compatibility with WSL so that can't happen. We should be able to use the wt commandline from any shell, including ones utilized in WSL (bash, fish, zsh, etc.)

@WSLUser commented on GitHub (Feb 18, 2020): > Make horizontal and vertical arguments case-insensitive. That would break compatibility with WSL so that can't happen. We should be able to use the wt commandline from any shell, including ones utilized in WSL (bash, fish, zsh, etc.)
claunia commented 2026-01-31 00:39:52 +00:00
Author
Owner
Copy Link

@alexandair commented on GitHub (Feb 18, 2020):

@WSLUser
What do you mean "that would break compatibility"? wt.exe is still not GA. It's 0.9. So, now is the right time to fix the problem in PowerShell shell. Pre-GA time is the time for a breaking change. In any supported shell.

@alexandair commented on GitHub (Feb 18, 2020): @WSLUser What do you mean "that would break compatibility"? wt.exe is still not GA. It's 0.9. So, now is the right time to fix the problem in PowerShell shell. Pre-GA time is the time for a breaking change. In any supported shell.
claunia commented 2026-01-31 00:39:52 +00:00
Author
Owner
Copy Link

@WSLUser commented on GitHub (Feb 18, 2020):

Yes there are a number of issues with the WT commmandline but certain fundamentals need to be kept in place. Perhaps we can simply add different aliases depending on the shell being supported. For PS (Windows installed) and cmd, we can get the traditional type of commandline and for everything else, continue the same syntax and simply fix the logic that appears that have a number of bugs with it.

@WSLUser commented on GitHub (Feb 18, 2020): Yes there are a number of issues with the WT commmandline but certain fundamentals need to be kept in place. Perhaps we can simply add different aliases depending on the shell being supported. For PS (Windows installed) and cmd, we can get the traditional type of commandline and for everything else, continue the same syntax and simply fix the logic that appears that have a number of bugs with it.
claunia commented 2026-01-31 00:39:52 +00:00
Author
Owner
Copy Link

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

I'm closing this one as by-design for now. We're tracking the case sensitivity in another issue, and requests for the help dialog to change go in the discussion thread #4601.

The dialogs are consistent if you consider that one is an error for an invalid param, one is subcommand --help and one is wt --help. We could likely improve them by showing subcommand --help when we present an error for an invalid param.

/dup #4601

@DHowett-MSFT commented on GitHub (Feb 21, 2020): I'm closing this one as by-design for now. We're tracking the case sensitivity in another issue, and requests for the help dialog to change go in the discussion thread #4601. The dialogs are consistent if you consider that one is an error for an invalid param, one is subcommand --help and one is wt --help. We could likely improve them by showing subcommand --help when we present an error for an invalid param. /dup #4601
claunia commented 2026-01-31 00:39:53 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Feb 21, 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 (Feb 21, 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.
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 Product-Terminal 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#6477
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?