unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
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 15:34:37 -0500	[thread overview]
Message-ID: <878rvfmnc2.fsf@kyleam.com> (raw)
In-Reply-To: <87h7a7uuhz.fsf@gnus.jao.io>

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".

  parent reply	other threads:[~2022-01-16 20:42 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 [this message]
2022-01-16 22:25       ` Jose A Ortega Ruiz
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=878rvfmnc2.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).