Custom palette support about kmscon

[viccie30]

Libtsm definitely has the necessary bits to enable a custom palette from kmscon.conf. It nearly has everything to support the Linux code as well, except for one bit.

libtsm rightfully expects every OSC sequence to end with either '\x07' or '\9C' (https://github.com/Aetf/libtsm/blob/4faef1e0a04b54eefbd2245abeea197a702e2086/src/tsm/tsm-vte.c#L2335-L2338). https://man7.org/linux/man-pages/man4/console_codes.4.html calls out an issue with the Linux palette set and reset sequences: they don't need to end on ST ('\x9C'). Like xterm, libtsm would mishandle these sequences without special treatment. Is this something you'd want added to libtsm in some way? Or just not support this and just set palettes from the configuration file?

The other issue is related to the Linux palette reset sequence. Except for a custom palette, there is no way for kmscon to reset the palette to the defaults for a built-in libtsm palette. Either kmscon should be able to query the current palette or the default palette from libtsm, or the whole machinery should be added to libtsm after all.

[viccie30]

I don't know if you've already worked on this, but I would like to have a go at this if not.

My personal idea would be to do both: allow a default custom palette in kmscon.conf and allow changing on the fly through escape codes. I think that would have to be implemented on the side of libtsm then?

[Aetf]

Feel free to take this 😄

libtsm already has the necessary bits for both. There's tsm_vte_set_osc_cb that can be set from kmscon to handle any OSC sequences. The gtktsm example uses it to handle title changes. kmscon can call tsm_vte_set_custom_palette during the OSC callback to change colors.

[Aetf]

Let's forget about it then. Setting a custom palette from the config file should be good enough for most use cases.