jerch
jerch
@hackerb9 Thx for this awsome test script. I still have an offset by 1 line error, but kinda on both sides:  I mainly have an issue in my decoder,...
Well for me the key take-aways from this discussion and hacker's test script is not to perfectly resemble vt340 output (as I dont strive for perfect vt340 emulation), but: -...
@j4james For me the vertical cursor placement on a vt340 is still not quite clear in relation to the last sixel band position, also scrolling is affected by that. Thus...
> According to this depending on where in `s2` the printing stops we may end up in either `r1` or `r2`. I dont think so - the problem is, that...
> No, I don't think so. Scrolling is independent of the text cursor position. If I remember correctly, it typically scrolls as soon as a sixel band would otherwise fall...
> but the very first thing you'll encounter when reading the sixel documentation is that the sequence takes two parameters, one selecting an aspect ratio, and one controlling transparency ,...
Wrote a small endless test script here https://github.com/jerch/xterm-addon-image/blob/9a45531788e4624bb6efe842137b6f0aabf92443/fixture/endless.sh, which slowly prints a sine wave forever. The endless mode isnt supported by any TE I can test here (only get some...
Yes moving it over as official addon would remove some of the typing quirks it currently faces. :+1: Regarding the vscode integration - maybe its a good idea to mention,...
@Tyriar FYI - did a last addon release from this repo for xtermjs 5.2, as it was more convenient for me at the current stage. Will move things over to...
> Cursor positioning: I personally don't see a need for anything other than the standard behavior, and I'd be very impressed if we could even get TEs to agree on...