Daniel Eklöf

> introduces one or more newlines since any text printed after a sixel will be put one line below the last pixel. If you use private mode 8452, the cursor...

> _Note: To avoid false high throughput artefacts by aggressive prebuffering, the script waits for a cursor position report sent from the terminal after the Sixel data._ @j4james nice touch!

There's been some performance improvements to the sixel decoder in foot since 1.6.4. Still, sixvid with nyancat is much slower than I'd expect. This is something I'm going to want...

> Uh. What happened to your XTerm? Good question... turned out to be this: ``` xterm*maxGraphicSize: 10000x10000 ``` With the default `maxGraphicSize` I get 110 FPS.

And with `1920x1080` (to match my monitor), I get just above 100 FPS.

I took a quick look at the nyancat issue, but not really sure what's going on; none of the processes are using nowhere near 100% CPU. My best guess atm...

@hackerb9 the escapes used by lsix (the first one, `\e[?2;1;0S`) works for me (in Sway). Using `swaymsg` will only work under Sway. Also, note that `swaymsg` will return the **full**...

> When you run this command, does it give you the same dimensions you get from swaymsg? @savchenko @hackerb9 note: I'd expect the escape to return (possibly) slightly smaller values,...

I think we can conclude that HLS isn't something that is used very much. Assuming libsixel is correct, the following screenshots shows that only mlterm and foot handle HLS correctly....

In foot, writing a sixel on top of another sixel blows away the first sixel, on a per cell basis. Which means foot doesn't handle transparent sixels layered on top...