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? -bean
