From: Richard Stallman <rms@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: larsi@gnus.org, arash@gnu.org, 55842@debbugs.gnu.org
Subject: bug#55842: 29.0.50; Using shorthand syntax in keymap-global-set
Date: Fri, 10 Jun 2022 18:46:44 -0400 [thread overview]
Message-ID: <E1nznOu-0000cg-Ci@fencepost.gnu.org> (raw)
In-Reply-To: <83wndp20ch.fsf@gnu.org> (message from Eli Zaretskii on Thu, 09 Jun 2022 20:49:50 +0300)
[[[ 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. ]]]
> > 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.
Even if we never convince _all users_ to switch, if most packages
use the new syntax, that will be an improvement in clarity.
--
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:[~2022-06-10 22:46 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
2022-06-10 22:46 ` Richard Stallman [this message]
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=E1nznOu-0000cg-Ci@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=55842@debbugs.gnu.org \
--cc=arash@gnu.org \
--cc=eliz@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).