Re: unwind-protect within while-no-input

[Spencer Baugh <sbaugh@janestreet.com>]

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Spencer Baugh <sbaugh@janestreet.com>
>> Date: Tue, 07 May 2024 15:43:43 -0400
>> 
>> Eli Zaretskii <eliz@gnu.org> writes:
>> >> It seems like it's impossible right now to use unwind-protect robustly
>> >> in face of quits, because a quit triggered in the body forms of the
>> >> unwind-protect will also interrupt the unwind forms.
>> >
>> > I think you can use condition-case for that:
>> >
>> >   (setq foo
>> > 	(condition-case nil
>> > 	    (while t nil)
>> > 	  (quit 'interrupted))) C-M-x C-g
>> >     => interrupted
>> 
>> That doesn't work with while-no-input:
>
> The message to which I responded said nothing about while-no-input, it
> made a much more general and broad assertion, see above.

1. The unwind forms should run if there is a quit, no matter what
   triggered the quit.

2. One thing that might trigger a quit is a while-no-input form outside
   my code.

3. Therefore, the unwind forms should be run even when while-no-input
   triggers the quit.

Your code does not run the unwind forms when run inside a
while-no-input.