From: Carl Worth <cworth@cworth.org>
To: Michal Vyskocil <mvyskocil@suse.cz>, notmuch@notmuchmail.org
Subject: Re: Search using email headers does not work
Date: Tue, 12 Feb 2013 11:57:43 -0800 [thread overview]
Message-ID: <87wqudi9u0.fsf@yoom.home.cworth.org> (raw)
In-Reply-To: <20130212173216.GL7346@zelvantb.site>
[-- Attachment #1: Type: text/plain, Size: 1109 bytes --]
Michal Vyskocil <mvyskocil@suse.cz> writes:
> I like such idea - but how hard would be to add a config options to
> extend a list of default headers used for indexing?
Not hard.
Obviously, notmuch is already indexing some headers, (From, Date, To,
Subject), and it wouldn't be hard to index more. [*]
List-Id has been proposed often enough that it should probably be on by
default.
Then, there are other, slightly more special-case headers, (like headers
added by spam filtering software), that probably would be best added on
an opt-in basis based on a configuration option.
-Carl
[*] The existing set of indexed headers is really just historical
accident based on two things:
1. I was originally writing index code to match sup's index building, so
I focused on the headers sup indexed.
2. I wrote code to index enough headers to satisfy my use case.
It's embarrassing to me that I added this note to the notmuch TODO file
in October 2009 (and it's still there):
Add support for the user to specify custom headers to be indexed.
--
carl.d.worth@intel.com
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2013-02-12 19:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-11 14:52 Search using email headers does not work Michal Vyskocil
2013-02-12 11:50 ` David Bremner
2013-02-12 17:03 ` Jameson Graef Rollins
2013-02-12 17:32 ` Michal Vyskocil
2013-02-12 19:57 ` Carl Worth [this message]
2013-02-12 20:05 ` David Bremner
2013-02-13 7:55 ` Mark Walters
2013-02-13 21:09 ` Jameson Graef Rollins
2013-02-13 21:20 ` Alexey Feldgendler
2013-02-15 8:27 ` Tomi Ollila
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=87wqudi9u0.fsf@yoom.home.cworth.org \
--to=cworth@cworth.org \
--cc=mvyskocil@suse.cz \
--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).