On Thu, 17 May 2018, Andy Lutomirski wrote: > It's definitely not intended. Can you confirm that the problem still > exists in 4.16? I have some vague recollection that this was a known issue > that got fixed, and we could plausibly just be missing a backport. I could reproduce it on 4.16.0 on my laptop. Alexander
