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

Color schemes can get "stuck" when the Theme is Light #19814

New Issue
Open
opened 2026-01-31 06:54:21 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 06:54:21 +00:00
Owner
Copy Link

Originally created by @j4james on GitHub (May 4, 2023).

Windows Terminal version

Commit 97a617a909

Windows build number

10.0.19045.2728

Other Software

No response

Steps to reproduce

  1. In Windows Terminal open the Settings page.
  2. Set the Theme to Light.
  3. Go to any profile and change the color scheme to something obviously different from the default, e.g. One Half Light.
  4. Go to the default profile and also change that color scheme to One Half Light.
  5. Go back to the profile from step 3 and reset the color scheme to the inherited value.
  6. Go to the default profile and reset the color scheme there too.
  7. Save the settings.
  8. Go back to the profile from step 3 and view the appearance.

Expected Behavior

Everything should now have been reset to the default color scheme, i.e. Campbell.

Actual Behavior

The color scheme is listed as being Campbell, but what is displayed in the preview window is still One Half Light, and that's also what gets used if you try and start that profile.

image

Originally created by @j4james on GitHub (May 4, 2023). ### Windows Terminal version Commit 97a617a909f1dd3664daf3a1764c9a7e8996a1b8 ### Windows build number 10.0.19045.2728 ### Other Software _No response_ ### Steps to reproduce 1. In Windows Terminal open the _Settings_ page. 2. Set the _Theme_ to _Light_. 3. Go to any profile and change the color scheme to something obviously different from the default, e.g. _One Half Light_. 4. Go to the default profile and also change that color scheme to _One Half Light_. 5. Go back to the profile from step 3 and reset the color scheme to the inherited value. 6. Go to the default profile and reset the color scheme there too. 7. Save the settings. 8. Go back to the profile from step 3 and view the appearance. ### Expected Behavior Everything should now have been reset to the default color scheme, i.e. _Campbell_. ### Actual Behavior The color scheme is listed as being _Campbell_, but what is displayed in the preview window is still _One Half Light_, and that's also what gets used if you try and start that profile. ![image](https://user-images.githubusercontent.com/4181424/236286427-de654633-1b16-40c0-9484-4498c2b7cded.png)
claunia added the Issue-BugPriority-3Product-TerminalArea-SettingsUI labels 2026-01-31 06:54:21 +00:00
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-SettingsUI Issue-Bug Priority-3 Product-Terminal
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#19814
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?