Comment 3 for bug 1850252
Revision history for this message
| Egmont Koblinger (egmont-gmail) wrote | #3 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
> of the good enough
In my opinion, sixel is nowhere near good enough for today's standards.
> but the image viewing program I use simply catches SIGWINCH and resends the image if needed
There's a lot more to this story, and I'm not going to go into the details _again_, sigh. E.g. what if it's not an app that keeps running refreshing its screen, but one that prints the image once (like an "ls") and then quits? Who is going to specify and implement the behavior of the terminal's data buffer in a robust, non-crashing way if the text flow and the image within live separate lives during a resize; adding gap, or moving them closer to each other so that they overlap – let alone what a crappy user experience this is? Also what about plenty of other things, like, tmux-ability, being able to crop the image by the terminal? There's a _lot_ more to this extremely complicated story.
> Maybe the VTE folks have changed their minds by this point?
VTE folks is two people at this moment, one of them is me, and I haven't changed my mind. I'd love to support a _good_ image protocol, which sixel is not.