Terminology is limited to only display 256 colors? #12
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I was making a NeoVim theme, when I noticed that the "very-dark purple" color was not showing up in the HEX value #1c1726 on my terminal (like in the half-right-side of the screenshot), I was trying other values without seeing any difference until inmediately changed to pretty much brighter color (like the colors appears only in big "steps")
Then I decided to install gnome-terminal to see what happens, surprised, it displays correctly the color I was trying to set (the one in the bottom-left)
https://i.imgur.com/5GGSPXN.png
I also tried to set the variable:
and to disable the TERM checkbox option of 256 colors in the options... no effect, it looks like terminology is limited to a smaller amount of colors, which may be 256
Related: #6
I just found this handy way to test "truecolor" in terminals (try it in terminology & gnome-terminal):
terminology understands truecolor escapes but will approximate them down to 256 color because that is what eva's textgrid supports. it has 1 byte for fg and 1 byte for bg color. that's the public api/data struct exposed.
So terminology is compatible (not failing) with truecolors but doesn't displays them. Could be possible to make it displaying true colors? this can be useful for example in editor colors where it is limited and it jumps from "pure black" to "creamy purple" instead of having a dark purpleish tone like in the previous screenshot
Maybe as an option:
[ ] Enable TRUECOLORS to allow more than 256 colors (uses more memory)
Or even better, maybe making it to render true colors dynamically when it encounters these escape codes 😎
don't use truecolro escapes then :) this would be similar to asking if it's possible for a commodor64 to display truecolor. it can't. it has 16 colors. evas's textgrid exposes colors with the above limit. terminology has to live with it. you'd have to create an altyernate evas textgrid api to expose much wider color fields in a parallel api and that doesn't exist.