bug#19945: emacsclient confused by active minibuffer

[Lars Ingebrigtsen]

Eli Zaretskii <eliz@gnu.org> writes:

>> But the first point still stands -- terminal 2 displays *scratch* first,
>> and then, one second later, switches to *foo* -- presumably there's
>> something timing out the `M-x' thing?
>> 
>> Does anybody have any insight into what might be happening here?
>
> We wait for echo-keystrokes seconds, I presume.

Yes, that seems to be it -- but why is emacsclient doing that instead of
ending the interaction immediately?  Is it doing this on purpose (to
show that we're in the middle of some keyboard action in some other
frame), or is it a bug?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no