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, I've failed to compile the lowest common ancestor `version-2_4_4-pre1`, and also most of the FVWM versions between that and `master`, probably because the build system has been changed and maybe relies on older versions. I've managed to compile `fd21cc0a`, which does show the bug. That is from 2011, somewhere between version 2.6.1 and 2.6.0 — i.e., if it's a bug in FVWM, then it's an old one. I'm still surprised though, that 2.4.20 does not exhibit the bug... -- http://stefan-klinger.de o/X I prefer receiving plain text messages, not exceeding 32kB. /\/ \
