[ui] Inconsistent "cmd" in new tab context menu #6296

Closed
opened 2026-01-31 00:35:04 +00:00 by claunia · 17 comments
Owner

Originally created by @vadimkantorov on GitHub (Feb 5, 2020).

Originally assigned to: @cinnamon-msft on GitHub.

I just installed the most recent update from Releases.

Note the available shell names: "Windows PowerShell", "cmd", "Ubuntu-18.04", "Azure Cloud Shell" and how "cmd" is the only one not capitalized and not a proper word. Shouldn't it be "Command Prompt" or "Command Prompt (cmd)"? It is a well-known everywhere-existing shell. It would be nice if it is named consistently.

image

Originally created by @vadimkantorov on GitHub (Feb 5, 2020). Originally assigned to: @cinnamon-msft on GitHub. I just installed the most recent update from Releases. Note the available shell names: "Windows PowerShell", "cmd", "Ubuntu-18.04", "Azure Cloud Shell" and how "cmd" is the only one not capitalized and not a proper word. Shouldn't it be "Command Prompt" or "Command Prompt (cmd)"? It is a well-known everywhere-existing shell. It would be nice if it is named consistently. ![image](https://user-images.githubusercontent.com/1041752/73861695-acf28000-483d-11ea-9e49-6e3ebae6fc30.png)
Author
Owner

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

Yeah, we should probably call it Command Prompt.

@DHowett-MSFT commented on GitHub (Feb 5, 2020): Yeah, we should probably call it Command Prompt.
Author
Owner

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

Thanks!

@DHowett-MSFT commented on GitHub (Feb 5, 2020): Thanks!
Author
Owner

@vadimkantorov commented on GitHub (Feb 5, 2020):

Also, please note that if one searches for Ubuntu app in Cortana, it is called "Ubuntu 18.04 LTS" without any dash:
image

Consistency would also be great in this respect too!

@vadimkantorov commented on GitHub (Feb 5, 2020): Also, please note that if one searches for Ubuntu app in Cortana, it is called "Ubuntu 18.04 LTS" without any dash: ![image](https://user-images.githubusercontent.com/1041752/73869196-2bedb580-484a-11ea-9443-9f211515494b.png) Consistency would also be great in this respect too!
Author
Owner

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

We explicitly ask the WSL distribution for its name. This is an upstream issue on Canonical.

@DHowett-MSFT commented on GitHub (Feb 5, 2020): We explicitly ask the WSL distribution for its name. This is an upstream issue on Canonical.
Author
Owner

@vadimkantorov commented on GitHub (Feb 5, 2020):

Well, this difference in style is confusing (all other names use spaces for word separation). If the team considers this is okay - so be it. I just wanted to have it in issues in case other users want to search for this.

@vadimkantorov commented on GitHub (Feb 5, 2020): Well, this difference in style is confusing (all other names use spaces for word separation). If the team considers this is okay - so be it. I just wanted to have it in issues in case other users want to search for this.
Author
Owner

@vadimkantorov commented on GitHub (Feb 5, 2020):

Also the minor margin between the context menu and the "v" button is not very common on Windows. And also when clicking on "v", both "v" and "+" get focus - strange.

image

@vadimkantorov commented on GitHub (Feb 5, 2020): Also the minor margin between the context menu and the "v" button is not very common on Windows. And also when clicking on "v", both "v" and "+" get focus - strange. ![image](https://user-images.githubusercontent.com/1041752/73870665-c51dcb80-484c-11ea-9f8d-32a152d3f3ef.png)
Author
Owner

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

Alright, let's not make this too big of a bucket issue for a bunch of UI complaints 😄
We're following the windows xaml SplitButton style here: all Xaml split buttons do this!

@DHowett-MSFT commented on GitHub (Feb 5, 2020): Alright, let's not make this too big of a bucket issue for a bunch of UI complaints :smile: We're following the windows xaml SplitButton style here: all Xaml split buttons do this!
Author
Owner

@vadimkantorov commented on GitHub (Feb 5, 2020):

We're following the windows xaml SplitButton style here: all Xaml split buttons do this!

Ok :)

@vadimkantorov commented on GitHub (Feb 5, 2020): > We're following the windows xaml SplitButton style here: all Xaml split buttons do this! Ok :)
Author
Owner

@vadimkantorov commented on GitHub (Feb 5, 2020):

Would you like me to file a separate issue about the space between buttons and context menu?

@vadimkantorov commented on GitHub (Feb 5, 2020): Would you like me to file a separate issue about the space between buttons and context menu?
Author
Owner

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

Looking at it more, the menu spacing also seems consistent with other Xaml apps:

image

image

@DHowett-MSFT commented on GitHub (Feb 5, 2020): Looking at it more, the menu spacing also seems consistent with other Xaml apps: ![image](https://user-images.githubusercontent.com/14316954/73871722-333da080-4803-11ea-8052-e4fdc9e1d5f3.png) ![image](https://user-images.githubusercontent.com/14316954/73871743-3b95db80-4803-11ea-8615-ccb26858e93b.png)
Author
Owner

@vadimkantorov commented on GitHub (Feb 5, 2020):

Hmm, ok then :)

@vadimkantorov commented on GitHub (Feb 5, 2020): Hmm, ok then :)
Author
Owner

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

1.x item: we may want to reopen the book on being able to use resource names as profile names; otherwise, we would have to figure out how to localize profile names (since Command Prompt is different in different languages, but cmd is not)

@DHowett-MSFT commented on GitHub (Feb 24, 2020): 1.x item: we may want to reopen the book on being able to use resource names as profile names; otherwise, we would have to figure out how to localize profile names (since `Command Prompt` is different in different languages, but `cmd` is _not_)
Author
Owner

@vadimkantorov commented on GitHub (Apr 8, 2020):

If one wanted to keep cmd in the name, you could have default name as "Command Prompt (cmd.exe)" and keep that suffix regardless of localization

@vadimkantorov commented on GitHub (Apr 8, 2020): If one wanted to keep `cmd` in the name, you could have default name as "Command Prompt (cmd.exe)" and keep that suffix regardless of localization
Author
Owner

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

Meh, I'm not particularly bothered by the loss of "cmd.exe"

@DHowett-MSFT commented on GitHub (Apr 8, 2020): Meh, I'm not particularly bothered by the loss of "cmd.exe"
Author
Owner

@vadimkantorov commented on GitHub (Apr 8, 2020):

If localization is on, the user is doomed in any case: "PowerShell", "Ubuntu-18.04", "Командная строка" :)

@vadimkantorov commented on GitHub (Apr 8, 2020): If localization is on, the user is doomed in any case: "PowerShell", "Ubuntu-18.04", "Командная строка" :)
Author
Owner

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

PowerShell, Windows, and Ubuntu are product names and aren't generally localized. Your argument was that command prompt usually is 😄 and on Windows it's not localized with "cmd.exe" at the end.

It is a well-known everywhere-existing shell. It would be nice if it is named consistently.

@DHowett-MSFT commented on GitHub (Apr 8, 2020): PowerShell, Windows, and Ubuntu are product names and aren't generally localized. Your argument was that _command prompt_ usually is :smile: and on Windows it's not localized with "cmd.exe" at the end. > It is a well-known everywhere-existing shell. It would be nice if it is named consistently.
Author
Owner

@vadimkantorov commented on GitHub (Apr 8, 2020):

Yes :)

@vadimkantorov commented on GitHub (Apr 8, 2020): Yes :)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#6296