Bug Report: profile colorScheme not applied #4199

Open
opened 2026-01-30 23:40:50 +00:00 by claunia · 0 comments
Owner

Originally created by @Kizmar on GitHub (Oct 1, 2019).

Environment

Windows build number: 10.0.18362.0
Windows Terminal version (if applicable): 0.5.2681.0
Visual Studio Code version: 1.38.1

Steps to reproduce

  • Click on Settings from the menu (Ctrl+)
  • For me this opens in Visual Studio Code
  • Under existing profiles, add "colorScheme": "<any_color_scheme>"
  • Save json file

Expected behavior

  • Changes colors to the scheme selected upon save of the json file
  • Changing the fontFace & fontSize DOES change as expected (so it's somewhat working)

Actual behavior

  • Observe no change in the colors
  • Restarted app after change, still no change in colors

Other notes

I've reviewed these docs and it seems pretty straight forward. I didn't see an issue stating that colorSchemes aren't working yet, but maybe I missed something.

I tried changing the profiles to one of the default included themes, and tried to add my own theme. Neither seemed to have any effect on the app colors when saved. Below is a current copy of my profiles.json file.

// To view the default settings, hold "alt" while clicking on the "Settings" button.
// For documentation on these settings, see: https://aka.ms/terminal-documentation

{
	"$schema": "https://aka.ms/terminal-profiles-schema",

	"defaultProfile": "{61c54bbd-c2c6-5271-96e7-009a87ff44bf}",

	"profiles": [{
			// Make changes here to the powershell.exe profile
			"guid": "{61c54bbd-c2c6-5271-96e7-009a87ff44bf}",
			"name": "Windows PowerShell",
			"commandline": "powershell.exe",
			"hidden": false,
			"colorScheme": "Afterglow",
			"fontFace": "Fire Code",
			"fontSize": 9
		},
		{
			// Make changes here to the cmd.exe profile
			"guid": "{0caa0dad-35be-5f56-a8ff-afceeeaa6101}",
			"name": "cmd",
			"commandline": "cmd.exe",
			"hidden": false,
			"colorScheme": "Afterglow"
		},
		{
			"guid": "{b453ae62-4e3d-5e58-b989-0a998ec441b8}",
			"hidden": false,
			"name": "Azure Cloud Shell",
			"source": "Windows.Terminal.Azure",
			"colorScheme": "Afterglow"
		}
	],

	// Add custom color schemes to this array
	"schemes": [{
		"name": "Afterglow",
		"black": "#151515",
		"red": "#ac4142",
		"green": "#7e8e50",
		"yellow": "#e5b567",
		"blue": "#6c99bb",
		"purple": "#9f4e85",
		"cyan": "#7dd6cf",
		"white": "#d0d0d0",
		"brightBlack": "#505050",
		"brightRed": "#ac4142",
		"brightGreen": "#7e8e50",
		"brightYellow": "#e5b567",
		"brightBlue": "#6c99bb",
		"brightPurple": "#9f4e85",
		"brightCyan": "#7dd6cf",
		"brightWhite": "#f5f5f5",
		"background": "#212121",
		"foreground": "#d0d0d0"
	}],

	// Add any keybinding overrides to this array.
	// To unbind a default keybinding, set the command to "unbound"
	"keybindings": []
}
Originally created by @Kizmar on GitHub (Oct 1, 2019). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- 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. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number: 10.0.18362.0 Windows Terminal version (if applicable): 0.5.2681.0 Visual Studio Code version: 1.38.1 ``` # Steps to reproduce - Click on Settings from the menu (Ctrl+) - For me this opens in Visual Studio Code - Under existing profiles, add `"colorScheme": "<any_color_scheme>"` - Save json file # Expected behavior - Changes colors to the scheme selected upon save of the json file - Changing the `fontFace` & `fontSize` DOES change as expected (so it's somewhat working) # Actual behavior - Observe no change in the colors - Restarted app after change, still no change in colors ## Other notes I've reviewed [these docs](https://github.com/microsoft/terminal/blob/master/doc/user-docs/UsingJsonSettings.md) and it seems pretty straight forward. I didn't see an issue stating that `colorSchemes` aren't working yet, but maybe I missed something. I tried changing the profiles to one of the default included themes, and tried to add my own theme. Neither seemed to have any effect on the app colors when saved. Below is a current copy of my `profiles.json` file. ``` // To view the default settings, hold "alt" while clicking on the "Settings" button. // For documentation on these settings, see: https://aka.ms/terminal-documentation { "$schema": "https://aka.ms/terminal-profiles-schema", "defaultProfile": "{61c54bbd-c2c6-5271-96e7-009a87ff44bf}", "profiles": [{ // Make changes here to the powershell.exe profile "guid": "{61c54bbd-c2c6-5271-96e7-009a87ff44bf}", "name": "Windows PowerShell", "commandline": "powershell.exe", "hidden": false, "colorScheme": "Afterglow", "fontFace": "Fire Code", "fontSize": 9 }, { // Make changes here to the cmd.exe profile "guid": "{0caa0dad-35be-5f56-a8ff-afceeeaa6101}", "name": "cmd", "commandline": "cmd.exe", "hidden": false, "colorScheme": "Afterglow" }, { "guid": "{b453ae62-4e3d-5e58-b989-0a998ec441b8}", "hidden": false, "name": "Azure Cloud Shell", "source": "Windows.Terminal.Azure", "colorScheme": "Afterglow" } ], // Add custom color schemes to this array "schemes": [{ "name": "Afterglow", "black": "#151515", "red": "#ac4142", "green": "#7e8e50", "yellow": "#e5b567", "blue": "#6c99bb", "purple": "#9f4e85", "cyan": "#7dd6cf", "white": "#d0d0d0", "brightBlack": "#505050", "brightRed": "#ac4142", "brightGreen": "#7e8e50", "brightYellow": "#e5b567", "brightBlue": "#6c99bb", "brightPurple": "#9f4e85", "brightCyan": "#7dd6cf", "brightWhite": "#f5f5f5", "background": "#212121", "foreground": "#d0d0d0" }], // Add any keybinding overrides to this array. // To unbind a default keybinding, set the command to "unbound" "keybindings": [] } ```
claunia added the Resolution-Duplicate label 2026-01-30 23:40:50 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#4199