unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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 20:49:50 +0300	[thread overview]
Message-ID: <83wndp20ch.fsf@gnu.org> (raw)
In-Reply-To: <87h74tzrlo.fsf@gnus.org> (message from Lars Ingebrigtsen on Thu,  09 Jun 2022 19:14:43 +0200)

> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: arash@gnu.org,  55842@debbugs.gnu.org
> Date: Thu, 09 Jun 2022 19:14:43 +0200
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > 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.
> 
> The aim with these new functions were to settle on a single syntax for
> keys, and the syntax we settled on was the `kbd' one.  You can't
> do (keymap-local-set "\C-\M-i" ...) or (keymap-local-set [?\C-\M-i] .. )
> or (keymap-local-set [(control meta i)] ...) either -- that was the
> whole point of the exercise.

Then I wish us good luck convincing users to switch.





  reply	other threads:[~2022-06-09 17:49 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
2022-06-09 17:14         ` Lars Ingebrigtsen
2022-06-09 17:49           ` Eli Zaretskii [this message]
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=83wndp20ch.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).