On 2023-11-26, coolbean <[email protected]> wrote: > for context, upstream xterm has default sixel support under various > terminals that it emulates however under openbsd's xenocara build > of xterm it prints nothing. > > now while snooping around about it yesterday i discovered that > inside xterm's configure.in, sixel support is enabled by default > and regis support is not, however sixel screen dump/print_graphics > actually inherits its default from the state of regis, despite > being required for both sixel and regis to work fully. > > so i have the question for anyone that might know, was this > intentional to avoid some sort of bug that occurs when regis is > disabled but print_graphics enabled that i simply havent > encountered while testing with the print_graphics default changed to yes, or > should i report this on bugs?
OpenBSD's build of xterm does not use autoconf. sixel was intentionally not enabled. While I don't know the original reason for this decision, it did save us from CVE-2022-24130. Your question about sixel/regis is probably better to go upstream because sixel isn't part of OpenBSD's build. -- Please keep replies on the mailing list.
