Christian Duerr

> I guess that nobody is working on this since there is no activity in the last month. That's to a large degree because none of the existing solutions are...

> We can decide about it when it can be tested. I think it's worth a try. Oh, feel free to give it a try. I just don't want to...

> If I understand correctly, the issue is adding 4 to the Primary Device Attributes command. According to its documentation, 4 only indicates that sixel is available. Do applications assume...

> In Xterm, by default, everything is blocked except CSI 15 t (report screen size in pixels), which looks like a bug in their configuration: XTerm intentionally prevents interactions with...

> Maybe we can split the feature in two patches: > > * The first one with the implementation for CSI 14 t and CSI 18 t, as described in...

> The lines are all drawn with a single rectangular sixel image, with transparency. You can see how printing text over the image is useful when the text lines up...

> It is likely that not a lot of performance improvements can be made without significantly refactoring the inner Grid structure (i.e. moving shaping logic to alacritty_terminal and saving results...

> Plus when ligatures are disabled the only overhead would be the extra bytes that each cell will take. Since Alacritty already has dynamic storage in place for cell content...

> @chrisduerr, to minimize the regression, I'll make it so that harfbuzz is not called when the ligatures option is disabled for folks that would like a performant terminal, which...

> Actually, I would argue that ligatures should be off by default, because some programs might have confusing behavior with ligatures on (eg. using