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

Misspelled "PowerShell" in defaults.json and settings.json files #7737

New Issue
Closed
opened 2026-01-31 01:11:33 +00:00 by claunia · 3 comments
claunia commented 2026-01-31 01:11:33 +00:00
Owner
Copy Link

Originally created by @alexandair on GitHub (Apr 27, 2020).

Could PowerShell be properly capitalized in the defaults.json and settings.json file by GA release?

"Campbell Powershell" should be "Campbell PowerShell"

"Windows.Terminal.PowershellCore" should be "Windows.Terminal.PowerShellCore"

Actually, "Core" is now gone. In 0.11 Terminal team even removed 7 and is using just "PowerShell", so source should be "Windows.Terminal.PowerShell".

Environment

Windows build number: 
Platform ServicePack Version      VersionString
-------- ----------- -------      -------------
 Win32NT             10.0.18363.0 Microsoft Windows NT 10.0.18363.0

Windows Terminal version:
Version: 0.11.1121.0

Steps to reproduce

Open auto-generated defaults.json and settings.json files.

Expected behavior

"name": "Campbell PowerShell"
"source": "Windows.Terminal.PowerShell"

Actual behavior

"name": "Campbell Powershell"
"source": "Windows.Terminal.PowershellCore"

Originally created by @alexandair on GitHub (Apr 27, 2020). Could PowerShell be properly capitalized in the defaults.json and settings.json file by GA release? "Campbell Powershell" should be "Campbell PowerShell" "Windows.Terminal.PowershellCore" should be "Windows.Terminal.PowerShellCore" Actually, "Core" is now gone. In 0.11 Terminal team even removed 7 and is using just "PowerShell", so source should be "Windows.Terminal.PowerShell". <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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: Platform ServicePack Version VersionString -------- ----------- ------- ------------- Win32NT 10.0.18363.0 Microsoft Windows NT 10.0.18363.0 Windows Terminal version: Version: 0.11.1121.0 ``` # Steps to reproduce <!-- A description of how to trigger this bug. --> Open auto-generated defaults.json and settings.json files. # Expected behavior <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> "name": "Campbell PowerShell" "source": "Windows.Terminal.PowerShell" # Actual behavior <!-- What's actually happening? --> "name": "Campbell Powershell" "source": "Windows.Terminal.PowershellCore"
claunia added the Needs-Tag-FixResolution-Won't-Fix labels 2026-01-31 01:11:33 +00:00
claunia commented 2026-01-31 01:11:34 +00:00
Author
Owner
Copy Link

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

Thanks for the report! Unfortunately, the source value is a contract between the user settings and Terminal, and it was created back when Core was part of powershell's name. It's not negotiable now that we've shipped it.

As for the color scheme name, I reckon we could fix it -- that color scheme is also deprecated, and only intended to be used by the inbuilt Windows PowerShell profile.

I don't disagree that these are wrong, but I'm going to mark this one as Won't fix. It's not worth the compatibility issue we'll probably cause with our future selves 😦

@DHowett-MSFT commented on GitHub (Apr 29, 2020): Thanks for the report! Unfortunately, the `source` value is a contract between the user settings and Terminal, and it was created back when Core was part of powershell's name. It's not negotiable now that we've shipped it. As for the color scheme name, I reckon we could fix it -- that color scheme is also deprecated, and only intended to be used by the inbuilt Windows PowerShell profile. I don't disagree that these are _wrong_, but I'm going to mark this one as Won't fix. It's not worth the compatibility issue we'll probably cause with our future selves 😦
claunia commented 2026-01-31 01:11:34 +00:00
Author
Owner
Copy Link

@alexandair commented on GitHub (Apr 29, 2020):

Windows Terminal is not shipped. It's still in preview. You broke my profiles.json in 0.11, and you haven't heard me complaining about that. Because it's a preview release. And I expect breaking changes. Not fixing wrong capitalization bugs before GA is just sloppy. Sorry.

@alexandair commented on GitHub (Apr 29, 2020): Windows Terminal is not shipped. It's still in preview. You broke my profiles.json in 0.11, and you haven't heard me complaining about that. Because it's a preview release. And I expect breaking changes. Not fixing wrong capitalization bugs before GA is just sloppy. Sorry.
claunia commented 2026-01-31 01:11:35 +00:00
Author
Owner
Copy Link

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

If it were just you and just your opinion, I’d be sold on it, you know? But the number of duplicates on #5458 and the sheer volume of dissatisfaction even though we’re in preview has made us more than a little shy about making further breaking changes.. especially mere weeks before we do final signoffs. I’m happy to fix the scheme name, but the generator may just have to stay. Sorry.

@DHowett-MSFT commented on GitHub (Apr 29, 2020): If it were just you and just your opinion, I’d be sold on it, you know? But the number of duplicates on #5458 and the sheer volume of dissatisfaction _even though we’re in preview_ has made us more than a little shy about making further breaking changes.. especially mere weeks before we do final signoffs. I’m happy to fix the scheme name, but the generator may just have to stay. Sorry.
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 Needs-Tag-Fix Resolution-Won't-Fix
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#7737
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?