James Holderness

I believe this was fixed in the libsixel/libsixel fork in PR https://github.com/libsixel/libsixel/pull/26.

The way timg currently detects the supported protocol is with an XTVERSION query that returns the terminal name, which is compared against a hardcoded list of terminals. This is not...

> Sounds like the terminal is neither implementing the `>q` query nor the primary device attributes Windows Terminal doesn't support the `>q` query, but it does support device attributes. And...

> The ambiguity between 4 and 42 was deliberate as I see this as a best-effort fallback solution, and I have also not seen any terminal I played with return...

> I already changed the detection so that only 4 not 42 is detected. Thanks. I only noticed that after I'd sent my message, but I've tested both versions now...

I should also mention that the "default cursor placement" is technically incorrect, so you tend to get text overlapping the bottom of images in Windows Terminal, and the grid layouts...

With `TIMG_SIXEL_NEWLINE_WORKAROUND` set to 1, that's definitely an improvement, but videos do still scroll sometimes, and grid view items aren't always aligned. It just depends on the image height and...

> I think that is a problem of the terminal, not properly reporting the size in pixels of their fonts. The Windows Terminal sixel implementation is designed to be compatible...

> I am almost tempted to get an original vt340 from ebay if one shows up There's a guy who did exactly that a couple of years ago, and he...

I could "fix" it so that it's VT340 compatible, and thus should work in Windows Terminal, but there's a good chance it'll then no longer work in multiple Linux terminals....