From: Drew Adams <drew.adams@oracle.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, 9 Jan 2021 13:21:47 -0800 (PST) [thread overview]
Message-ID: <b30ee8bc-01a4-4b4a-8a79-1284e8cdfb0f@default> (raw)
In-Reply-To: <CAGP6POLtn0zW=wc=2qVP2UucyARN7cgD5JU5FP8xj2XGY6hF0w@mail.gmail.com>
Wrt `C-q' (besides what was said about quoting):
If I remember right, at one point `C-s' and `C-q' in Emacs may have had their traditional ASCII Control character behaviors of XOFF and XON.
(At least I seem to remember _some_ keys doing that. Maybe it was `<scroll>', usable as a toggle.)
https://en.wikipedia.org/wiki/Software_flow_control
ASCII Control character behaviors were a partial starting point for some Emacs keys, I think.
https://en.wikipedia.org/wiki/ASCII#Control_characters
On the other hand, there may also have some influence from UNIX shell control chars (`C-c', `C-d'), though I don't recall anything specific.
Some is history. Some is mnemonics. Some is ...
next prev parent reply other threads:[~2021-01-09 21:21 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 ` Drew Adams [this message]
2021-01-09 17:39 ` The correspondence of the command-name and its key-sequence Kévin Le Gouguec
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
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=b30ee8bc-01a4-4b4a-8a79-1284e8cdfb0f@default \
--to=drew.adams@oracle.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.
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).