Comment 4 for bug 775967

> On Fri, 10 Jun 2011, auquicu wrote:
>
>>>> Public bug reported:
>>>>
>>>> Binary package hint: xterm
>>>>
>>>> Start X, and under X an xterm running bash.
>>>> Select some text and paste it at the command prompt. It is not echoed.
>>>> Type any keyboard character and the mouse-pasted text appears,
>>>> followed by the typed character.
>>>> This is not a bash problem: typing to cat or ed shows the same
>>>> results.

>> If I kill twm, and type _mwm_ to the shell prompt in the current window,
>> then the reaction is
>>
>> $ mwm
>> The program 'mwm' can be found in the following packages:
>> * lesstif-bin
>> * motif-clients
>> Try: sudo apt-get install <selected package>
>>
>> and nothing happens until I touch the mouse (or some key such as Shift
>> on the keyboard). It looks like a synchronization problem on some event
>> queue.
>
> Perhaps the "pointerMode" resource is related. If you set it to 0 (zero),
> it's supposed to disable that feature.

I played a bit with pointerMode but see no relation. For 0 the mouse
pointer is shown, for 1 it is not shown until one moves the mouse.
As far as I can see, this works as documented.

I also played a bit more with the bug reported. I now find that "It is not
echoed" may have to be replaced by "It is echoed after approximately 50
seconds". However, if I open an "emacs --no-splash" window, without doing
anything there, no keyboard or mouse activity related to that emacs
window, then pasted text is echoed afted approximately 1 second.

So, the hypothesis is that emacs does some polling that xterm does not do,
and this polling moves some event queue.

That was the "select and paste and wait for the pasted text to be echoed".
The other reproducible bug is "say _mwm_, see the message about it not
being installed, and wait for the following shell prompt". This shell
prompt comes after a varying amount of time, sometimes after 50 seconds,
sometimes after 10 seconds, sometimes almost immediately. But what also
happens is that only the top half (a few but not all pixel lines) is
shown,
and the remainder appears first after a while, or upon activity of mouse
or keyboard.

I imagine that it is xterm that does the drawing, so if sometimes only the
top half of a line is displayed, that looks like an xterm or X bug.