unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Paul Rankin <hello@paulwrankin.com>
To: Tino Calancha <tino.calancha@gmail.com>
Cc: 27634@debbugs.gnu.org
Subject: bug#27634: 25.2.1; C-g does not quit register-read-with-preview
Date: Tue, 11 Jul 2017 15:07:43 +1000	[thread overview]
Message-ID: <3D7307DF-FB47-49FF-AEA9-67659E12821A@paulwrankin.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1707111328400.16870@calancha-pc>



> On 11 Jul 2017, at 2:48 pm, Tino Calancha <tino.calancha@gmail.com> wrote:
> 
> 
> 
>> On Tue, 11 Jul 2017, Paul Rankin wrote:
>> 
>> 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"?
> I thought about that, but i discarded because i think binding something
> other that `keyboard-quit' to `C-g' is a misuse.  The Emacs manual is full
> of mentions to `C-g' as `keyboard-quit'.
> There is even the following remark in the tips section:
> 
> "don't bind a key sequence ending in @key{C-g}, since that
> is commonly used to cancel a key sequence."
> 
> If a user want to ignore such kind of advice he/she should
> not expect everything will work the same.

I'm gonna do this just to mess with you 😉

> Maybe we can fix this so that `register-read-with-preview'
> will work with `C-g' bound to `my-cool-foo-command'; but we
> cannot assure that no other Emacs part is affected because such
> misguided `C-g' binding.  We must encourage users to follow
> good practices.

While I think encouragement and enforcement are different things, the point about C-g is more what if the user *also* binds keyboard-quit to "7". In this case the user expects 7 to call keyboard-quit, not just C-g.

Also as Eli said ESC ESC is supposed to keyboard quit I think.

But main thing, as in life, better to look for what what you want than control for what you don't want.





  reply	other threads:[~2017-07-11  5:07 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 [this message]
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
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=3D7307DF-FB47-49FF-AEA9-67659E12821A@paulwrankin.com \
    --to=hello@paulwrankin.com \
    --cc=27634@debbugs.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).