Date: Fri, 10 Jun 2016 08:38:05 +0000
From: Gaute Hope <eg@gaute.vetsj.com>
Subject: Re: [PATCH] WIP: regexp matching in 'subject' and 'from'
To: David Bremner <david@tethera.net>, Austin Clements
 <aclements@csail.mit.edu>
Cc: sfischme@uwaterloo.ca, notmuch <notmuch@notmuchmail.org>
References: <1465265149-7174-1-git-send-email-david@tethera.net>
 <1465525688-30913-1-git-send-email-david@tethera.net>
In-Reply-To: <1465525688-30913-1-git-send-email-david@tethera.net>
User-Agent: astroid/v0.5-221-g4c2c7173 (https://github.com/gauteh/astroid)
Message-Id: <1465547660-astroid-0-nudmv20lbk-1296@strange>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable
Precedence: list

David Bremner writes on juni 10, 2016 4:28:
> the idea is that you can run
>=20
> % notmuch search subject_re:<your-favourite-regexp>
> % notmuch search from_re:<your-favourite-regexp>'
>=20
> or
>=20
> % notmuch search subject:"your usual phrase search"
> % notmuch search from:"usual phrase search"
>=20
> This should also work with bindings, since it extends the query parser.
>=20
> This is trivial to extend for other value slots, but currently the only
> value slots are date, message_id, from, subject, and last_mod. Date is
> already searchable, and message_id is not obviously useful to regex
> match.
> ---
>=20
> This is more or less complete codewise, it fixes the know problems
> with the last version. Names of prefixes are debatable, and of course
> it needs doc and tests.  I don't see any reason not to do this at the mom=
ent,
> since it's basically free; no new terms are added to the database.

Cool!

Would it break a lot of things if you just replace the original prefix?

Could it be made to work on the message body?

Regards, Gaute

=