GNU bug report logs - #52821
Should "(elisp) Keymaps" describe key sequences first?

Previous Next

Package: emacs;

Reported by: Stefan Kangas <stefan <at> marxist.se>

Date: Mon, 27 Dec 2021 15:25:02 UTC

Severity: normal

Fixed in version 30.2

Done: Stefan Kangas <stefankangas <at> gmail.com>

Bug is archived. No further changes may be made.

Full log

View this message in rfc822 format

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: Stefan Kangas <stefan <at> marxist.se>
Cc: 52821 <at> debbugs.gnu.org
Subject: bug#52821: Should "(elisp) Keymaps" describe key sequences first?
Date: Wed, 29 Dec 2021 17:02:32 +0100

Stefan Kangas <stefan <at> marxist.se> writes:

> 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, and the
> thing that should be exposed to (new) ELisp code is rather the new key
> description format accepted by `key-valid-p'.
>
> I'm thinking it should be moved further down, perhaps in a section next
> to this one:
>
> * Low-Level Key Binding::       Legacy key syntax description.

Yes, sounds good to me.

> There is a good description on the "new" key format in
> (info "(elisp) Changing Key Bindings").  Perhaps it should
> be moved up instead?

Yup.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no
This bug report was last modified 78 days ago.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.