Write-Host -ForegroundColor Gray Shows Whatever The Supplied Foreground Color in Scheme is

[CamRatliff]

Windows Terminal version (or Windows build number)

1.6.105671.0

Other Software

PS 7.1.3

Steps to reproduce

Write-Host "Hello world!" -ForegroundColor DarkGray
Write-Host "Hello world!" -ForegroundColor Gray
Write-Host "Hello world!" -ForegroundColor White

Expected Behavior

Write-Host -ForegroundColor Gray "Hello world!" returns a string formatting using the Gray (White or BrightBlack?) color as defined in the console.

Actual Behavior

Strings formatted with -ForegroundColor Gray are whatever the console's Foreground color is defined as, in the color scheme JSON of the WT theme.

When using Write-Host with -ForegroundColor Gray, Windows Terminal uses the Foreground key from the Color Theme's JSON to determine the color, instead of the White key.

Here is a screenshot with the defaults as the theme

Here is a screenshot with the foreground key turned off

Here is a screenshot using White as the foreground key

Here is a screenshot using Red as the foreground key

Here is a screenshot using Cyan as the brightBlack key

Here's a screenshot with the foreground key turned off, and the Powershell console's foreground set to white.

Finally, here's a screenshot with the foreground key set to Red, and the Powershell console's foreground set to white.

[DHowett]

Thanks for the comprehensive report. This boils down to how we handle compatibility with poorly-behaved powershell versions.

Unfortunately, this is by design. PowerShell erroneously tells us to use a black background and gray foreground so often that it would cause there to be black streaks across the display (even if the terminal background was set to white or acrylic transparency) and your preferred foreground color to be ignored.

We had to disable gray foreground and black background for PowerShell, specifically. #6810. Tracking the "fix" in /dup #6807.

[ghost]

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!