starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-09-25 00:15:10 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

colorScheme does not work #11637

New Issue
Closed
opened 2026-01-31 02:53:14 +00:00 by claunia · 7 comments
claunia commented 2026-01-31 02:53:14 +00:00
Owner
Copy Link

Originally created by @agarwalvaibhav0211 on GitHub (Nov 30, 2020).

Environment

Windows build number: Microsoft Windows [Version 10.0.19042.630]
Windows Terminal version (if applicable):1.3.2651.0

Any other software?

Steps to reproduce

I have my settings.json file as follows:

// This file was initially generated by Windows Terminal 1.3.2651.0
// It should still be usable in newer versions, but newer versions might have additional
// settings, help text, or changes that you will not see unless you clear this file
// and let us generate a new one for you.

// 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": "{2c4de342-38b7-51cf-b940-2309a097f518}",

    // You can add more global application settings here.
    // To learn more about global settings, visit https://aka.ms/terminal-global-settings

    // If enabled, selections are automatically copied to your clipboard.
    "copyOnSelect": false,

    // If enabled, formatted data is also copied to your clipboard
    "copyFormatting": false,

    // A profile specifies a command to execute paired with information about how it should look and feel.
    // Each one of them will appear in the 'New Tab' dropdown,
    //   and can be invoked from the commandline with `wt.exe -p xxx`
    // To learn more about profiles, visit https://aka.ms/terminal-profile-settings
    "profiles":
    {
        "defaults":
        {
            // Put settings here that you want to apply to all profiles.
			"suppressApplicationTitle": true,
			"fontSize": 14,
			"startingDirectory": ".",
			"useAcrylic": true,
			"acrylicOpacity": 0.5,
			"backgroundImage": "C:\\Users\\Vaibhav\\Pictures\\Terminal\\2.jpg",
			"backgroundImageOpacity": 0.4,
			"colorScheme": "Campbell",
        },
        "list":
        [
            {
                // Make changes here to the powershell.exe profile.
                "guid": "{61c54bbd-c2c6-5271-96e7-009a87ff44bf}",
                "name": "Windows PowerShell",
                "commandline": "powershell.exe",
                "hidden": false
            },
            {
                // Make changes here to the cmd.exe profile.
                "guid": "{0caa0dad-35be-5f56-a8ff-afceeeaa6101}",
                "name": "Command Prompt",
                "commandline": "cmd.exe",
                "hidden": false
            },
            {
                "guid": "{2c4de342-38b7-51cf-b940-2309a097f518}",
                "hidden": false,
                "name": "Ubuntu",
                "source": "Windows.Terminal.Wsl"
            },
            {
                "guid": "{b453ae62-4e3d-5e58-b989-0a998ec441b8}",
                "hidden": false,
                "name": "Azure Cloud Shell",
                "source": "Windows.Terminal.Azure"
            }
        ]
    },

    // Add custom color schemes to this array.
    // To learn more about color schemes, visit https://aka.ms/terminal-color-schemes
    "schemes": [
		{
			"name" : "Campbell",

			"cursorColor": "#FFFFFF",
			"selectionBackground": "#FFFFFF",

			"background" : "#0C0C0C",
			"foreground" : "#CCCCCC",

			"black" : "#0C0C0C",
			"blue" : "#0037DA",
			"cyan" : "#3A96DD",
			"green" : "#13A10E",
			"purple" : "#881798",
			"red" : "#C50F1F",
			"white" : "#fc1100",
			"yellow" : "#C19C00",
			"brightBlack" : "#767676",
			"brightBlue" : "#3B78FF",
			"brightCyan" : "#61D6D6",
			"brightGreen" : "#16C60C",
			"brightPurple" : "#B4009E",
			"brightRed" : "#E74856",
			"brightWhite" : "#F2F2F2",
			"brightYellow" : "#F9F1A5"
		}
	],

    // Add custom actions and keybindings to this array.
    // To unbind a key combination from your defaults.json, set the command to "unbound".
    // To learn more about actions and keybindings, visit https://aka.ms/terminal-keybindings
    "actions":
    [
        // Copy and paste are bound to Ctrl+Shift+C and Ctrl+Shift+V in your defaults.json.
        // These two lines additionally bind them to Ctrl+C and Ctrl+V.
        // To learn more about selection, visit https://aka.ms/terminal-selection
        { "command": {"action": "copy", "singleLine": false }, "keys": "ctrl+c" },
        { "command": "paste", "keys": "ctrl+v" },

        // Press Ctrl+Shift+F to open the search box
        { "command": "find", "keys": "ctrl+shift+f" },

        // Press Alt+Shift+D to open a new pane.
        // - "split": "auto" makes this pane open in the direction that provides the most surface area.
        // - "splitMode": "duplicate" makes the new pane use the focused pane's profile.
        // To learn more about panes, visit https://aka.ms/terminal-panes
        { "command": { "action": "splitPane", "split": "auto", "splitMode": "duplicate" }, "keys": "alt+shift+d" }
    ]
}

Expected behavior

