From: Carl Worth <cworth@cworth.org>
To: Michal Vyskocil <mvyskocil@suse.cz>, notmuch@notmuchmail.org
Subject: Re: Search using email headers does not work
In-Reply-To: <20130212173216.GL7346@zelvantb.site>
References: <20130211145259.GF7346@zelvantb.site>
	<87ehgl92e5.fsf@zancas.localnet>
	<877gmdo46y.fsf@servo.finestructure.net>
	<20130212173216.GL7346@zelvantb.site>
User-Agent: Notmuch/0.13.1 (http://notmuchmail.org) Emacs/23.4.1
	(x86_64-pc-linux-gnu)
Date: Tue, 12 Feb 2013 11:57:43 -0800
Message-ID: <87wqudi9u0.fsf@yoom.home.cworth.org>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-=";
	micalg=pgp-sha1; protocol="application/pgp-signature"
Precedence: list

--=-=-=
Content-Transfer-Encoding: quoted-printable

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.

=2DCarl

[*] 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.

=2D-=20
carl.d.worth@intel.com

--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlEanrcACgkQ6JDdNq8qSWgxnACfVeUYMhYylc5DbEZa/ZadveV6
s/UAmgOvUQ8C01WbW7v4RArXk6IBM+iw
=5Yoe
-----END PGP SIGNATURE-----
--=-=-=--