Stefan Klinger (2018-Nov-09, excerpt):
> Now I'll start bisecting FVWM...
Oh my!
Well, I've figured out that the described bug occurs with the current
`master` at `4e759d6f`, and also with `fvwm2-stable` at `65007a8f`.
The bug does *not* occur with `version-2_4_20` at `86004a59`.
Unfortunately,
To make this more clear: I think it's a darktable bug. But I'm
surprised to see it disappear with FVWM 2.4.20 (from 2006!). I've
failed to find the code change in FVWM that changes behaviour.
--
http://stefan-klinger.deo/X
I prefer receiving plain text m
