From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: arash@gnu.org, 55842@debbugs.gnu.org
Subject: bug#55842: 29.0.50; Using shorthand syntax in keymap-global-set
Date: Thu, 09 Jun 2022 19:55:53 +0300 [thread overview]
Message-ID: <8335gd3heu.fsf@gnu.org> (raw)
In-Reply-To: <87sfodztcd.fsf@gnus.org> (message from Lars Ingebrigtsen on Thu, 09 Jun 2022 18:37:06 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: arash@gnu.org, 55842@debbugs.gnu.org
> Date: Thu, 09 Jun 2022 18:37:06 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > Without thinking about this too much, my opinion is that if the new
> > APIs are to be the replacement for the obsolete ones, they had better
> > supported the same syntax, because I don't believe there's a single
> > Emacs user out there who doesn't have some key bindings in their init
> > files. If the syntax is incompatible, how can we ever convince the
> > majority to switch?
>
> I'm not sure what you mean here. People that previously said
> (local-set-key "\C-\M-i" ... ) can say (keymap-local-set "C-M-i" ...)
> just fine.
My point is that (keymap-local-set "\C-\M-i" ...) signals an error,
and a weird one at that. I hoped that we could make the APIs fully
compatible.
next prev parent reply other threads:[~2022-06-09 16:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-08 9:48 bug#55842: 29.0.50; Using shorthand syntax in keymap-global-set Arash Esbati
2022-06-09 13:35 ` Lars Ingebrigtsen
2022-06-09 16:08 ` Eli Zaretskii
2022-06-09 16:37 ` Lars Ingebrigtsen
2022-06-09 16:43 ` Lars Ingebrigtsen
2022-06-09 16:55 ` Eli Zaretskii [this message]
2022-06-09 17:14 ` Lars Ingebrigtsen
2022-06-09 17:49 ` Eli Zaretskii
2022-06-10 22:46 ` Richard Stallman
2022-06-10 8:32 ` Arash Esbati
2022-06-10 8:57 ` Lars Ingebrigtsen
2022-06-10 10:33 ` Arash Esbati
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=8335gd3heu.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=55842@debbugs.gnu.org \
--cc=arash@gnu.org \
--cc=larsi@gnus.org \
/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).