From: David Bremner <david@tethera.net>
To: Gaute Hope <eg@gaute.vetsj.com>,
Austin Clements <aclements@csail.mit.edu>
Cc: notmuch <notmuch@notmuchmail.org>
Subject: Re: [PATCH] WIP: regexp matching in 'subject' and 'from'
Date: Sat, 11 Jun 2016 13:49:39 -0300 [thread overview]
Message-ID: <87fusjvffg.fsf@zancas.localnet> (raw)
In-Reply-To: <1465662533-astroid-3-6vuqm3zu54-1296@strange>
Gaute Hope <eg@gaute.vetsj.com> writes:
>
> Maybe we could check if the search string contains a regexp and decide
> whether to pre-process it on the background of that? I think that would
> make the interface more user-friendly. You'd just always use search
> whether you decide that you need to put in some regexp or not.
>
There are some technical limitations of the xapian query parser (and
field processors in particular) that mean we'll probably have explicitly
ask for regex expansion.
> I would rather have double the db and be able wildcard beginning of
> terms. If it is not too much maintaining overhead it might be made
> optional?
perhaps. If that's really your primary goal, regexp search is
overkill. Maybe you should discuss with xapian upstream the possibility
of having xapian support more general wildcards. I have a vague memory
of olly once saying it was not out of the question. But I might be wrong
about that, it's just a half-remembered IRC discussion.
d
next prev parent reply other threads:[~2016-06-11 16:49 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-06 6:58 searching: '*analysis' vs 'reanalysis' Gaute Hope
2016-06-06 12:42 ` David Bremner
2016-06-06 12:53 ` Gaute Hope
2016-06-06 15:52 ` Sebastian Fischmeister
2016-06-06 17:29 ` David Bremner
2016-06-06 19:20 ` Austin Clements
2016-06-06 20:08 ` Gaute Hope
2016-06-06 20:22 ` Austin Clements
2016-06-07 2:05 ` [PATCH] WIP: regexp matching in subjects David Bremner
2016-06-07 10:16 ` David Bremner
2016-06-10 2:28 ` [PATCH] WIP: regexp matching in 'subject' and 'from' David Bremner
2016-06-10 2:42 ` David Bremner
2016-06-10 11:11 ` Tomi Ollila
2016-06-10 11:50 ` David Bremner
2016-06-10 8:38 ` Gaute Hope
2016-06-10 11:09 ` David Bremner
2016-06-11 16:32 ` Gaute Hope
2016-06-11 16:49 ` David Bremner [this message]
2016-06-11 17:09 ` Tomi Ollila
2016-06-11 17:34 ` Gaute Hope
2016-06-11 1:49 ` 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=87fusjvffg.fsf@zancas.localnet \
--to=david@tethera.net \
--cc=aclements@csail.mit.edu \
--cc=eg@gaute.vetsj.com \
--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).