THIS GIST WAS MOVED TO TERMSTANDARD/COLORS REPOSITORY.
PLEASE ASK YOUR QUESTIONS OR ADD ANY SUGGESTIONS AS A REPOSITORY ISSUES OR PULL REQUESTS INSTEAD!
Last active
April 8, 2024 14:02
-
Star
2,364
You must be signed in to star a gist -
Fork
168
You must be signed in to fork a gist
-
-
Save XVilka/8346728 to your computer and use it in GitHub Desktop.
True Colour (16 million colours) support in various terminal applications and terminals
@XVilka Great, I'm glad not to have to maintain my own.
(And this also explains why things have been so quiet here.)
People will keep coming here because this gist has 2200 stars and 147 forks - twenty times more links than your repo - so search results are naturally going to rank it higher than your repo.
I searched for the URL you just posted and can now see that it's referenced in the top line "Most updated version is always available", which is great, but it's very easy to miss or ignore: at first glance it just looks like the kind of link that's on every GitHub.io website, that simply points back that the very page you're already reading; it's not obvious that it's pointing at a different repo without carefully reading the URL. (Indeed it's so unobvious that I went ahead and made my own repo, thinking that none existed.)
This gist also hundreds of comments, so it's not easy to find the other links to your repo either.
To make sure that people do actually go to your new repo, instead of commenting here, I suggest starting with something like:
THIS GIST IS OBSOLETE
See termstandard/colors instead.
And to make it even more obvious, remove all the other content.
I updated the repository, thanks for the @kurahaupo's PR, also syncronized this gist with the repository, and added the link.
xterm no-longer approximates truecolor rgb to a palette, afaict.
About Querying the Terminal: the response should actually look like ...;48:2::1:2:3m - note the double colon which allows a position for the optional color space value.
I want to know why MacOS built-in terminal not support true color?
echo -ne \e[1;3;4:3;5;53;38;2;255;127;0;58;2;0;48;255;48;2;255;0;{0..255..8}mX \e[0m\n
windows terminal was not a fan of this one
@khamer @JoshMerlino what is the 4:3 supposed to do in the middle of that escape sequence, before the 38 and 48 "extended" colour codes?
@mintty @wendajiang @JoshMerlino - please note that this gist is no longer maintained. Please add your comments to the standardterm repo instead.
@XVilka - this is why I suggested that the entire content of this gist should be deleted except for the link to the repo. It would also help to mark all the comments as "hidden".
After my confirmation. Xshell6/7 support truecolor. But you must set "Tools-Options..-Advanced" check the "Use true color*"
@coolmian would you mind please adding your notes as an issue on the standardterm repo ? (Preferably create a PR with a fix.)
Reminder to future readers who want to make a comment but didn't notice the warning at the top of this page.
It's now a full-blown git repo so please write your comments there, or clone the repo and suggest changes via a Pull Request:
git clone git+ssh://github.com/termstandard/colors truecolor
THIS GIST HAS MOVED
so any comments made here will be ignored!
@kurahaupo yes, should have made this a long time ago. Now it's done.
@coolmian would you mind please adding your notes as an issue on the standardterm repo ? (Preferably create a PR with a fix.)
OK, I've done it now
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
@kurahaupo: I made repo some time ago - feel free to send PRs, issues, etc https://github.com/termstandard/colors