st-flexipatch VS xst

Check out st-flexipatch if you want to simplify the patching process. I've never used it but would if I was coming to st for the first time! https://github.com/bakkeby/st-flexipatch

https://github.com/bakkeby/dwm-flexipatch https://github.com/bakkeby/st-flexipatch

If you just need a well-configured st terminal without deep understanding how it works, use st-flexipatch

https://github.com/bakkeby/st-flexipatch -- "The flexipatch builds have a different take on patching where preprocessor directives are used to decide whether or not to include a patch during build time. This means, for better or worse, that the code contains both the patched and the original code. The aim being that you can pick and mix your patches from a configuration file and just compile."

For testing st patches, try: https://github.com/bakkeby/st-flexipatch

I use xst, a fork of st. It does everything I need it to do. It's not very feature-full, but even if I had the kinds of features other terminal emulators have I wouldn't use them, so this is fine.

https://github.com/gnotclub/xst

Anyway, I digress. OP might want to check out xst

Then I found this page where someone suggests what to do when st gives the error "font weight does not match". And surely, by uncommenting the line f->badweight = 1; * in x.c I have managed to set up the lovely Fira Code font with original colours.