Terminal: OperatorColor and ParameterColor are same color as background on Solarized Dark

[duckness]

Environment

Windows build number: Microsoft Windows NT 10.0.18363.0
Windows Terminal version (if applicable): 0.7.3451.0

Any other software?

Steps to reproduce

Leaving other settings as default, set on the profile: "colorScheme": "Solarized Dark"

Expected behavior

Text is not the same color as the background.

Actual behavior

OperatorColor and ParameterColor are same color as background

[j4james]

That's just the way the _Solarized Dark_ color scheme is setup. The default background color is set to "bright black" rather than "black", so if the foreground is set to "bright black", it's going to invisible. Frankly it's just not a good color scheme for a terminal.

[duckness]

That's just the way the Solarized Dark color scheme is setup.

I see. What is the intent/reason that it is set up in this manner? I do not recall having this issue using this theme in other terminals.

[j4james]

My understanding is the _Solarized_ scheme was originally designed for syntax highlighting, and it doesn't have the right range of colors for a terminal color scheme. Trying to use that exact same palette just doesn't map very well to terminal colors, and no mapping of that sort will ever be sensible (although the "official" one seems particularly bad IMHO).

As for why you may not have this problem in other terminals, it's likely they just aren't using the official _Solarized_ colors. Conemu, for example, has four variations of the _Solarized_ scheme, none of which match the official colors. So if there is some version of the scheme that you like in another terminal, I'd recommend you just convert those values into an equivalent Windows Terminal scheme.

[DHowett-MSFT]

Looks like this has been answered. Thanks everyone!

[gavinbeatty]

The provided Solarized Dark color scheme is unusable. I just wrote a long ffmpeg command and I absolutely needed to use a different scheme in order to fix a minor issue (-metadata:s:a:0 language=eng must be quoted as "-metadata:s:a:0" language=eng in powershell).

If the advice is for users to substitute their own scheme, I strongly recommend removing the default Solarized Dark scheme. Anyone using it is going to have a bad time, and by extension, have a bad time using Windows Terminal.

[M-Pixel]

This is still an issue, it should not be closed. It is closely related to #6390 which is still open.

The Solarized Dark theme that is included with the current version of Terminal defines brightBlack and background as the same color (source). brightBlack maps to [ConsoleColor]::DarkGray, which is the default color for Parameters in PowerShell 6.

In all _other_ color schemes defined in defaults.json, black and background are set to the same values, or no other color has the same value as background; Solarized Dark is an anomaly in this regard. Unless somebody can justify this anomaly, it should be seen as a flaw that needs fixing.

The following steps reproduce the issue:

• Install the latest version of Terminal from the Windows Store
• Change the color scheme for PowerShell to Solarized Dark

Expected: I can enter a basic PowerShell command that uses flags, and see the text that I type.

Actual: Flag text is the same color as the background, and therefore cannot be seen unless it is highlighted.

[msftbot[bot]]

:tada:This issue was addressed in #6985, which has now been successfully released as Windows Terminal v1.1.2021.0.:tada:

Handy links:

• Release Notes
• Store Download

[msftbot[bot]]

:tada:This issue was addressed in #6985, which has now been successfully released as Windows Terminal v1.1.2021.0.:tada:

Handy links:

• Release Notes
• Store Download

[msftbot[bot]]

:tada:This issue was addressed in #6985, which has now been successfully released as Windows Terminal Preview v1.2.2022.0.:tada:

Handy links:

• Release Notes
• Store Download