Kovid Goyal

There is no end. Rendering works by mapping each cell to a number. That number acts as an index into a sprite map which is uploaded to the GPU. The...

Rendering happens per cell, there is no vertex data for a cell. The vertex locations on the screen are calculated in the shader from instance id. See the section set...

The general problem of ligatures certainly. This particular issue however, might be solved by improving wcswidth calculations for flags. I have to look into it someday when i have time.

yes the idea would be for wcswidth to know about flags sequences. I dont know how feasible that is, will have to see.

wcswidth is defintely not always equal to sum wcwidth() if it were then emoji variation selectors would not work. See the kitty implementation of wcswidth() in screen.c. The only reason...

And yet it does. Pretty much all advanced terminal applications use their own wcswidth() implementations, precisely because glibc's is a broken umm POS. glibc is not the canonical source for...

No worries, and yes looking into modifying wcswidth for ZWJ/flags is why this issue remains open.

@ctrlcctrlv if you are thinking of implementing this, please keep in mind that I wont accept changes that have significant negative performance impact on normal (i.e. no bidi) usage. Given...

I dont care about enabled by default or not, I care about it not impacting performance in the absence of bidi control sequences/text.

It's a cool idea, I really like it, however, I dont want to add unstable Wayland protocols to kitty. If and when this protocol makes it to wayland-protocols so that...