From: Lars Ingebrigtsen <larsi@gnus.org>
To: Daniel Mendler <mail@daniel-mendler.de>
Cc: 61184@debbugs.gnu.org, rpluim@gmail.com, monnier@iro.umontreal.ca
Subject: bug#61184: 29.0.60; keymap-local-set and keymap-global-set became less strict
Date: Tue, 31 Jan 2023 04:42:25 +0100 [thread overview]
Message-ID: <875ycngyji.fsf@gnus.org> (raw)
In-Reply-To: <5876987d-2479-f512-5767-218c8c16a909@daniel-mendler.de> (Daniel Mendler's message of "Mon, 30 Jan 2023 21:52:54 +0100")
Daniel Mendler <mail@daniel-mendler.de> writes:
> There was an old commit by Stefan Monnier, where he relaxed the API, but
> Lars made it clear back then that it is better to only accept a single
> format for the keymap API, such that guidance for the user is better due
> to clear error messages.
Yes, that was kinda the point of the whole keymap-* thing. If there's
one clear syntax, it makes many "but will this work, then?" problems
users have go away -- there's a lot of trial and error involved
currently.
In addition, having one single syntax allows people to grep for bindings
etc -- when exploring the source code, they can isearch for `C-c C-k'
(or whatever) exactly and reliably find the command they're looking for
that way (eventually).
So keymap-local-set and keymap-global-set should be fixed to be strict
again, otherwise there's not much point to the entire `keymap-*'
exercise.
next prev parent reply other threads:[~2023-01-31 3:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 20:52 bug#61184: 29.0.60; keymap-local-set and keymap-global-set became less strict Daniel Mendler
2023-01-30 21:00 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-30 21:06 ` Daniel Mendler
2023-01-30 21:45 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-30 22:03 ` Daniel Mendler
2023-01-31 3:42 ` Lars Ingebrigtsen [this message]
[not found] ` <87zg9zvzuc.fsf@gmail.com>
[not found] ` <871qnbnhhy.fsf@rub.de>
2023-01-31 10:23 ` Robert Pluim
2023-01-31 10:31 ` Stephen Berman
2023-01-31 10:37 ` Robert Pluim
2023-01-31 10:44 ` Stephen Berman
2023-01-31 16:06 ` Eli Zaretskii
2023-01-31 12:10 ` Eli Zaretskii
2023-01-31 12:49 ` Daniel Mendler
2023-01-31 14:16 ` Eli Zaretskii
2023-01-31 14:53 ` Daniel Mendler
2023-02-03 9:19 ` Robert Pluim
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=875ycngyji.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=61184@debbugs.gnu.org \
--cc=mail@daniel-mendler.de \
--cc=monnier@iro.umontreal.ca \
--cc=rpluim@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).