unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: David Bremner <david@tethera.net>
To: Keith Amidon <camalot@picnicpark.org>, notmuch@notmuchmail.org
Subject: Re: Multiple header sources for an index.header query prefix?
Date: Sun, 15 Aug 2021 12:27:24 -0700	[thread overview]
Message-ID: <87czqe8q5f.fsf@tethera.net> (raw)
In-Reply-To: <4607c340-60f7-cfa4-2a97-3d13cb6bdb59@picnicpark.org>

Keith Amidon <camalot@picnicpark.org> writes:

>>> I started thinking about how I would add this feature and was thinking
>>> it might be better to support in the configuration by using semi-colon
>>> separated values like some of the other config options. For example:
>>>
>>> [index]
>>> header.Spam=X-Spam;X-Spam-Result
> Thanks for the encouragement and suggestions. The time it has taken me 
> to respond to this thread is a fairly accurate indication of the amount 
> of time I have to work on this right now, but it is something that I'd 
> definitely would find useful so I'll plug away on it when I can make 
> time and update the list when I hopefully get something working.
>

I should repeat my advertising for the (in-progress) s-expression query
parser [1], which would allow defining macros to group various user
defined headers. So assuming headers XSpam and XSpamResult are defined,

$ notmuch config set squery.Spam '(macro (term) (or (XSpam term) (XSpamResult term)))'
$ notmuch search --query=sexp '(Spam "foo bar baz")'

If that seems workable for you, you could just wait ;).

d

[1] id:20210812170728.1348333-2-david@tethera.net

  reply	other threads:[~2021-08-15 19:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-04 14:56 Multiple header sources for an index.header query prefix? Keith Amidon
2021-08-05 10:44 ` David Bremner
2021-08-15 19:01   ` Keith Amidon
2021-08-15 19:27     ` David Bremner [this message]
2021-08-16 15:20       ` Keith Amidon

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=87czqe8q5f.fsf@tethera.net \
    --to=david@tethera.net \
    --cc=camalot@picnicpark.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).