From: Jose A Ortega Ruiz <jao@gnu.org>
To: Kyle Meyer <kyle@kyleam.com>
Cc: notmuch@notmuchmail.org
Subject: Re: [PATCH v4] emacs: customizable names for search buffers
Date: Sun, 16 Jan 2022 22:25:06 +0000 [thread overview]
Message-ID: <87zgnv1fp9.fsf@gnus.jao.io> (raw)
In-Reply-To: <878rvfmnc2.fsf@kyleam.com>
On Sun, Jan 16 2022, Kyle Meyer wrote:
> Jose A Ortega Ruiz writes:
>
>> yeah, that's what i use and didn't notice my error above. format-spec
>> is much nicer than a plain regexp subs, one can use format specifiers
>> like %3t and many others, but unfortunately seems to have been
>> introduced in emacs 27.
>
> format-spec has been present in Emacs since version 21.1, specifically
> c113de23613 (2000-09-19). (Some parameters have been added since then,
> but you only use FORMAT and SPECIFICATION in your patch.)
>
> Here's a test with Emacs 25, Notmuch's current minimum (if I grep
> correctly):
>
> (emacs-version) ; => "GNU Emacs 25.3.50.1 ..."
> (require 'format-spec)
> (format-spec "%b" '((?b . "fine"))) ; => "fine"
>
> At first I thought you were getting confused by the fact that
> format-spec has been marked as autoloaded only recently, but it looks
> like that was in 0185d76e742 (Fix and extend format-spec (bug#41758),
> 2020-06-18), which will be part of the 28.1 release. So that's not
> consistent with "introduced in emacs 27".
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 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.
Thanks a lot for checking,
jao
--
"The evil that is in the world almost always comes of ignorance, and
good intentions may do as much harm as malevolence if they lack understanding."
- Albert Camus
next prev parent reply other threads:[~2022-01-16 22:25 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 [this message]
2022-01-16 23:06 ` Kyle Meyer
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=87zgnv1fp9.fsf@gnus.jao.io \
--to=jao@gnu.org \
--cc=kyle@kyleam.com \
--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).