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

Feature Request: Option for ColorTool to read color theme from registry like conhost #2019

New Issue
Open
opened 2026-01-30 22:44:38 +00:00 by claunia · 1 comment
claunia commented 2026-01-30 22:44:38 +00:00
Owner
Copy Link

Originally created by @jantari on GitHub (Jun 23, 2019).

Summary of the new feature/enhancement

The new Windows Terminal should have an option to set "HKCU\Console" as the source of its color theme instead of specifying the colors in the JSON.

If this were to be the default setting it would make transitioning easier as a users previously customized theme just carries over to WT. Even if it were not the default though, the option to do this would be nice to enable the user to easily theme both conhost and wt consistently from one place instead of having to maintain two configurations (registry for conhost, json for wt)

Proposed technical implementation details (optional)

"Source Registry settings" (or similar name) should be added as an option for the theme, if a settings GUI is planned then it would be sitting right along the other color schemes inside the theme-selection combobox. Alternatively, it could be a checkbox sitting above the Theme-selection combobox that disables the combobox when checked. Either way, choosing this option, wt would source its color configuration from the ColorTableXX and CursorColor keys in HKCU\Console

Originally created by @jantari on GitHub (Jun 23, 2019). # Summary of the new feature/enhancement The new Windows Terminal should have an option to set "HKCU\Console" as the source of its color theme instead of specifying the colors in the JSON. If this were to be the default setting it would make transitioning easier as a users previously customized theme just carries over to WT. Even if it were not the default though, the option to do this would be nice to enable the user to easily theme both conhost and wt consistently from one place instead of having to maintain two configurations (registry for conhost, json for wt) # Proposed technical implementation details (optional) "Source Registry settings" (or similar name) should be added as an option for the theme, if a settings GUI is planned then it would be sitting right along the other color schemes inside the theme-selection combobox. Alternatively, it could be a checkbox sitting above the Theme-selection combobox that disables the combobox when checked. Either way, choosing this option, wt would source its color configuration from the ColorTableXX and CursorColor keys in HKCU\Console
claunia added the Product-ColortoolIssue-FeatureHelp WantedArea-Settings labels 2026-01-30 22:44:38 +00:00
claunia commented 2026-01-30 22:44:39 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Jun 27, 2019):

This could be a good thing for ColorTool to support. A recent PR added the ability to export colors in WT format.

@DHowett-MSFT commented on GitHub (Jun 27, 2019): This could be a good thing for ColorTool to support. A recent PR added the ability to export colors in WT format.
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 Help Wanted Issue-Feature Product-Colortool
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#2019
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?