From: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>
To: Hongyi Zhao <hongyi.zhao@gmail.com>
Cc: help-gnu-emacs <help-gnu-emacs@gnu.org>
Subject: Re: The correspondence of the command-name and its key-sequence.
Date: Sat, 09 Jan 2021 18:39:00 +0100 [thread overview]
Message-ID: <87bldyc8nf.fsf@gmail.com> (raw)
In-Reply-To: <CAGP6PO+F-G_xiyZirDR4EGMhqkVcg-pRm=rCY6yReUUqrmAoTw@mail.gmail.com> (Hongyi Zhao's message of "Sat, 9 Jan 2021 14:05:36 +0800")
Hongyi Zhao <hongyi.zhao@gmail.com> writes:
> To summarize, why use C-g to
> represent the command keyboard-quit, instead of other more directly
> related forms, say, C-q.
Previously, on emacs-devel:
<M8Qc6iq--3-2@tutanota.com>
https://lists.gnu.org/archive/html/emacs-devel/2020-05/msg03273.html
Followed by:
<7w367f6y81.fsf_-_@junk.nocrew.org>
https://lists.gnu.org/archive/html/emacs-devel/2020-06/msg00009.html
My personal takeaway:
Lars Brinkhoff <lars@nocrew.org> writes:
> Now, why TECO uses Control-G for "quit", I don't know. ASCII "BEL" as
> an "alarm" is a plausible theory, but hard to verify. In general
> there's no strong link between control characteras as inputs and their
> corresponding output behaviour.
next prev parent reply other threads:[~2021-01-09 17:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-09 6:05 The correspondence of the command-name and its key-sequence Hongyi Zhao
2021-01-09 6:32 ` Drew Adams
2021-01-09 7:16 ` Hongyi Zhao
2021-01-09 8:23 ` Omar Polo
2021-01-09 9:33 ` Hongyi Zhao
2021-01-09 10:00 ` Omar Polo
2021-01-11 8:04 ` Hongyi Zhao
2021-01-11 8:20 ` Omar Polo
2021-01-11 9:51 ` tomas
2021-01-09 17:20 ` Francis Belliveau
2021-01-14 22:21 ` ASCII - Why...? -- as promised Francis Belliveau
2021-01-09 21:21 ` The correspondence of the command-name and its key-sequence Drew Adams
2021-01-09 17:39 ` Kévin Le Gouguec [this message]
2021-01-09 18:47 ` Eduardo Ochs
2021-01-09 22:29 ` Kévin Le Gouguec
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=87bldyc8nf.fsf@gmail.com \
--to=kevin.legouguec@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=hongyi.zhao@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 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.