From: Paul Rankin <hello@paulwrankin.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: tino.calancha@gmail.com, 27634@debbugs.gnu.org
Subject: bug#27634: 25.2.1; C-g does not quit register-read-with-preview
Date: Wed, 12 Jul 2017 12:12:27 +1000 [thread overview]
Message-ID: <1499825547.1062546.1038009976.1AADC27F@webmail.messagingengine.com> (raw)
In-Reply-To: <83a84bjb1i.fsf@gnu.org>
On Wed, 12 Jul 2017, at 12:36 AM, Eli Zaretskii wrote:
> I believe the user expectations by now are that any character should
> do. We want to exempt C-g and ESC ESC in order to allow the user to
> bail out, but other than that, I see no reason to add restrictions
> where they aren't needed. "Alphanumeric" these days means much more
> than just ASCII, and we have no reasons I can see to restrict users to
> ASCII, certainly not after so many years of the current behavior.
>
> > One overlooked thing about Tino's solution is that C-g is a keystroke and keyboard-quit is a function, which obviously aren't necessarily equivalent. What if the user remaps keyboard quit to "7"?
>
> As Andreas points out, only quit char is important. If we want to be
> holier than the Pope, we could look at its value by calling
> current-input-method. I don't object to such an extension.
Looks like you guys have this under control 👍
next prev parent reply other threads:[~2017-07-12 2:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-10 3:58 bug#27634: 25.2.1; C-g does not quit register-read-with-preview Paul Rankin
2017-07-10 6:33 ` Tino Calancha
2017-07-10 7:20 ` Paul Rankin
2017-07-10 7:59 ` Tino Calancha
2017-07-10 17:06 ` Eli Zaretskii
2017-07-11 4:14 ` Paul Rankin
2017-07-11 4:48 ` Tino Calancha
2017-07-11 5:07 ` Paul Rankin
2017-07-11 5:50 ` Tino Calancha
2017-07-11 7:20 ` Andreas Schwab
2017-07-11 14:36 ` Eli Zaretskii
2017-07-12 2:12 ` Paul Rankin [this message]
2017-07-10 19:01 ` Andreas Schwab
2017-07-21 3:47 ` Allen Li
2017-07-21 6:19 ` Tino Calancha
2017-07-21 8:40 ` Eli Zaretskii
2017-07-21 8:55 ` Tino Calancha
2017-07-25 2:45 ` Tino Calancha
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=1499825547.1062546.1038009976.1AADC27F@webmail.messagingengine.com \
--to=hello@paulwrankin.com \
--cc=27634@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=tino.calancha@gmail.com \
/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).