Remarks on the article and the st terminal

[ShrykeWindgrace]

That's quite a feat to compare and analyze these terminals!

I started reading the article, and I decided to put my remarks here as a GH issue:

• Kovid "Goyle" (author of kitty) should be Kovid Goyal

• my personal instance of st exhibits different behavior compared to your tests; since this emulator leans heavily to applying patches to its source code for personal settings and usage (and they even maintain a list of "official" patches https://st.suckless.org/patches/). For example, the ZWJ in the article is stated as yet in my st it shows I checked the repo, there were no new commits since October, so apparently some of the st patches can lead to significantly different results. I think the main improvement comes from this patch: https://st.suckless.org/patches/glyph_wide_support/

Since these patches (think of them as config, let's be honest) are mutually dependent, I am not sure how to submit data entry in PR: Should that be a "st-with-that-and-that-and-those-patches"? Or should we just say "here's data for unpatched st, but it can do better without much effort"?

[jquast]

Thank You! I'll fix Kovid's name shortly.

On st, you are please welcome to submit a replacement yaml with the patch applied. In any situation like this I wish to present the latest data, even betas or not yet distributed, whatever best represents their latest efforts. Please make the yaml with command,

ucs-detect --save-yaml=data/linux-st-0.9.yaml --limit-codepoints=5000 --limit-words=5000 --limit-errors=500

In my case, I was using Debian Linux, it looks like they do not apply that patch in their distribution. I can direct my efforts towards debian to apply the wide support patch there https://salsa.debian.org/debian/st/-/tree/debian/latest/debian and gosh knows where else "st" terminal is packaged without it.

I will add a comment field to the yaml file that you submit with support to render that into the html report to make note of this "st with patch"

THANK YOU for your reading my article, your feedback, testing st, finding the difference etc. I appreciate it!