On 25 September 2018 at 16:32, Laslo Hunhold <d...@frign.de> wrote: > On Tue, 25 Sep 2018 16:28:22 -0700 > AR Garbe <garb...@gmail.com> wrote: >> This is something I was considering, however it looks like the water >> of the babie's bathtub is poisoned with freetype2/fc bacteria. I don't >> wanna introduce abstractions that might be premature, hence I suggest >> to fully revert back to XFont* API until something like this is proven >> to be work properly. It can only improve the performance of st as well >> ;) > > what a fitting analogy! :D > > I am also in favor of going back to XFont. It's the best compromise, but > we should not forget the drawbacks.
Hehe, well there are drawbacks, but at least we are well aware of the limitations and we won't see people complaining about crashes on emoji glyphs ever again ;) -Anselm
