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

[Eli Zaretskii]

> From: Michael Heerdegen <address@hidden>
> Cc: address@hidden
> Date: Mon, 24 Sep 2018 19:39:48 +0200
> 
> > Is it while-no-input that returns immediately, or is it sit-for?
> 
> If I repeat the recipe with only `sit-for', I get no interrupt, so
> `w-n-i' seems involved.

What do you mean by "no interrupt"?

> I started ls -R in *shell* and evaluated
> 
> (progn (sit-for 100)
>        (message "!!!"))
> 
> The *shell* buffer got still filled, but the !!! message only appeared
> after I had hit a key.
> 
> Is a bug report justified?

It cannot hurt, especially if you could come up with a convenient
reproducer.