GNU bug report logs - #16583
Possible bug in inhibit-quit

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 16583 in the body.
You can then email your comments to 16583 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

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

From: E Sabof <esabof <at> gmail.com>
To: bug-gnu-emacs <at> gnu.org
Subject: Possible bug in inhibit-quit
Date: Wed, 29 Jan 2014 00:42:52 +0000

[Message part 1 (text/plain, inline)]

I couldn't reproduce this with emacs -Q, but this is what happends. I
insert these forms into a scratch-buffer

;; QUIT gets inserted
(condition-case error
    (sleep-for 5)
  (quit (goto-char (point-max))
        (insert "QUIT")))


;; QUIT doesn't get inserted. Quit isn't displayed in the mini-buffer
(condition-case error
    (let ((inhibit-quit t))
      (sleep-for 5))
  (quit (goto-char (point-max))
        (insert "QUIT")))


GNU Emacs 24.3.1 (x86_64-unknown-linux-gnu, GTK+ Version 3.6.4) of
2013-11-02 on ubuntu

[Message part 2 (text/html, inline)]

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

From: E Sabof <esabof <at> gmail.com>
To: 16583 <at> debbugs.gnu.org
Subject: Possible bug in inhibit-quit/abort-recursive-edit
Date: Wed, 29 Jan 2014 01:07:27 +0000

[Message part 1 (text/plain, inline)]

The previous message was incomplete, and sent by accident. I have a complete
recipe now. Both forms are meant to be evaluated C-M-x, and followed by
abort-recursive-edit, or keyboard-quit.

;; QUIT gets inserted, and a Quit message is displayed.
(condition-case error
    (sleep-for 5)
  (quit (goto-char (point-max))
        (insert "QUIT")))


;; With abort-recursive-edit
;; QUIT doesn't get inserted. Quit isn't displayed in the mini-buffer

;; With keyboard-quit
;; QUIT doesn't get inserted. Quit is displayed in the mini-buffer

(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?

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.

Evgeni

GNU Emacs 24.3.1 (x86_64-unknown-linux-gnu, GTK+ Version 3.6.4) of
2013-11-02 on ubuntu

[Message part 2 (text/html, inline)]

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

From: Noam Postavsky <npostavs <at> users.sourceforge.net>
To: E Sabof <esabof <at> gmail.com>
Cc: 16583 <at> debbugs.gnu.org
Subject: Re: bug#16583: Possible bug in inhibit-quit/abort-recursive-edit
Date: Fri, 09 Feb 2018 22:17:09 -0500

tags 16583 notabug
close 16583
quit

E Sabof <esabof <at> gmail.com> 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.

Previous Next

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