[Tickit-dev] Forcing RGB8 support in terminal driver

[Paul "LeoNerd" Evans]

I have a patch supplied by a user which makes the xterm driver directly
read getenv("COLORTERM")  looking for either "truecolor" or "24bit" to
force RGB8 support on, because apparently some terminals set that but
don't reply to DECRQSS.

I dislike it though, primarily, I don't think a term driver itself
ought to be getenv()'ing.. it ought to be more abstracted than that.
But also I dislike the idea of needing to override - really, said
terminal ought to support DECRQSS on SGR to let the driver discover
that for itself.

But I am considering making TICKIT_TERMCTL_COLORS writeable to somehow
support this idea. That if you forcibly set it to (1<<24) it'll turn on
RGB8 mode. Then maybe higher up the code chain (e.g. where
getenv("TERM") is currently read), the code can additionally force that
mode on if it thinks appropriate. What does anyone think?


Also I -might- add a (readonly) TICKIT_TERMCTL_DRIVER that returns a
string giving the name of the driver ("terminfo" or "xterm" currently),
but that needs a getctl_str which currently doesn't exist. We'll need
that sometime when we have clipboard support, so I could add it.

-- 
Paul "LeoNerd" Evans

leonerd at leonerd.org.uk      |  https://metacpan.org/author/PEVANS
http://www.leonerd.org.uk/  |  https://www.tindie.com/stores/leonerd/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: OpenPGP digital signature
URL: <http://mail.leonerd.org.uk/pipermail/tickit-dev/attachments/20190409/acda25a6/attachment.sig>