Eli Zaretskii writes: > Feel free to dig in the display code involved in this, I don't intend > doing that any time soon. Ok, I spent some time doing that. I have attached a patch which resolves this problem on my side, but could you please look at it and see if I'm doing anything wrong? Thanks. I have tried to provide a detailed explanation of the changes in the patch message and the code itself.