unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Keith Amidon <camalot@picnicpark.org>
To: notmuch@notmuchmail.org
Subject: Multiple header sources for an index.header query prefix?
Date: Wed, 4 Aug 2021 07:56:37 -0700	[thread overview]
Message-ID: <aa7237e2-3ff3-fab2-8b92-1c752d6df033@picnicpark.org> (raw)

I've been a very happy user of notmuch for a very long time. Thank you 
for such a great tool!

Recently I've been working on implementing a new workflow for handling 
email which uses automated tagging much more heavily. In doing so, I 
want to use some custom header indexes to construct some of the searches 
and it seems like it would be very convenient to be able to index 
multiple custom headers under the same query prefix. For example, I'd 
like to be able to index both X-spam and X-Spam-Result under the query 
prefix "Spam:".

I tried just adding two custom header lines to the config file with the 
same query prefix, like:

[index]
header.Spam=X-Spam
header.Spam=X-Spam-Result

It appeared that after reindexing, notmuch just used the final line with 
the same query prefix. In addition, the python bindings config parser 
fails on such a configuration with an error that the header value is 
already in use. Checking the code, it this behavior seems consistent.

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

Does this seem a reasonable way to go? Is this an extension of the 
custom header indexing behavior that you would be interested in? 
Finally, any suggestions for approaching an implementation? In 
particular, I believe there were some recent changes to also store the 
configuration in the database. Any thoughts on how this suggestion would 
interact with that?

Thanks for your help!

Regards, Keith

             reply	other threads:[~2021-08-04 15:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-04 14:56 Keith Amidon [this message]
2021-08-05 10:44 ` Multiple header sources for an index.header query prefix? David Bremner
2021-08-15 19:01   ` Keith Amidon
2021-08-15 19:27     ` David Bremner
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=aa7237e2-3ff3-fab2-8b92-1c752d6df033@picnicpark.org \
    --to=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).