GNU bug report logs - #78737
sit-for behavior changes when byte-compiled

Previous Next

Full log

Message #266 received at 78737 <at> debbugs.gnu.org (full text, mbox):

From: Stefan Monnier <monnier <at> iro.umontreal.ca>
To: Daniel Colascione <dancol <at> dancol.org>
Cc: 78737 <at> debbugs.gnu.org, Eli Zaretskii <eliz <at> gnu.org>, pipcet <at> protonmail.com
Subject: Re: bug#78737: sit-for behavior changes when byte-compiled
Date: Fri, 13 Jun 2025 14:00:31 -0400

>>> 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.

I thought the difference was only in terms of "emergency quit", which
I think is not what Eli referred to when he meant "interruptible".
[ I suspect these kinds of differences of intended meaning are
a significant part of the misunderstandings in this thread.  ]


        Stefan

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.