From: E Sabof <esabof@gmail.com>
To: 16583@debbugs.gnu.org
Subject: bug#16583: Possible bug in inhibit-quit/abort-recursive-edit
Date: Wed, 29 Jan 2014 01:07:27 +0000 [thread overview]
Message-ID: <CAEp6Dya7wcm9RA=Hsf2Y7x5c1-fheHDDVroGx=im1_BtZ4u+tA@mail.gmail.com> (raw)
In-Reply-To: <CAEp6DyYzPcV5NZC4qd6D22k0pfSmNFhA7rhOTZXnO_fZcWVYOg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1096 bytes --]
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
[-- Attachment #2: Type: text/html, Size: 1528 bytes --]
next prev parent reply other threads:[~2014-01-29 1:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-29 0:42 bug#16583: Possible bug in inhibit-quit E Sabof
2014-01-29 1:07 ` E Sabof [this message]
2018-02-10 3:17 ` bug#16583: Possible bug in inhibit-quit/abort-recursive-edit Noam Postavsky
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAEp6Dya7wcm9RA=Hsf2Y7x5c1-fheHDDVroGx=im1_BtZ4u+tA@mail.gmail.com' \
--to=esabof@gmail.com \
--cc=16583@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.