nick black

i eagerly support this move! i have thus far refrained from using libsixel in Notcurses. if it's going to be actively maintained, i'm likely to revisit that decision. Notcurses is...

I think this might actually hinge on emission of Set Raster Attributes (the sequence following the initial \ePq, containing geometry). If I include "1;1;x;y" in my Sixel, i get this...

> I think this might actually hinge on emission of Set Raster Attributes (the sequence following the initial \ePq, containing geometry). If I include "1;1;x;y" in my Sixel, i get...

> @dankamongmen, have you made a start on fixing this? no; i never heard anything back (is libsixel development dead? last commit was 2020-01), and wasn't interested in forking this...

> Another annoyance is that much of what libsixel does is there to directly support img2sixel. Things like processing environment variables, printing directly to stdout after encoding, the way options...

it also seems to have stripped the color from that `doubleoctagon`

awesome, i wasn't sure if you were still maintaining this useful tool (i've been using it for over a decade!). please take your time. i'll be able to test your...

@ayosec, I see you've been asked about identifying as a VT132 before (i can only find it in gitmemories: https://githubmemory.com/@ayosec?page=2), and i believe the conclusion reached is an incorrect one....

> @dankamongmen > > This is not an academic concern; [Notcurses](https://github.com/dankamongmen/notcurses) uses this control sequence to extract fairly critical information. > What should be changed to support properly Notcurses? So,...

> > as noted, alacritty appears to be answering with `\e[?4;6c`, as seen in my `strace` output above. This identifies a VT132, which _did not_ have Sixel graphics (it had...