On 19.09.19 01:08, Dan Wilcox wrote:
I think that the actual answer is: there is no rationale, it's a bug.
actually, it turned out to be a bug *fix*.
according to the git history, the current behaviour is entirely intentional, see [747] for a discussion.
fmasdr IOhannes