15:31 <ovf> dnkl: is there a way to save/restore enough of the terminal state that "are we currently in sixel mode" would be in it?

15:32 <ovf> my rlwrap-like thing passes through program output but sometimes wants to e.g. redraw the edit line, and then continue with output

15:40 <dnkl> ovf: don't think so. A sixel is emitted as a single escape sequence. You can't inject anything else in the middle of it

15:42 <ovf> so the two options are either second-guess (charitably, track) the terminal state handling in my own state machine (granted i do have it), or resort to hacks (charitably, heuristics) like i think real rlwrap does. :-(

15:44 <dnkl> yeah, a proper vt state machine is required to handle this correctly. Note that the same limitations apply to all escape sequences

15:48 <ovf> i seem to be worried about the wrong things. e.g. what if someone was never going to finish the sixel dcs? i'll be in a bad state, but then so will be the terminal...