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

Theme only work in profile Deafults. #8758

New Issue
Closed
opened 2026-01-31 01:37:12 +00:00 by claunia · 9 comments
claunia commented 2026-01-31 01:37:12 +00:00
Owner
Copy Link

Originally created by @ghost on GitHub (Jun 2, 2020).

Hey, I have set my color scheme to a theme called Atom.
{ "name": "Atom", "black": "#000000", "red": "#fd5ff1", "green": "#87c38a", "yellow": "#ffd7b1", "blue": "#85befd", "purple": "#b9b6fc", "cyan": "#85befd", "white": "#e0e0e0", "brightBlack": "#000000", "brightRed": "#fd5ff1", "brightGreen": "#94fa36", "brightYellow": "#f5ffa8", "brightBlue": "#96cbfe", "brightPurple": "#b9b6fc", "brightCyan": "#85befd", "brightWhite": "#e0e0e0", "background": "#161719", "foreground": "#c72a2a"//"#c5c8c6" }
I Have verified it works, but only in the profile defaults. I can't set them in the profiles section per profile.

Originally created by @ghost on GitHub (Jun 2, 2020). Hey, I have set my color scheme to a theme called Atom. { "name": "Atom", "black": "#000000", "red": "#fd5ff1", "green": "#87c38a", "yellow": "#ffd7b1", "blue": "#85befd", "purple": "#b9b6fc", "cyan": "#85befd", "white": "#e0e0e0", "brightBlack": "#000000", "brightRed": "#fd5ff1", "brightGreen": "#94fa36", "brightYellow": "#f5ffa8", "brightBlue": "#96cbfe", "brightPurple": "#b9b6fc", "brightCyan": "#85befd", "brightWhite": "#e0e0e0", "background": "#161719", "foreground": "#c72a2a"//"#c5c8c6" } I Have verified it works, but only in the profile defaults. I can't set them in the profiles section per profile.
claunia commented 2026-01-31 01:37:15 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jun 3, 2020):

As requested in the other thread, can you share a gist of your full settings file? Thanks!

@DHowett commented on GitHub (Jun 3, 2020): As requested in the other thread, can you share a [gist](https://gist.github.com) of your full settings file? Thanks!
claunia commented 2026-01-31 01:37:15 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jun 5, 2020):

https://gist.github.com/IveGotRoot/2a978cb14c35428f12a0f554a5f29239

@ghost commented on GitHub (Jun 5, 2020): https://gist.github.com/IveGotRoot/2a978cb14c35428f12a0f554a5f29239
claunia commented 2026-01-31 01:37:15 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jun 5, 2020):

I mean, you have two profiles that explicitly set the colorScheme to Campbell. Are those the ones that aren't working?

@DHowett commented on GitHub (Jun 5, 2020): I mean, you have two profiles that _explicitly_ set the `colorScheme` to `Campbell`. Are those the ones that aren't working?
claunia commented 2026-01-31 01:37:15 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jun 6, 2020):

All of them aren't working

@ghost commented on GitHub (Jun 6, 2020): All of them aren't working
claunia commented 2026-01-31 01:37:15 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jun 7, 2020):

I have them set as an experiment, I was just trying to set the theme to atom. Both of them were replaced correctly for the atom theme. I could only get it if I set the theme in default.

@ghost commented on GitHub (Jun 7, 2020): I have them set as an experiment, I was just trying to set the theme to atom. Both of them were replaced correctly for the atom theme. I could only get it if I set the theme in default.
claunia commented 2026-01-31 01:37:16 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jun 9, 2020):

Ah okay, I see it. The first profile in your list of profiles is... odd. It's got a source, but no guid, so it's not actually being correlated to any profile. If you wanted to change the properties of the "Windows Powershell" profile, you'd want the following:

            {
                "guid" : "{61c54bbd-c2c6-5271-96e7-009a87ff44bf}",
                "name" : "Powershell",
                "acrylicOpacity" : 0.7,
                "fontFace" : "Cascadia Code PL",
                "colorScheme" : "Atom"
            },
@zadjii-msft commented on GitHub (Jun 9, 2020): Ah okay, I see it. The first profile in your list of profiles is... odd. It's got a `source`, but no `guid`, so it's not actually being correlated to _any_ profile. If you wanted to change the properties of the "Windows Powershell" profile, you'd want the following: ```json { "guid" : "{61c54bbd-c2c6-5271-96e7-009a87ff44bf}", "name" : "Powershell", "acrylicOpacity" : 0.7, "fontFace" : "Cascadia Code PL", "colorScheme" : "Atom" }, ```
claunia commented 2026-01-31 01:37:16 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jun 9, 2020):

Thanks, It had no guid by default. Is that intentional?

@ghost commented on GitHub (Jun 9, 2020): Thanks, It had no guid by default. Is that intentional?
claunia commented 2026-01-31 01:37:16 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jun 9, 2020):

Definitely not - the ones that have the "source" property are dynamically generated and need the GUID to help the dynamic generator figure out which profile it is.

The "Windows Powershell" profile isn't dynamically generated, since it's always available on every version of Windows. It's defined in defaults.json, and also requires a GUID so the terminal can know that you're trying to change it's settings.

@zadjii-msft commented on GitHub (Jun 9, 2020): Definitely not - the ones that have the `"source"` property are [_dynamically generated_](https://docs.microsoft.com/en-us/windows/terminal/dynamic-profiles) and need the GUID to help the dynamic generator figure out which profile it is. The "Windows Powershell" profile _isn't_ dynamically generated, since it's always available on every version of Windows. It's defined in [`defaults.json`](https://github.com/microsoft/terminal/blob/master/src/cascadia/TerminalApp/defaults.json), and also requires a GUID so the terminal can know that you're trying to change it's settings.
claunia commented 2026-01-31 01:37:17 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jun 13, 2020):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost commented on GitHub (Jun 13, 2020): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.
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-Question Needs-Author-Feedback Needs-Triage No-Recent-Activity Product-Terminal Resolution-Answered
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#8758
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?