From: Richard Stallman <rms@gnu.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: 52821@debbugs.gnu.org
Subject: bug#52821: Should "(elisp) Keymaps" describe key sequences first?
Date: Mon, 27 Dec 2021 23:20:33 -0500 [thread overview]
Message-ID: <E1n23yT-0007OD-La@fencepost.gnu.org> (raw)
In-Reply-To: <CADwFkmmNG8TRpiphZPbadywnj4qXG2D6frtGO=ZU-hY3_FMzzg@mail.gmail.com> (message from Stefan Kangas on Mon, 27 Dec 2021 07:24:22 -0800)
[[[ To any NSA and FBI agents reading my email: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> Now that we promote the new keymap-* functions, does it really make
> sense to start the section (info "(elisp) Keymaps") with a description
> of key sequences?
> This seems to now be considered more of an internal detail,
A key sequence is a Lisp object, and it's not internal -- quite a few
programs operate on them.
The description in that node is confused between describing the
Lisp object itself and describing its printed representation.
Perhaps this node should describe the Lisp object format
and the issue of printing and inputting them should be elsewhere.
--
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
next prev parent reply other threads:[~2021-12-28 4:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-27 15:24 bug#52821: Should "(elisp) Keymaps" describe key sequences first? Stefan Kangas
2021-12-28 4:20 ` Richard Stallman [this message]
2021-12-29 16:02 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1n23yT-0007OD-La@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=52821@debbugs.gnu.org \
--cc=stefan@marxist.se \
/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.