From: David Bremner <david@tethera.net>
To: Jani Nikula <jani@nikula.org>, notmuch@notmuchmail.org
Subject: Re: [Patch v2] lib: regexp matching in 'subject' and 'from'
Date: Wed, 18 Jan 2017 17:01:29 -0400 [thread overview]
Message-ID: <871sw0f5g6.fsf@rocinante.cs.unb.ca> (raw)
In-Reply-To: <877f5scewx.fsf@nikula.org>
Jani Nikula <jani@nikula.org> writes:
> I played around with this a bit, and it seemed to work. Unsurprisingly,
> getting the quoting right was the hardest part. Even though I know how
> the stuff works under the hood, it took me a while to realize that you
> have to use 're:"subject:<regex with spaces>"' to make it work. (I kept
> trying 're:subject:"<regex with spaces>"'.) I don't know if there's
> anything we could really do about this.
>
I _think_ we could add distinct prefixes at the xapian level for each
regex-prefix. That opens the can of worms of naming them eg re-subject:
and re-from:. I'm not sure about the added complexity, but I think it's
a matter of adding an extra argument to the field processor constructor.
d
next prev parent reply other threads:[~2017-01-18 21:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-27 13:33 [PATCH] lib: regexp matching in 'subject' and 'from' David Bremner
2016-11-14 21:46 ` [Patch v2] " David Bremner
2017-01-18 20:05 ` Jani Nikula
2017-01-18 21:01 ` David Bremner [this message]
2017-01-19 12:16 ` [Patch v3] " David Bremner
2017-01-21 3:27 ` [WIP] " David Bremner
2017-01-21 13:59 ` [Patch v4] " David Bremner
2017-01-25 19:40 ` Tomi Ollila
2017-01-26 2:21 ` David Bremner
2017-01-29 11:23 ` Jani Nikula
2017-02-05 20:16 ` Tomi Ollila
2017-02-05 23:28 ` David Bremner
2017-02-09 3:11 ` David Bremner
2017-02-09 16:15 ` Tomi Ollila
2017-02-10 8:29 ` Mark Walters
2017-02-11 23:25 ` David Bremner
2017-01-29 11:06 ` Jani Nikula
2017-01-19 14:27 ` [Patch v2] " David Bremner
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=871sw0f5g6.fsf@rocinante.cs.unb.ca \
--to=david@tethera.net \
--cc=jani@nikula.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).