[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 12:40:39 -0400 |
|
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) |
>> (while-no-input (sit-for 100))
> Is it while-no-input that returns immediately, or is it sit-for?
Oh, good point, I skipped the body of the while-no-input and hence
didn't notice the sit-for.
This said, the bulk of my answer isn't affected: sit-for shouldn't be
interrupted by subprocess output either, I think.
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