[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: while-no-input interrupted by *shell*
From: |
Stefan Monnier |
Subject: |
Re: while-no-input interrupted by *shell* |
Date: |
Mon, 24 Sep 2018 14:35:50 -0400 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) |
>> This said, the bulk of my answer isn't affected: sit-for shouldn't be
>> interrupted by subprocess output either, I think.
> Really? I think sit-for is expected to stop waiting when we read
> something from a subprocess;
Hmm... Really? I'm not sure what's really the ideal behavior, nor what
we've done historically, but it seems undesirable to pay attention to
subprocess output (in general subprocess output is unrelated to the
Elisp calling sit-for).
I thought accept-process-output waits for subprocess output and sit-for
waits for input events (and we don't have any direct fonction to wait for both
at the same time).
Stefan
- while-no-input interrupted by *shell*, Michael Heerdegen, 2018/09/24
- Re: while-no-input interrupted by *shell*, Michael Heerdegen, 2018/09/24
- Re: while-no-input interrupted by *shell*, Stefan Monnier, 2018/09/24
- Re: while-no-input interrupted by *shell*, Eli Zaretskii, 2018/09/25
- Re: while-no-input interrupted by *shell*, Michael Heerdegen, 2018/09/25
- Re: while-no-input interrupted by *shell*, Eli Zaretskii, 2018/09/25
- Re: while-no-input interrupted by *shell*, Eli Zaretskii, 2018/09/29
- BUFFER_SWITCH_EVENT (was: while-no-input interrupted by *shell*), Stefan Monnier, 2018/09/25