nick black

> 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...

note that i am already displaying many PDFs in Notcurses via sixel/kitty as a result of ffmpeg cheerfully decoding them into RGBA. IMHO this kind of thing ought be client-side,...

i would love for there to be emphasis on supporting a greater number of smaller bitmaps. the ideal is what i have been calling "mosaics", where bitmaps are treated entirely...

> FWIW, as an implementor, I honestly didn't think about this feature in terms of min or max number of images, cells or pixels that I wanted to support: my...

> Since Jexer is both multiplexer and windowing system, it may show image pieces from different terminals or application windows, and any image fragment could be obscured by an overlapping...

> The thing with these bitmap image protocols (iTerm2, GIP) is that none of them except SIXEL are defined well enough that one could feasibly burn the encoder/decoder in hardware...

the importance of the kitty z-axis for me has not been its correspondence to the integers, but rather three distinct values: -1, 0, and 1. without those, you can't flexibly...

> @dankamongmen Does "graphics-over-text, not text-over-graphics" mean, you need both? Because for that we would need 3 FG-related layers: `[FG-1, FG, FG+1]`. My current thinking regarding the FG layer -...

> ideally i would like three layers, yes (and three layers ought be sufficient): text, graphic, text. to fully match the Notcurses abstraction, i would theoretically need N layers (text,...

> Hey, many thanks for responding to that matter. My big question though is: what is the Usecase, or is that a purely academical feature that has no real use....