From: Kyle Meyer <kyle@kyleam.com>
To: Jose A Ortega Ruiz <jao@gnu.org>
Cc: notmuch@notmuchmail.org
Subject: Re: [PATCH v4] emacs: customizable names for search buffers
Date: Sun, 16 Jan 2022 18:06:37 -0500 [thread overview]
Message-ID: <875yqjmgaq.fsf@kyleam.com> (raw)
In-Reply-To: <87zgnv1fp9.fsf@gnus.jao.io>
Jose A Ortega Ruiz writes:
> In very recent emacs (i'm using its master branch, actually), if one M-x
> describe-function RET format-spec one sees in the help buffer:
>
> Probably introduced at or before Emacs version 27.1.
>
> that's where my misconception came from.
I see. If I recall correctly, that help string is generated by
searching NEWS* files for the name of interest. While that often works
okay, in this case format-spec is first mentioned in the NEWS for 27.1:
$ git describe
emacs-28.0.91-28-ge4886018496
$ git grep -c format-spec -- 'etc/NEWS*'
etc/NEWS:5
etc/NEWS.27:1
> I guess that's potentially good news: i don't see an emacs version
> specified in notmuch's package: is it supposed to be compatible with
> emacs < 25.3? If not, we can just forget about the regexp branch.
Here's the last statement about the minimum Emacs version I see in
Notmuch's NEWS (for v0.31):
The minimum supported major version of GNU Emacs is now 25.1.
The example in my last message used 25.3 because that's the closest
version to 25.1 for which I had a local working tree checked out and
built. But, as I mentioned, format-spec has been present since Emacs
21.1.
next prev parent reply other threads:[~2022-01-16 23:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-10 18:16 [PATCH v4] emacs: customizable names for search buffers jao
2022-01-13 6:05 ` Tomi Ollila
2022-01-13 22:43 ` Jose A Ortega Ruiz
2022-01-14 0:57 ` Jose A Ortega Ruiz
2022-01-16 19:42 ` Tomi Ollila
2022-01-16 20:40 ` Jose A Ortega Ruiz
2022-01-16 20:34 ` Kyle Meyer
2022-01-16 22:25 ` Jose A Ortega Ruiz
2022-01-16 23:06 ` Kyle Meyer [this message]
2022-01-16 23:51 ` Jose A Ortega Ruiz
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://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=875yqjmgaq.fsf@kyleam.com \
--to=kyle@kyleam.com \
--cc=jao@gnu.org \
--cc=notmuch@notmuchmail.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://yhetil.org/notmuch.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).