[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: User interaction from multiple threads
From: |
martin rudalics |
Subject: |
Re: User interaction from multiple threads |
Date: |
Wed, 22 Aug 2018 09:18:48 +0200 |
> 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"?
martin
- Re: User interaction from multiple threads, (continued)
- Re: User interaction from multiple threads, Uday S Reddy, 2018/08/29
- Re: User interaction from multiple threads, Eli Zaretskii, 2018/08/30
- Re: User interaction from multiple threads, Uday Reddy, 2018/08/30
- Re: User interaction from multiple threads, Eli Zaretskii, 2018/08/31
- Re: User interaction from multiple threads, Richard Stallman, 2018/08/26
- Re: User interaction from multiple threads, Tom Tromey, 2018/08/22
- Re: User interaction from multiple threads, Eli Zaretskii, 2018/08/22
- Re: User interaction from multiple threads, Tom Tromey, 2018/08/25
- Re: User interaction from multiple threads,
martin rudalics <=
- Re: User interaction from multiple threads, Eli Zaretskii, 2018/08/22
- Re: User interaction from multiple threads, Gemini Lasswell, 2018/08/21
Re: User interaction from multiple threads, Uday Reddy, 2018/08/29