Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes
To: notmuch@notmuchmail.org
Subject: Re: Search using email headers does not work
References: <20130211145259.GF7346@zelvantb.site>
	<87ehgl92e5.fsf@zancas.localnet>
	<877gmdo46y.fsf@servo.finestructure.net>
	<20130212173216.GL7346@zelvantb.site>
	<87wqudi9u0.fsf@yoom.home.cworth.org>
	<87mwv9i9ho.fsf@convex-new.cs.unb.ca> <87ip5wlkbb.fsf@qmul.ac.uk>
	<874nhfncot.fsf@servo.finestructure.net>
Date: Wed, 13 Feb 2013 22:20:34 +0100
MIME-Version: 1.0
Content-Transfer-Encoding: Quoted-Printable
From: "Alexey Feldgendler" <alexey@feldgendler.ru>
Message-ID: <op.wsgqwkri1h6og4@sandwich.feldgendler.ru>
In-Reply-To: <874nhfncot.fsf@servo.finestructure.net>
User-Agent: Opera Mail/12.13 (Linux)
Precedence: list

On Wed, 13 Feb 2013 22:09:22 +0100, Jameson Graef Rollins  =

<jrollins@finestructure.net> wrote:

>> I think I mentioned this on irc sometime ago: would indexing all the
>> headers as a separate free text entry (under headers: for example)
>> satisfy most of this. So then you could search for things like
>> headers:"List-Id: blah" or similar.
>>
>> It is not as nice as individually indexed headers, but it does mean t=
hat
>> all notmuch instances would be the same and the same commands would
>> work, the library interface would be consistent etc.

> I like this idea.  Simple to implement, and covers all needs
> automatically.

It will work for some headers, but not for others. Where a header's valu=
e  =

is a list, there will be no precise way of specifying =E2=80=9Cthe list =
contains  =

X=E2=80=9D. NEAR is only an approximation.


-- =

Alexey Feldgendler <alexey@feldgendler.ru>
[ICQ: 115226275] http://feldgendler.livejournal.com