Daniel Brooks

I made a pull request that fixes the test case from the foot bug, see https://github.com/ayosec/alacritty/pull/3 for details.

> with your branch, i end up with all four cells of the sixel, and the glyph is nowhere to be found. That’s actually going to be hard to implement....

Incidentally, @dankamongmen, how does https://github.com/ayosec/alacritty/pull/4 fare in your tests?

> sixel doesn't give me a way to "delete" a graphic, though Yea, good point. And if we add a clip mask then you could overwrite the sixel with text,...

> There's an issue open to deal with that. Might be worth synchronizing foot's and Alacritty's implementations? Makes sense to me. Here’s the implementation I just wrote: https://github.com/db48x/alacritty/pull/4/commits/b2a40073c68bd7e1966abddf52c3af285cfeb493 Would that...

@ayosec, I have been thinking about how to allow text to be printed over the top of graphics. Here’s a quick manual test–case: https://gist.githubusercontent.com/db48/90e22be473548a6f5ab26091f6922c65/raw/52fcd35cc91e756d41488e35491621962b3fe8a5/sixel-overwritten-with-text.six Foot breaks up the image into...

> That said, I still think there's room for a mechanism to erase sixels. Actually, the more I think about it the more I think that foot’s solution is the...

> > I allows images to be erased just by writing spaces over top of them > > Erase escapes can also be used to remove sixels, and is probably...

> This entire section seems like the sixel protocol is unnecessarily complex when it comes to interaction between text and images. I don't see any reason why you'd ever want...

Hmm. Can you explain why it is an atrocity? It’s fairly important that map labels line up with the map, for example.