Just in case, these posts A look at terminal emulators in two parts 1 and 2 seem to reflect st (not sure if patched) is not that good on latency, it seems xterm is the winner. Those two seem remarkably the same as 1 and 2. That's 2018, but then there's this other post on 2024 Terminal Latency that seems to find the same without a patch, but then there's a re-generation of the tests on st with a patch (I don't see a reference for it) getting much better results, but still with xterm better. st looks interesting in the amount of memory and resources required (some patches might notably change that I'd guess, like adding transparency and such), but the most appealing side of it is way less code (which again increases with patches), which xterm doesn't behave in this regard. All in all, good old xterm is still rocking these days. And yes, st with work seems able to improve, but it depends on one having to tweak it.
This topic, even though closed, has been really interesting to me. Sorry for chiming in, and I appreciate the conversation.
@clappingsnowdrop, I did the edits because in the end having what I originally copied there was a misleading mistake, sorry about that. Perhaps I didn't pay enough attention. Just in case, alacritty is actually using the Mono version of Iosevka with just IosevkaTerm Nerd Font not sure why, that definitely influenced me,
And the nerd glyphs still show small regardles, like half the height, which is somehow weird, but I can still distinguish them so that's fine. And having the Xresources settings specific to xterm and then copying them for uxterm just in case works, though not really required according to arch xterm wiki. On another look, I decided to stick with IosevkaTerm Nerd Font Mono since when I'm tired it's easier for me to notice the difference between 0 and 8 with it,
Xterm settings are ok now I believe. The xft when specifying the font is redundant when using faceName according to the man, but it doesn't hurt either. If interested:
*.termName: xterm-256color
*.vt100.locale: true
*.vt100.utf8: true
*.vt100.utf8Fonts: true
*.vt100.metaSendsEscape: true
*.vt100.backarrowKey: false
*.ttyModes: erase ^?
*.vt100.saveLines: 4096
*.vt100.translations: #override \n\
<Btn1Up>: select-end(PRIMARY, CLIPBOARD, CUT_BUFFER0) \n\
Ctrl Shift <Key>C: copy-selection(CLIPBOARD) \n\
Ctrl Shift <Key>V: insert-selection(CLIPBOARD) \n\
Alt <Key>B: exec-formatted("xdg-open '%t'", PRIMARY) select-start() select-end() \n\
*.vt100.foreground: #F8F8F2
*.vt100.background: #000000
*.VT100.colorBDMode: true
*.VT100.colorULMode: true
*.vt100.color0: #000000
*.vt100.color8: #4D4D4D
*.vt100.color1: #FF5555
*.vt100.color9: #FF6E67
*.vt100.color2: #50FA7B
*.vt100.color10: #5AF78E
*.vt100.color3: #F1FA8C
*.vt100.color11: #F4F99D
*.vt100.color4: #BD93F9
*.vt100.color12: #CAA9FA
*.vt100.color5: #FF79C6
*.vt100.color13: #FF92D0
*.vt100.color6: #8BE9FD
*.vt100.color14: #9AEDFE
*.vt100.color7: #BFBFBF
*.vt100.color15: #E6E6E6
*faceName: xft:IosevkaTerm Nerd Font Mono:style=Regular:antialias=false
*.faceSize: 15
*.vt100.charClass: 33:48,36-47:48,58-59:48,61:48,63-64:48,95:48,126:48
*.vt100.pointerColor: red
This one:
*.vt100.charClass: 33:48,36-47:48,58-59:48,61:48,63-64:48,95:48,126:48
Makes it easy to match URLs and paths in the text with double click, but I'm debating if that's what I want because it breaks one word kind of default. We'll see...