Daniel Eklöf

That said, it looks like chafa isn't emitting a newline at all, so even with the tweaked cursor placement (always put it on the last row touched by the sixel),...

@PerBothner @christianparpart @wez I was hoping we could all agree on how to implement cursor placement after emitting a sixel. As far as I can tell, foot, DomTerm, Contour and...

How about this: For sixels without an explicit width/height (no raster attributes), assume all sixels are 6 pixels tall. I.e don't bother inspecting the image looking for transparency. For sixels...

My understanding is the text cursor's horizontal position isn't changed at all. It only moves vertically. Put another way, it is positioned "at the beginning of the sixel", i.e in...

@hpjansson related, but perhaps worth its own issue; chafa currently ends the sixel with a GNL ('-'). Is this intentional? It adds an extra, empty, graphical row. I think it...

I agree, mostly. It's important we unify the vertical placement since it affects scrolling. Horizontal placement isn't as important, *except* if a terminal places it *after* the image, in which...

Foot currently allows "level 2" sixels to be extended, both vertically and horizontally. That is, the image will be resized, if necessary, to accommodate whatever the encoder is emitting. I'd...

> Should the text after a new line overwrite transparent pixels at the bottom of the graphic? I believe so unless the RA width and height specify otherwise. Not sure...

Thanks for clarifying the issue with trailing transparent rows. I actually did it that way in earlier versions of foot, simply because XTerm did. I changed it when I couldn't...

Not sure if it's a bad thing :) I was surprised when I noticed it. It is also different from how fcitx5 works (and I'm not saying it is better...)