Re: while-no-input interrupted by *shell*

[Eli Zaretskii]

> From: Michael Heerdegen <address@hidden>
> Date: Mon, 24 Sep 2018 17:24:47 +0200
> 
> I found another annoyance with `while-no-input': If you have a *shell*
> buffer producing output - for example run something like ls -R in
> *shell* - then `while-no-input' is obviously interrupted by what's going
> on there.  For example
> 
>   (while-no-input (sit-for 100))
> 
> immediately terminates when evaluated while such a shell buffer exists.
> 
> Is this expected, and is there a way to avoid this behavior?

Is it while-no-input that returns immediately, or is it sit-for?