Re: User interaction from multiple threads

[Eli Zaretskii]

> Date: Wed, 22 Aug 2018 09:18:48 +0200
> From: martin rudalics <address@hidden>
> Cc: address@hidden, address@hidden,
>       address@hidden
> 
>  > This must happen before the prompt is displayed, so it means we will
>  > need to identify all the functions used for prompting (or channel them
>  > all into a single low-level function), and do this enqueuing there.
> 
> Earlier you said:
> 
>  >> The simplest idea is to have every primitive that displays in the echo
>  >> area to take a certain mutex before it does so.
> 
> Doesn't that boil down to something very similar, namely that "we will
> need to identify all the functions that display in the echo area"?

Yes, it does.  But the important part of the "This must happen" text
is the "before the prompt" part.  It was written in response to a
suggestion to have the prompting thread block when it attempts to read
the response to the prompt, which is _after_ the prompt was already
shown.