hackerb9

I put a sleep in the first test and it seems to clear the screen when the first byte after q is received. (I didn't send the backslash for five...

Oh, duh. Of course, it's waiting for DECGRA. So a double quote after the q does not clear the screen.

For the second test, it clears the screen unless there is some sixel data. For example, this clears the top left corner (as soon as it receives the escape character):...

I think clearing the whole screen when there is no sixel data is a bug as the following should be equivalent, but correctly clears just the top left corner: printf...

Speaking of weird finite state machine things, maybe I'm just tired, but I don't understand how my VT340 seems to know to get out of sixel mode when I get...

> Technically I think the ANSI/ECMA specs require that a `DCS` sequence be terminated by an `ST`, and thus shouldn't be executed if it isn't. But as far as I...

Results are in [unexpected.png](../blob/main/j4james/unexpected.png). Note that the backwards question mark is the VT340 way of indicating an unknown character.

Bizarrely, that is exactly what displays on the screen. I tried it again and, during MediaCopy command, most of the colors got switched to `47;47;47`. Here's is the header of...

No idea what went wrong before. This time it worked. I had a suspicion it was glitching because of background transparency, but that doesn't seem to be it. Another possibility...

A 10x6 block with a 240x240 background fill that is 6 rows down.