I expect the text color to change in the terminal.

Actual behavior

All Text is displayed as white.
Screenshot 2020-11-30 225304

I have already tried #2883 and all issues referenced on #3012

Originally created by @agarwalvaibhav0211 on GitHub (Nov 30, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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: Microsoft Windows [Version 10.0.19042.630] Windows Terminal version (if applicable):1.3.2651.0 Any other software? ``` # Steps to reproduce I have my settings.json file as follows: ``` // This file was initially generated by Windows Terminal 1.3.2651.0 // It should still be usable in newer versions, but newer versions might have additional // settings, help text, or changes that you will not see unless you clear this file // and let us generate a new one for you. // 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": "{2c4de342-38b7-51cf-b940-2309a097f518}", // You can add more global application settings here. // To learn more about global settings, visit https://aka.ms/terminal-global-settings // If enabled, selections are automatically copied to your clipboard. "copyOnSelect": false, // If enabled, formatted data is also copied to your clipboard "copyFormatting": false, // A profile specifies a command to execute paired with information about how it should look and feel. // Each one of them will appear in the 'New Tab' dropdown, // and can be invoked from the commandline with `wt.exe -p xxx` // To learn more about profiles, visit https://aka.ms/terminal-profile-settings "profiles": { "defaults": { // Put settings here that you want to apply to all profiles. "suppressApplicationTitle": true, "fontSize": 14, "startingDirectory": ".", "useAcrylic": true, "acrylicOpacity": 0.5, "backgroundImage": "C:\\Users\\Vaibhav\\Pictures\\Terminal\\2.jpg", "backgroundImageOpacity": 0.4, "colorScheme": "Campbell", }, "list": [ { // Make changes here to the powershell.exe profile. "guid": "{61c54bbd-c2c6-5271-96e7-009a87ff44bf}", "name": "Windows PowerShell", "commandline": "powershell.exe", "hidden": false }, { // Make changes here to the cmd.exe profile. "guid": "{0caa0dad-35be-5f56-a8ff-afceeeaa6101}", "name": "Command Prompt", "commandline": "cmd.exe", "hidden": false }, { "guid": "{2c4de342-38b7-51cf-b940-2309a097f518}", "hidden": false, "name": "Ubuntu", "source": "Windows.Terminal.Wsl" }, { "guid": "{b453ae62-4e3d-5e58-b989-0a998ec441b8}", "hidden": false, "name": "Azure Cloud Shell", "source": "Windows.Terminal.Azure" } ] }, // Add custom color schemes to this array. // To learn more about color schemes, visit https://aka.ms/terminal-color-schemes "schemes": [ { "name" : "Campbell", "cursorColor": "#FFFFFF", "selectionBackground": "#FFFFFF", "background" : "#0C0C0C", "foreground" : "#CCCCCC", "black" : "#0C0C0C", "blue" : "#0037DA", "cyan" : "#3A96DD", "green" : "#13A10E", "purple" : "#881798", "red" : "#C50F1F", "white" : "#fc1100", "yellow" : "#C19C00", "brightBlack" : "#767676", "brightBlue" : "#3B78FF", "brightCyan" : "#61D6D6", "brightGreen" : "#16C60C", "brightPurple" : "#B4009E", "brightRed" : "#E74856", "brightWhite" : "#F2F2F2", "brightYellow" : "#F9F1A5" } ], // Add custom actions and keybindings to this array. // To unbind a key combination from your defaults.json, set the command to "unbound". // To learn more about actions and keybindings, visit https://aka.ms/terminal-keybindings "actions": [ // Copy and paste are bound to Ctrl+Shift+C and Ctrl+Shift+V in your defaults.json. // These two lines additionally bind them to Ctrl+C and Ctrl+V. // To learn more about selection, visit https://aka.ms/terminal-selection { "command": {"action": "copy", "singleLine": false }, "keys": "ctrl+c" }, { "command": "paste", "keys": "ctrl+v" }, // Press Ctrl+Shift+F to open the search box { "command": "find", "keys": "ctrl+shift+f" }, // Press Alt+Shift+D to open a new pane. // - "split": "auto" makes this pane open in the direction that provides the most surface area. // - "splitMode": "duplicate" makes the new pane use the focused pane's profile. // To learn more about panes, visit https://aka.ms/terminal-panes { "command": { "action": "splitPane", "split": "auto", "splitMode": "duplicate" }, "keys": "alt+shift+d" } ] } ``` <!-- A description of how to trigger this bug. --> # Expected behavior I expect the text color to change in the terminal. <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> # Actual behavior All Text is displayed as white. ![Screenshot 2020-11-30 225304](https://user-images.githubusercontent.com/43950046/100642507-dcd7ba80-335e-11eb-90b9-4b320c663502.png) <!-- What's actually happening? --> I have already tried #2883 and all issues referenced on #3012
claunia added the Issue-QuestionNeeds-Tag-FixResolution-Answered labels 2026-01-31 02:53:14 +00:00
claunia commented 2026-01-31 02:53:15 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Nov 30, 2020):

