Subject: bug#78737: sit-for behavior changes when byte-compiled

From: Daniel Colascione <[email-masked]>
Date: Fri, 13 Jun 2025 09:22:21 -0700

On June 13, 2025 9:18:03 AM PDT, Stefan Monnier <[email-masked]> wrote:
>> What I asked, and still didn't get an answer to, is at what point does
>> a program that calls read-event becomes interruptible by a single C-g,
>> after the changes on the branch?
>
>It's interrupted if the `C-g` occurs while running the code rather than
>while sitting inside `read-event`.  For the tight `while t` loop, it's
>virtually never.

For clarity's sake, Stefan is describing what's in the branch right now and I'm describing what will be on the branch before it's ready for merging.