dwmblocks-async VS dwm-vanitygaps

Depends. There are several dwmblocks implementations floating around. I use https://github.com/UtkarshVerma/dwmblocks-async and it has a signal per block that can be sent with pkill to rerun the script.

Maybe some day I'll finish configuring dwm/dwl and dwmblocks/somebar+someblocks and use it, but even then XFCE will always be my fallback.

Ah yes, correct. The dwmblocks-async author says statuscmd is needed on https://github.com/UtkarshVerma/dwmblocks-async for clickable blocks. I did pull that in a while ago into my dwm code, but forgot that it's only needed there for clicking. Good call!

I recommend you to use this version of dwmblocks: https://github.com/UtkarshVerma/dwmblocks-async

https://github.com/UtkarshVerma/dwmblocks-async is very nice.

currently i use dwmblocks-async with this configuration:

As these were not hindrances to my work, I've had these on the back burner for quite some time, until today when I humbly present to you dwmblocks-async. It fixes the above-mentioned issues by doing the following:

I surfed the net a bit, but couldn't find this particular patch. Either I'm blind or it doesn't exist. Although, I've managed to find this, but it seems there's no addition of vanitygaps(gappih, gappoh, gappiv, gappov etc..) to pertag functions. There's also this, but again no mention of vanity gaps in pertag functions. Nevertheless, I'll see if it works in case I'm really blind.

If you like dynamic wm, i know one for dwm, you can take a look at https://github.com/bakkeby/dwm-vanitygaps. It also explains what dwm patches have been added, so it's more or less ready to use