Carlos R. Mafra wrote: > The problem seems to be the key event handling at startWindozeCycle() in > src/cycling.c
Yes. And it is fixed now and will be at 'next'. It turned out to be 'next' specific in the end, but due to the fine-grained nature of the changes, it was easy to bisect it and find my brainfart. So I am sorry Paul, but _this_ bug at least is gone now. And I learned something new today, so that is still OK for me :-) But I still share Martin's initial reaction that there is a old bug lying around somewhere, but obviously not this one that is gone now. I have this dim memory of unfocused xterm's from ages ago, but it is not easy to reproduce. -- To unsubscribe, send mail to [email protected].
