Display a warning when someone passes an invalid profile name on the `wt` commandline

[thlac]

Environment

Windows build number: 10.0.19041.264
Windows Terminal version (if applicable): 1.0.1401.0

Profiles:
Windows Powershell
Command Prompt
PowerShell
PowerShell 7 Preview
Ubuntu
Azure Cloud Shell

Config: settings.txt

Steps to reproduce

1. wt -p Windows PowerShell
   Causes Windows Powershell to be loaded, but with Powershell (Core) as the profile
2. wt -p Command Prompt
   Following message is shown: [error 0x80070002 when launching `Prompt'] (Is using the Powershell (Core) profile but the tab name is empty)
3. wt -p ubuntu
   Launches Powershell (Core)

Expected behavior

Less confusing behaviour, from what I have observed it seems like, on my system at least, the Powershell (Core) profile is considered a default of sorts, so if it doesn't find a direct match it just opens that. It also seems that the second argument seems to be passed as an argument to the profile, not entirely sure if that's right way to describe it, as wt -p Windows Get-Date results in the same error as the Command Prompt example instead of executing Get-Date.

So I think ways of adressing that would be:

1. Commands should only accept the ones defined in the documentation, (e.g. new-tab, split-pane, focus-tab)
2. If a direct (case insensitive) profile match isn't found, is it possible to launch the default profile while displaying to the user that the selected profile wasn't found?
3. (imo) If a direct (case insensitive) profile match is found do launch that, instead of the default. (i.e. wt -p ubuntu is the same as wt -p Ubuntu)

Actual behavior

In steps to reproduce, above.

[zadjii-msft]

You need to use spaces to wrap the profile names as a single argument - so do wt -p "Windows Powershell" or wt -p "Command Prompt". For more details, refer to command-line arg documentation

[thlac]

Hi, I'm sorry if I didn't phrase the issue better, but none of the issues I mentioned are related to quotes itself, they are how I discovered the issues, but everything I wrote is still the case, whether quotes are used or not.

[zadjii-msft]

Ah okay, gotcha. Sorry, long day triaging.

If we can't find the profile provided, you're right, we default to whatever the default profile is for your settings. So that's why it seems like "powershell core" is the default value - it probably is.

RE:

• Commands should only accept the ones defined in the documentation, (e.g. new-tab, split-pane, focus-tab)

• If a direct (case insensitive) profile match isn't found, is it possible to launch the default profile while displaying to the user that the selected profile wasn't found?

• (imo) If a direct (case insensitive) profile match is found do launch that, instead of the default. (i.e. wt -p ubuntu is the same as wt -p Ubuntu)

1. I'm not sure I totally get what the problem is here - we definitely only accept the given subcommands. Everything that we don't recognize that's passed to new-tab or split-pane is treated as a commandline value to use instead of the commandline from the profile. When there's no subcommand provided, we default to new-tab.
2. This isn't a terrible idea.
3. I tried playing with case-insensitivity in Make profile names, scheme names case-insensitive #5690, though, I think we're probably going to stick with case sensitivity at this point.