Ansi color 243 hard-wired to color 8 (brightBlack) #6508

Closed
opened 2026-01-31 00:40:35 +00:00 by claunia · 2 comments
Owner

Originally created by @9Rune5 on GitHub (Feb 18, 2020).

Environment

Windows build number: 10.0.18363.0
Windows Terminal version (if applicable): 0.9.433.0

Steps to reproduce

testcolor.txt

testcolor.txt is a file containing ansi codes. Bottom line is a greyscale.

  1. (from the command line) type testcolor.txt
  2. Change "brightBlack" of the current colour scheme
    "brightBlack":"#555555"

Expected behavior

Ansi color 243 should not change.

"232-255: grayscale from black to white in 24 steps" (https://en.wikipedia.org/wiki/ANSI_escape_code)

The old console host works as expected.

Actual behavior

Ansi color 243 is hard-wired to color 8.

Originally created by @9Rune5 on GitHub (Feb 18, 2020). # Environment ```none Windows build number: 10.0.18363.0 Windows Terminal version (if applicable): 0.9.433.0 ``` # Steps to reproduce <!-- A description of how to trigger this bug. --> [testcolor.txt](https://github.com/microsoft/terminal/files/4218164/testcolor.txt) testcolor.txt is a file containing ansi codes. Bottom line is a greyscale. 1. (from the command line) `type testcolor.txt` 2. Change "brightBlack" of the current colour scheme "brightBlack":"#555555" # Expected behavior Ansi color 243 should not change. "232-255: grayscale from black to white in 24 steps" (https://en.wikipedia.org/wiki/ANSI_escape_code) The old console host works as expected. # Actual behavior Ansi color 243 is hard-wired to color 8.
claunia added the Resolution-Duplicate label 2026-01-31 00:40:35 +00:00
Author
Owner

@DHowett-MSFT commented on GitHub (Feb 18, 2020):

/dup #2661

@DHowett-MSFT commented on GitHub (Feb 18, 2020): /dup #2661
Author
Owner

@ghost commented on GitHub (Feb 18, 2020):

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!

@ghost commented on GitHub (Feb 18, 2020): 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!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#6508