From: Daniel Mendler <mail@daniel-mendler.de>
To: Stefan Monnier <monnier@iro.umontreal.ca>
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: Tue, 5 Sep 2023 09:44:51 +0200 [thread overview]
Message-ID: <35c9fd30-9bd2-5196-e5e9-ceaab7855f15@daniel-mendler.de> (raw)
In-Reply-To: <jwvedjdmvj9.fsf-monnier+emacs@gnu.org>
On 9/5/23 00:20, Stefan Monnier wrote:
>> 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`, ...
Okay, thanks! Makes sense. The goal of Compat is to reduce such feature
checks in packages, but if Compat is not used, fboundp is the way to go.
Daniel
next prev parent reply other threads:[~2023-09-05 7:44 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
2023-09-05 7:44 ` Daniel Mendler [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=35c9fd30-9bd2-5196-e5e9-ceaab7855f15@daniel-mendler.de \
--to=mail@daniel-mendler.de \
--cc=60990-done@debbugs.gnu.org \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.