From: Lars Ingebrigtsen <larsi@gnus.org>
To: "積丹尼 Dan Jacobson" <jidanni@jidanni.org>
Cc: 27454@debbugs.gnu.org
Subject: bug#27454: C-S-g [keyboard-quit] doesn't work to get out of disabled command choice
Date: Sun, 21 Jul 2019 17:48:54 +0200 [thread overview]
Message-ID: <87lfwr4cd5.fsf@mouse.gnus.org> (raw)
In-Reply-To: <87r2ybxwjq.fsf@jidanni.org> ("積丹尼 Dan Jacobson"'s message of "Fri, 23 Jun 2017 10:33:29 +0800")
積丹尼 Dan Jacobson <jidanni@jidanni.org> writes:
> Please make
> C-S-g [keyboard-quit]
> work just like
> C-g [keyboard-quit]
> to get out of
> Please type y, n, ! or SPC (the space bar):
> in case one's CAPS LOCK key gets stuck, etc.
> Seen on
> You have typed e, invoking disabled command gnus-summary-edit-article.
To reproduce:
emacs -Q
C-x n n
and then try using C-S-g to break out of it, and that doesn't work.
So I'm guessing that whatever does this translation normally doesn't
work in whatever disabled-command-function uses...
Oh, it's this:
(while (progn (setq char (read-event))
(or (not (numberp char))
(not (memq (downcase char)
'(?! ?y ?n ?\s ?\C-g)))))
(ding)
(message "Please type y, n, ! or SPC (the space bar): "))))
Because normally C-S-g works the same as C-g (see below). Should we
perhaps just add C-S-g to the events this function checks for?
---
C-g (translated from C-S-g) runs the command keyboard-quit (found in
global-map), which is an interactive compiled Lisp function in
‘simple.el’.
It is bound to C-g.
(keyboard-quit)
Signal a ‘quit’ condition.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2019-07-21 15:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-23 2:33 bug#27454: C-S-g [keyboard-quit] doesn't work to get out of disabled command choice 積丹尼 Dan Jacobson
2019-07-21 15:48 ` Lars Ingebrigtsen [this message]
2019-07-21 16:22 ` Eli Zaretskii
2019-07-21 17:22 ` Lars Ingebrigtsen
2019-07-21 17:53 ` Eli Zaretskii
2019-07-21 18:17 ` Lars Ingebrigtsen
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lfwr4cd5.fsf@mouse.gnus.org \
--to=larsi@gnus.org \
--cc=27454@debbugs.gnu.org \
--cc=jidanni@jidanni.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).