From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Daniel Mendler <mail@daniel-mendler.de>
Cc: Philip Kaludercic <philipk@posteo.net>,
Stefan Kangas <stefankangas@gmail.com>,
60990-done@debbugs.gnu.org
Subject: bug#60990: 29.0.60; New seq release 2.24
Date: Mon, 04 Sep 2023 18:20:50 -0400 [thread overview]
Message-ID: <jwvedjdmvj9.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <77c2030d-c8cf-6695-6568-feb23521860f@daniel-mendler.de> (Daniel Mendler's message of "Mon, 4 Sep 2023 23:12:08 +0200")
> What do you see as '"the usual" solutions'?
The solutions used when changes are made in `minibuffer.el`,
`simple.el`, `subr.el`, ...
E.g. using `fboundp`, testing `emacs-major-version`, ...
> To be concrete, if new seq-* functions are added in Emacs 30 do you
> consider it a viable solution if we add backports to Compat or not?
Can't see why not, yes (but I'm not sufficiently familiar with `compat`
to know if there might be some subtle issues).
Stefan
next prev parent reply other threads:[~2023-09-04 22:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-21 14:51 bug#60990: 29.0.60; New seq release 2.24 Daniel Mendler
2023-09-04 15:32 ` Stefan Kangas
2023-09-04 16:16 ` Daniel Mendler
2023-09-04 17:05 ` Stefan Kangas
2023-09-04 17:32 ` Daniel Mendler
2023-09-04 18:35 ` Stefan Kangas
2023-09-04 19:23 ` Daniel Mendler
2023-09-04 20:11 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-04 20:35 ` Stefan Kangas
2023-09-04 21:12 ` Daniel Mendler
2023-09-04 22:20 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-09-05 7:44 ` Daniel Mendler
2023-09-09 8:15 ` Daniel Mendler
2023-09-09 12:28 ` Stefan Kangas
2023-09-09 13:42 ` Daniel Mendler
2023-09-09 21:57 ` Stefan Kangas
2023-09-09 15:47 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-09 16:07 ` Daniel Mendler
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=jwvedjdmvj9.fsf-monnier+emacs@gnu.org \
--to=bug-gnu-emacs@gnu.org \
--cc=60990-done@debbugs.gnu.org \
--cc=mail@daniel-mendler.de \
--cc=monnier@iro.umontreal.ca \
--cc=philipk@posteo.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).