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

colorScheme in a profile does not apply the selected scheme #1926

New Issue
Open
opened 2026-01-30 22:42:06 +00:00 by claunia · 0 comments
claunia commented 2026-01-30 22:42:06 +00:00
Owner
Copy Link

Originally created by @antoineco on GitHub (Jun 22, 2019).

Environment

Windows build number: Version 10.0.18922.1000
Windows Terminal version (if applicable): 0.2.1715.0

Steps to reproduce

  1. Open profiles.json
  2. In the "cmd" profile, change the value of colorScheme from "Campbell" to "Solarized Dark" (ensure this scheme exists in the built-in schemes list)
  3. Close and reopen Terminal
  4. Open the "cmd" profile

Also reproducible with WSL profiles (e.g. "Ubuntu").

Expected behavior

According to doc/cascadia/SettingsSchema.md, colorScheme selects the color scheme to use for the profile, so I would expect to see Solarized colors in my terminal.

solarized dark

Actual behavior

cmd profile:
no-solarized

ubuntu profile (output of color-test.sh):
no-solarized_wsl

Originally created by @antoineco on GitHub (Jun 22, 2019). <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number: Version 10.0.18922.1000 Windows Terminal version (if applicable): 0.2.1715.0 ``` # Steps to reproduce 1. Open `profiles.json` 2. In the "cmd" profile, change the value of `colorScheme` from "Campbell" to "Solarized Dark" (ensure this scheme exists in the built-in `schemes` list) 3. Close and reopen Terminal 4. Open the "cmd" profile Also reproducible with WSL profiles (e.g. "Ubuntu"). <!-- A description of how to trigger this bug. --> # Expected behavior <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> According to [doc/cascadia/SettingsSchema.md](https://github.com/microsoft/terminal/blob/03e3d8a685b7c2b74e6e56e34199e823353defb1/doc/cascadia/SettingsSchema.md), `colorScheme` selects the color scheme to use for the profile, so I would expect to see Solarized colors in my terminal. ![solarized dark](https://raw.githubusercontent.com/mbadolato/iTerm2-Color-Schemes/master/screenshots/builtin_solarized_dark.png) # Actual behavior <!-- What's actually happening? --> cmd profile: ![no-solarized](https://user-images.githubusercontent.com/3299086/59968372-1c2e9480-9539-11e9-909d-c0024ca2dba2.png) ubuntu profile (output of [color-test.sh](https://github.com/fikovnik/bin-scripts/blob/master/color-test.sh)): ![no-solarized_wsl](https://user-images.githubusercontent.com/3299086/59968428-21d8aa00-953a-11e9-87a2-8e239dcdbcfb.png)
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 Needs-Attention 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#1926
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?