From: Andreas Schwab <schwab@linux-m68k.org>
To: Philip Kaludercic <philip.kaludercic@fau.de>
Cc: emacs-devel@gnu.org
Subject: Re: Deprecation of define-key?
Date: Fri, 29 Jul 2022 18:16:54 +0200 [thread overview]
Message-ID: <87mtcr99mx.fsf@igel.home> (raw)
In-Reply-To: <875yjgszm4.fsf@posteo.net> (Philip Kaludercic's message of "Fri, 29 Jul 2022 17:33:07 +0200")
On Jul 29 2022, Philip Kaludercic wrote:
> The docstring for `define-key' currently says:
>
> This is a legacy function; see ‘keymap-set’ for the recommended
> function to use instead.
>
> yet `keymap-set' uses `define-key' internally. Is there a long-term
> plan to re implement parts of keymap.el in C?
>
> If not, this should be rephrased (my understanding up until now was that
> keymap-* is a higher-level abstraction)
I don't see any need. The use of define-key in keymap-set is an
implementation detail.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2022-07-29 16:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-29 15:33 Deprecation of define-key? Philip Kaludercic
2022-07-29 16:16 ` Andreas Schwab [this message]
2022-07-30 11:46 ` Philip Kaludercic
2022-07-30 11:51 ` Lars Ingebrigtsen
2022-07-31 6:48 ` Jean Louis
2022-07-31 7:14 ` Visuwesh
2022-08-02 9:44 ` Augusto Stoffel
2022-08-02 9:54 ` Philip Kaludercic
2022-08-02 10:01 ` Lars Ingebrigtsen
2022-08-02 10:06 ` Philip Kaludercic
2022-08-02 10:11 ` Lars Ingebrigtsen
2022-08-02 10:00 ` Lars Ingebrigtsen
2022-08-02 10:11 ` Philip Kaludercic
2022-08-02 10:46 ` Lars Ingebrigtsen
2022-08-02 10:14 ` Augusto Stoffel
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=87mtcr99mx.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=emacs-devel@gnu.org \
--cc=philip.kaludercic@fau.de \
/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).