Greetings.
I’ve looked at this problem. St has a simple double‐buffering strategy,
which creates this behaviour. Here is how w3mimg works: It gets the win‐
dow id and sits on top of X11 events. When some change is received
w3mimg draws into the shown window buffer. Now st’s simple double‐
buffering does first draw to the back buffer and then overwrites every‐
thing – the drawn image of w3mimg too.
W3mimg would need a corner‐case for this to wait a bit and then draw
again. I don’t think st should change its simple double‐buffering design
because of that w3mimg hack.
Anyone interested in the w3mimg compatibility should try to fix this in
w3mimg. It will surely help with the flickering and half‐drawing in
urxvt too.
Sincerely,
Christoph Lohmann