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

Powershell colorscheme doesn't get updated by colortool. #190

New Issue
Closed
opened 2026-01-30 21:45:06 +00:00 by claunia · 2 comments
claunia commented 2026-01-30 21:45:06 +00:00
Owner
Copy Link

Originally created by @artifaktor on GitHub (Mar 12, 2018).

It looks like one can run two different kind of powershell, one with the normal way of launching it from the start, or from the win+x menu, and one with the right click open powershell here method. The normal ps colorscheme doesn't get update by the colortool while the cmd console, and the wsl console do get the new colorscheme. Here is a screenshot of this happening:
kepernyofelvetel 2

Originally created by @artifaktor on GitHub (Mar 12, 2018). It looks like one can run two different kind of powershell, one with the normal way of launching it from the start, or from the win+x menu, and one with the right click open powershell here method. The normal ps colorscheme doesn't get update by the colortool while the cmd console, and the wsl console do get the new colorscheme. Here is a screenshot of this happening: ![kepernyofelvetel 2](https://user-images.githubusercontent.com/8431047/37311340-2e286164-2647-11e8-883f-0c3608d521b5.png)
claunia added the Issue-Question label 2026-01-30 21:45:06 +00:00
claunia commented 2026-01-30 21:45:07 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Mar 12, 2018):

That's because these are different mechanisms by which you can launch powershell. One involves the Start Menu's Powershell shortcut, and the other uses the registry's values for powershell.exe. Colortool will only be able to set the values for the version that was launched, the other will remain unmodified.

See this blog post for details.

@zadjii-msft commented on GitHub (Mar 12, 2018): That's because these *are* different mechanisms by which you can launch powershell. One involves the Start Menu's Powershell shortcut, and the other uses the registry's values for powershell.exe. Colortool will only be able to set the values for the version that was launched, the other will remain unmodified. See [this blog post ](https://blogs.msdn.microsoft.com/commandline/2017/06/20/understanding-windows-console-host-settings/) for details.
claunia commented 2026-01-30 21:45:07 +00:00
Author
Owner
Copy Link

@artifaktor commented on GitHub (Mar 12, 2018):

I see, thank you for the link and the information about settings mechanism. I would never have guessed that this was the reason for the behaviour, because I did not modify the setting for that shortcut, I didn't think it would retain those settings. This was really helpfull.

@artifaktor commented on GitHub (Mar 12, 2018): I see, thank you for the link and the information about settings mechanism. I would never have guessed that this was the reason for the behaviour, because I did not modify the setting for that shortcut, I didn't think it would retain those settings. This was really helpfull.
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 Issue-Question
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#190
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?