jasonm23/xterm-256color.svg

The (r, g, b) tuples of the xterm256 hex codes are the product of {0, 95, 135, 175, 215, 255}. There are 6^3 tuples. The pattern is broken towards the end, though, with 223 appearing in place of 215. You have xterm 200, for example, as '#ff00df'/(255, 0, 223). Should this actually be '#ff00d7'/(255, 0, 215) or does the pattern actually switch from 215 to 223 at some point?

See also https://github.com/sindresorhus/xterm-colors which uses d7 instead of df throughout. (Disclaimer: I'm just a random visitor Googl/DDGing around and have no clue whatsoever.)

After more digging – the df values are indeed wrong.

See the xterm source at https://invisible-island.net/xterm/#download, file 256colres.pl, which contains the formula for the sequence of color values used in xterm for each of the R/G/B components: (0=00, 95=5f, 135=87, 175=af, 215=d7, 255=ff).

Well, if that's the case, this command might do the trick:
$ sed -i -e 's,df,d7,g' xterm-256color.yaml

Hi all, Please consider donating to this or any of my many of opensource projects.

Not until you correct your chart and the information Wikipedia is showing the world 😜

@scarlion1 as far as I know it's correct. I would happily correct any errors. @davidchambers didm't cite a reference just noticed the pattern is a bit, inconsistent. (It's why I provided the unrolled sequence instead of providing a generator to compute it.)

I grabbed a link for https://github.com/joejulian/xterm/blob/master/256colres.h I'll cross check it today.

Welp, looks like there's at least one error, @scarlion1, @davidchambers. Updating shortly.

@mfurquimdev @felixrabe - thanks for those corrections.

Updated on https://en.wikipedia.org/wiki/Xterm thanks all.

Good boy 🫳
I gib coffee ☕☕☕☕

@scarlion1 hah! Thanks, I thought you were joking ;)