bug-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#16583: Possible bug in inhibit-quit/abort-recursive-edit


From: Noam Postavsky
Subject: bug#16583: Possible bug in inhibit-quit/abort-recursive-edit
Date: Fri, 09 Feb 2018 22:17:09 -0500
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/26.0.90 (gnu/linux)

tags 16583 notabug
close 16583
quit

E Sabof <address@hidden> writes:

> (condition-case error
>     (let ((inhibit-quit t))
>       (sleep-for 5))
>   (quit (goto-char (point-max))
>         (insert "QUIT")))
>
> I understand why "QUIT" might not be displayed -- the signal is not
> guaranteed to be sent immediately after then end of (let). But,
> shouldn't abort-recursive-edit also cause Quit to be displayed in the
> minibuffer? 

I don't see any bug here: abort-recursive-edit doesn't signal `quit', so
the condition-case is not triggered.

> It so happens that I have abort-recursive-edit bound to C-g, and
> ((inhibit-quit t)) seems to discard all sent "C-g"s.

I think it's rather that Emacs doesn't process input events during
sleep-for.  If you want to handle input use sit-for.





reply via email to

[Prev in Thread] Current Thread [Next in Thread]