@agarwalvaibhav0211 Could you try running the following?

printf "\e[31mA\e[42mB\e[33;44mC\e[95mD\e[m\n"

It should look something like:
image

@zadjii-msft commented on GitHub (Nov 30, 2020): @agarwalvaibhav0211 Could you try running the following? ``` printf "\e[31mA\e[42mB\e[33;44mC\e[95mD\e[m\n" ``` It should look something like: ![image](https://user-images.githubusercontent.com/18356694/100644601-2691b800-3301-11eb-800b-652682c5d090.png)
claunia commented 2026-01-31 02:53:16 +00:00
Author
Owner
Copy Link

@agarwalvaibhav0211 commented on GitHub (Nov 30, 2020):

This is the output:
image

@agarwalvaibhav0211 commented on GitHub (Nov 30, 2020): This is the output: ![image](https://user-images.githubusercontent.com/43950046/100645854-4954b880-3363-11eb-97c8-e76aaa5a15db.png)
claunia commented 2026-01-31 02:53:16 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Nov 30, 2020):

Okay, then it looks like the color scheme is actually working just fine. I'd bet your .bashrc isn't configured to enable a colored prompt. I forget what exactly turns on the colors, but it's somewhere in this block:
image

IIRC setting force_color_prompt=yes (and restarting bash) will turn the colors on.

@zadjii-msft commented on GitHub (Nov 30, 2020): Okay, then it looks like the color scheme is actually working just fine. I'd bet your `.bashrc` isn't configured to enable a colored prompt. I forget what exactly turns on the colors, but it's somewhere in this block: ![image](https://user-images.githubusercontent.com/18356694/100646279-71acca80-3303-11eb-91d6-976cb9e2706b.png) IIRC setting `force_color_prompt=yes` (and restarting `bash`) will turn the colors on.
claunia commented 2026-01-31 02:53:16 +00:00
Author
Owner
Copy Link

@agarwalvaibhav0211 commented on GitHub (Nov 30, 2020):

I uncommented force_color_prompt=yes and restarted lxssmanager and restarted the terminal, still no effect. Even in powershell and command prompt in windows terminal, there is no color

@agarwalvaibhav0211 commented on GitHub (Nov 30, 2020): I uncommented` force_color_prompt=yes` and restarted lxssmanager and restarted the terminal, still no effect. Even in powershell and command prompt in windows terminal, there is no color
claunia commented 2026-01-31 02:53:16 +00:00
Author
Owner
Copy Link

@agarwalvaibhav0211 commented on GitHub (Nov 30, 2020):

on running . .bashrc the colors load up. But on restarting windows terminal I lose it. How can I make it so that the colors are there on startup. I don't know how this happened but till a week back bashrc was executing

@agarwalvaibhav0211 commented on GitHub (Nov 30, 2020): on running `. .bashrc` the colors load up. But on restarting windows terminal I lose it. How can I make it so that the colors are there on startup. I don't know how this happened but till a week back bashrc was executing
claunia commented 2026-01-31 02:53:16 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Nov 30, 2020):

Well that's unexpected, especially considering the color is working, you're just missing some piece of config for the shell that'll enable it.

Are you running something like screen, tmux, ssh?

cmd.exe doesn't have any color by default, but does executing the following turn some color on?

set PROMPT=$e[31m$p$g$e[m

image

Is PsReadline enabled in powershell? Because that's what's responsible for colorizing the prompt:
image

image

@zadjii-msft commented on GitHub (Nov 30, 2020): Well that's unexpected, especially considering the color _is working_, you're just missing some piece of config for the shell that'll enable it. Are you running something like `screen`, `tmux`, `ssh`? `cmd.exe` doesn't have any color by default, but does executing the following turn some color on? ```bat set PROMPT=$e[31m$p$g$e[m ``` ![image](https://user-images.githubusercontent.com/18356694/100648062-07495980-3306-11eb-9081-078526595878.png) Is `PsReadline` enabled in powershell? Because that's what's responsible for colorizing the prompt: ![image](https://user-images.githubusercontent.com/18356694/100648272-52fc0300-3306-11eb-8090-11623ca5f2b5.png) ![image](https://user-images.githubusercontent.com/18356694/100648371-76bf4900-3306-11eb-89f9-7e6052e86975.png)
claunia commented 2026-01-31 02:53:16 +00:00
Author
Owner
Copy Link

@agarwalvaibhav0211 commented on GitHub (Nov 30, 2020):

Ok, solved the issue. There was a ~/.bash_profile file. It was interfering with the execution of ~/.profile and consequently ~/.bashrc. I removed the file and now its working. I can see the colors on cmd and powershell using the above steps. Thanks for the help.

@agarwalvaibhav0211 commented on GitHub (Nov 30, 2020): Ok, solved the issue. There was a ~/.bash_profile file. It was interfering with the execution of ~/.profile and consequently ~/.bashrc. I removed the file and now its working. I can see the colors on cmd and powershell using the above steps. Thanks for the help.
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 Issue-Question Needs-Tag-Fix 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#11637
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?