From: "João Távora" <joaotavora@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Philip Kaludercic <philipk@posteo.net>,
Stefan Monnier <monnier@iro.umontreal.ca>,
emacs-devel <emacs-devel@gnu.org>
Subject: Re: Proposal: Forwards-Compatibility Library for Emacs
Date: Tue, 21 Sep 2021 23:34:55 +0100 [thread overview]
Message-ID: <CALDnm52F_T75Hu0CgFjw8dDytD2ouXfaLOi9UnvvykL3=jtt4A@mail.gmail.com> (raw)
In-Reply-To: <87lf3pwopa.fsf@gnus.org>
On Tue, Sep 21, 2021 at 11:26 PM Lars Ingebrigtsen <larsi@gnus.org> wrote:
>
> João Távora <joaotavora@gmail.com> writes:
>
> >> (And we certainly don't want to take on the maintenance burden of
> >> writing subr-x in such a way that it's backwards-compatible.)
> >
> > Then the same problem will happen when you copy these functions
> > into compat.el. Unless you do what Stefan says, and rename them.
>
> No, the same problem doesn't exist in compat.el. Philip's package
> doesn't redefine functions in that way.
I see (I think). Then the :core packages using the subr-x functions
must deal with slightly different specifications (if the 25.1 version indeed
isn't the same as the 28.1 version). You called this bug-compatibility a while
ago. So is this a lesser-of-two-evils situation? Is it better to break the ELPA
usage this way then to break the libraries in core Emacs 25.1 as in your
example?
And which functions are we talking about again? Or were you just
speculating about possibilities?
João
next prev parent reply other threads:[~2021-09-21 22:34 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-20 23:35 Proposal: Forwards-Compatibility Library for Emacs Philip Kaludercic
2021-09-21 0:30 ` Adam Porter
2021-09-21 4:10 ` Lars Ingebrigtsen
2021-09-21 8:28 ` Philip Kaludercic
2021-09-21 12:31 ` Stefan Monnier
2021-09-21 12:40 ` Eli Zaretskii
2021-09-21 12:50 ` Stefan Kangas
2021-09-21 13:38 ` Arthur Miller
2021-09-21 13:49 ` João Távora
2021-09-21 13:00 ` Philip Kaludercic
2021-09-21 13:12 ` Eli Zaretskii
2021-09-21 13:28 ` Philip Kaludercic
2021-09-21 13:24 ` João Távora
2021-09-21 13:29 ` Philip Kaludercic
2021-09-21 13:50 ` João Távora
2021-09-21 14:59 ` Lars Ingebrigtsen
2021-09-21 12:58 ` Philip Kaludercic
2021-09-21 13:37 ` Arthur Miller
2021-09-21 13:54 ` Philip Kaludercic
2021-09-21 14:18 ` Arthur Miller
2021-09-21 15:02 ` Lars Ingebrigtsen
2021-09-21 15:40 ` João Távora
2021-09-21 16:10 ` Philip Kaludercic
2021-09-21 16:22 ` João Távora
2021-09-21 17:22 ` Lars Ingebrigtsen
2021-09-21 17:29 ` João Távora
2021-09-21 19:24 ` Stefan Monnier
2021-09-21 21:06 ` Philip Kaludercic
2021-09-21 21:50 ` Stefan Monnier
2021-09-22 6:48 ` Philip Kaludercic
2021-09-22 17:53 ` Stefan Monnier
2021-09-22 18:54 ` Philip Kaludercic
2021-09-22 19:15 ` Stefan Monnier
2021-09-21 21:57 ` Lars Ingebrigtsen
2021-09-21 22:08 ` João Távora
2021-09-21 22:16 ` Lars Ingebrigtsen
2021-09-21 22:24 ` João Távora
2021-09-21 22:25 ` Lars Ingebrigtsen
2021-09-21 22:34 ` João Távora [this message]
2021-09-22 6:53 ` Philip Kaludercic
2021-09-22 7:12 ` João Távora
2021-09-22 7:14 ` Arthur Miller
2021-09-21 13:05 ` Philip Kaludercic
2021-09-21 13:27 ` Arthur Miller
2021-09-21 13:45 ` Philip Kaludercic
2021-09-21 14:05 ` Arthur Miller
2021-09-21 22:17 ` Richard Stallman
2021-09-21 22:24 ` Lars Ingebrigtsen
2021-09-22 9:54 ` Philip Kaludercic
2021-10-04 23:00 ` [ELPA] Add compat.el Philip Kaludercic
2021-10-07 7:03 ` Old (static) builds of Emacs Philip Kaludercic
2021-10-07 7:48 ` Michael Albinus
2021-10-07 7:56 ` Philip Kaludercic
2021-10-07 12:49 ` Stefan Monnier
2021-10-07 20:29 ` Philip Kaludercic
2021-10-07 21:21 ` Stefan Monnier
2021-11-30 21:21 ` Philip Kaludercic
2021-12-01 13:15 ` Stefan Monnier
2021-10-07 20:49 ` [ELPA] Add compat.el Philip Kaludercic
2021-10-08 5:56 ` Eli Zaretskii
2021-10-08 9:59 ` Philip Kaludercic
2021-10-08 11:10 ` Eli Zaretskii
2021-10-08 11:35 ` Philip Kaludercic
2021-10-08 7:45 ` Mattias Engdegård
2021-10-08 10:00 ` Philip Kaludercic
2021-10-15 19:08 ` Philip Kaludercic
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='CALDnm52F_T75Hu0CgFjw8dDytD2ouXfaLOi9UnvvykL3=jtt4A@mail.gmail.com' \
--to=joaotavora@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
--cc=philipk@posteo.net \
/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).