[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: while-no-input interrupted by *shell*
From: |
Eli Zaretskii |
Subject: |
Re: while-no-input interrupted by *shell* |
Date: |
Mon, 24 Sep 2018 20:00:19 +0300 |
> From: Stefan Monnier <address@hidden>
> Date: Mon, 24 Sep 2018 12:40:39 -0400
>
> 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; sleep-for makes a point of restarting the
wait when that happens.
- 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