starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-03 21:25:34 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Revisit the Powershell Defaults #647

New Issue
Closed
opened 2026-01-30 21:57:55 +00:00 by claunia · 10 comments
claunia commented 2026-01-30 21:57:55 +00:00
Owner
Copy Link

Originally created by @rkeithhill on GitHub (May 6, 2019).

That blue background is a thing of the past RE PowerShell. When opening PowerShell Core or in the future PowerShell 7 (ie pwsh.exe), you should use the current default bg for these apps which is a dark background similar to cmd.exe and WSL IIRC.

It would be worth keeping that Blue background if you offered to launch Windows PowerShell 5.1 which will be needed for some back compat purposes.

Originally created by @rkeithhill on GitHub (May 6, 2019). That blue background is a thing of the past RE PowerShell. When opening PowerShell Core or in the future `PowerShell 7` (ie pwsh.exe), you should use the current default bg for these apps which is a dark background similar to cmd.exe and WSL IIRC. It would be worth keeping that Blue background if you offered to launch `Windows PowerShell 5.1` which will be needed for some back compat purposes.
claunia added the Resolution-Fix-CommittedArea-SettingsIssue-BugProduct-Terminal labels 2026-01-30 21:57:56 +00:00
claunia commented 2026-01-30 21:57:56 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (May 6, 2019):

Sorry, is this a request that we don’t do something? PSCore already doesn’t install a shortcut with a hardcoded blue background.

@DHowett-MSFT commented on GitHub (May 6, 2019): Sorry, is this a request that we don’t do something? PSCore already doesn’t install a shortcut with a hardcoded blue background.
claunia commented 2026-01-30 21:57:57 +00:00
Author
Owner
Copy Link

@rkeithhill commented on GitHub (May 6, 2019):

I noticed that when I used the drop down menu to start pwsh.exe, it started with a blue background. That is in the terminal settings (json) file.

@rkeithhill commented on GitHub (May 6, 2019): I noticed that when I used the drop down menu to start pwsh.exe, it started with a blue background. That is in the terminal settings (json) file.
claunia commented 2026-01-30 21:57:57 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (May 6, 2019):

I think the suggestion is to remove the "background": "#012456" property from the default powershell profile we generate.

If you wanted to change the color of pwsh, you could remove that element from the profiles.json file, and we'll use the default BG from the colorscheme instead.

@zadjii-msft commented on GitHub (May 6, 2019): I think the suggestion is to remove the `"background": "#012456"` property from the default powershell profile we generate. If you wanted to change the color of pwsh, you could remove that element from the `profiles.json` file, and we'll use the default BG from the colorscheme instead.
claunia commented 2026-01-30 21:57:57 +00:00
Author
Owner
Copy Link

@rkeithhill commented on GitHub (May 6, 2019):

Yup, did that. But I think "out of the box" it should use that color for PowerShell.exe but not pwsh.exe. At the very least, run it by Joey on the PowerShell team.

@rkeithhill commented on GitHub (May 6, 2019): Yup, did that. But I think "out of the box" it should use that color for PowerShell.exe but not pwsh.exe. At the very least, run it by Joey on the PowerShell team.
claunia commented 2026-01-30 21:57:58 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (May 6, 2019):

You know, we're already detecting powershell core vs powershell, so I don't think this is an impossible ask

@zadjii-msft commented on GitHub (May 6, 2019): You know, we're already detecting powershell core vs powershell, so I don't think this is an impossible ask
claunia commented 2026-01-30 21:57:58 +00:00
Author
Owner
Copy Link

@rkeithhill commented on GitHub (May 6, 2019):

Also, if I did a PR to add OneHalfDark/OneHalfLight color schemes would you take it? Out of curiousity, these were in colortool, why not in terminal by default?

@rkeithhill commented on GitHub (May 6, 2019): Also, if I did a PR to add OneHalfDark/OneHalfLight color schemes would you take it? Out of curiousity, these were in colortool, why not in terminal by default?
claunia commented 2026-01-30 21:57:58 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (May 6, 2019):

Sure!

Simple answer - I didn't even think about it. I kinda only added solarized as a proof-of-concept.

I dream of one day adding a flag to wt.exe to attempt to parse all your colortool schemes, and import them if they don't already exist in your profiles.json.

@zadjii-msft commented on GitHub (May 6, 2019): Sure! Simple answer - I didn't even think about it. I kinda only added solarized as a proof-of-concept. I dream of one day adding a flag to wt.exe to attempt to parse all your colortool schemes, and import them if they don't already exist in your profiles.json.
claunia commented 2026-01-30 21:57:58 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (May 14, 2019):

@joeyaiello for his opinion on this.

What background color should we have for powershell, and what font face? We're currently using "powershell blue" and Courier New, from the vintage inbox powershell settings. Is that still appropriate?

@zadjii-msft commented on GitHub (May 14, 2019): @joeyaiello for his opinion on this. What background color should we have for powershell, and what font face? We're currently using "powershell blue" and Courier New, from the vintage inbox powershell settings. Is that still appropriate?
claunia commented 2026-01-30 21:57:58 +00:00
Author
Owner
Copy Link

@rkeithhill commented on GitHub (May 15, 2019):

Eventually, for PowerShell 6/7 I'd like to see it default to the new, spiffy Cascadia Code font (assuming it looks as good in person as I've seen in the BUILD demos). :-)

@rkeithhill commented on GitHub (May 15, 2019): Eventually, for PowerShell 6/7 I'd like to see it default to the new, spiffy Cascadia Code font (assuming it looks as good in person as I've seen in the BUILD demos). :-)
claunia commented 2026-01-30 21:57:59 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (May 24, 2019):

Hey I'm pretty sure this was closed with #918

@zadjii-msft commented on GitHub (May 24, 2019): Hey I'm pretty sure this was closed with #918
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-Settings Issue-Bug Product-Terminal Resolution-Fix-Committed
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#647
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?