From: Philip Kaludercic <philipk@posteo.net>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Augusto Stoffel <arstoffel@gmail.com>,
Andreas Schwab <schwab@linux-m68k.org>,
emacs-devel@gnu.org
Subject: Re: Deprecation of define-key?
Date: Tue, 02 Aug 2022 10:06:22 +0000 [thread overview]
Message-ID: <87mtcnc63l.fsf@posteo.net> (raw)
In-Reply-To: <87sfmf0xrc.fsf@gnus.org> (Lars Ingebrigtsen's message of "Tue, 02 Aug 2022 12:01:59 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Philip Kaludercic <philipk@posteo.net> writes:
>
>> One thing I still don't understand about keymap (which is part of the
>> reason I initiated this thread), is who the "target audience" is, if
>> any? Core development, ELPA packages in general, user configurations,
>> or someone else?
>
> Everybody?
In that case I think keymap.el should be make avalaible on ELPA, so it
can be reasonably used in packages before the year 2030. If there is no
interest or a technical reason against doing so, I would try replicating
the functionality in compat.el, but I haven't looked into what this
would mean in more detail.
next prev parent reply other threads:[~2022-08-02 10:06 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
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 [this message]
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=87mtcnc63l.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=arstoffel@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=schwab@linux-m68k.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).