From: Drew Adams via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>, Hong Xu <hong@topbug.net>,
Stefan Kangas <stefankangas@gmail.com>
Cc: "74983@debbugs.gnu.org" <74983@debbugs.gnu.org>
Subject: bug#74983: [PATCH] Use `keymap-set' instead of `define-key' in emacs lisp intro
Date: Fri, 20 Dec 2024 15:43:15 +0000 [thread overview]
Message-ID: <DS7PR10MB5232CCB63D72B218FE1EF23BF3072@DS7PR10MB5232.namprd10.prod.outlook.com> (raw)
In-Reply-To: <86pllmkfcm.fsf@gnu.org>
> So my suggestion is not to _replace_ define-key with keymap-set, but
> instead describe _both_, explaining that as of Emacs 29 we are
> migrating towards keymap-set, which is preferred.
+1.
next prev parent reply other threads:[~2024-12-20 15:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-19 22:36 bug#74983: [PATCH] Use `keymap-set' instead of `define-key' in emacs lisp intro Hong Xu
2024-12-20 7:01 ` Eli Zaretskii
2024-12-20 9:35 ` Stefan Kangas
2024-12-20 21:42 ` bug#74999: [PATCH v2] Recommend " Hong Xu
2024-12-21 7:19 ` Eli Zaretskii
2024-12-21 8:03 ` bug#74999: [PATCH v3] " Hong Xu
2024-12-23 20:42 ` Hong Xu
2024-12-24 3:27 ` Eli Zaretskii
2024-12-26 8:20 ` Eli Zaretskii
2024-12-26 21:46 ` bug#74999: [PATCH v4] Use `keymap*-set' over `global-set-key'/`define-key' in elisp intro Hong Xu
2024-12-26 22:05 ` Hong Xu
2024-12-27 7:44 ` Eli Zaretskii
2024-12-28 12:17 ` Eli Zaretskii
2024-12-28 19:56 ` Hong Xu
2024-12-26 21:58 ` bug#74999: [PATCH v3] Recommend `keymap-set' instead of `define-key' in emacs lisp intro Hong Xu
2024-12-27 7:37 ` Eli Zaretskii
2024-12-21 8:06 ` bug#74999: [PATCH v2] " Hong Xu
2024-12-20 15:43 ` Drew Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-12-20 21:50 ` bug#74983: [PATCH] Use " Hong Xu
2024-12-21 7:20 ` Eli Zaretskii
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=DS7PR10MB5232CCB63D72B218FE1EF23BF3072@DS7PR10MB5232.namprd10.prod.outlook.com \
--to=bug-gnu-emacs@gnu.org \
--cc=74983@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=eliz@gnu.org \
--cc=hong@topbug.net \
--cc=stefankangas@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).