From: Jani Nikula <jani@nikula.org>
To: Carl Worth <cworth@cworth.org>,
Austin Clements <aclements@csail.mit.edu>,
notmuch@notmuchmail.org
Subject: Re: [PATCH 0/5] lib: make folder: prefix literal
Date: Wed, 29 Jan 2014 21:05:30 +0200 [thread overview]
Message-ID: <874n4mfw1x.fsf@nikula.org> (raw)
In-Reply-To: <874n4rvcvo.fsf@yoom.home.cworth.org>
On Sun, 26 Jan 2014, Carl Worth <cworth@cworth.org> wrote:
> Jani Nikula <jani@nikula.org> writes:
>> Here's a thought. With boolean prefix folder:, we can devise a scheme
>> where the folder: query defines what is to be matched.
>
> I like the idea, but I tried to infer the rules from the examples, and I
> failed. It looks like there are two new symbols, "/" and "/." but I
> couldn't decipher the exact semantics of each.
>
> I think a proposal like this should not re-use the '/' symbol as we
> already have that as a path divider. (See rsync for lots of user
> confusion with a significant trailing '/').
>
> I propose a similar, but slightly different approach, where we add two
> additional symbols:
>
> '^' Matches the beginning of a path
>
> '$' Matches the end of a path
>
> [Obviously, I chose these symbols from regular expressions. I would be
> OK with alternate symbols, ('$' seems like it might be problematic in
> the shell, but perhaps not too much if it's always at the end of a
> phrase.)]
>
> This way, one could search for:
>
> folder:foo Works like "folder:" historically
>
> folder:^full/path$ Works like Jani's proposal
>
> folder:^path/prefix Satisfies Tomi's use case, (as well as anyone
> who doesn't want to have to specify or
> distinguish between "/cur" or "/new".
>
> Any extra '/' at the beginning or end of a search string, (such as
> "folder:^/full/path/$") would not change the semantics.
>
> Further, I think we can implement this with less database bloat by
> leaving "folder" as probabilistic and simply indexing two new terms to
> indicate the beginning of the path and the end of the path.
>
> Finally, we could also extend the scheme to other things like subject:
> to allow for an exact subject search like:
>
> "subject:^lib: make folder: prefix literal$"
>
> It was with an eye toward something like this that I chose to make
> folder: probabilistic in the first place. (I probably would have indexed
> things appropriately in the first place as well, but at the time doing
> the necessary query parsing for '^' and '$' seemed daunting).
Unfortunately, I haven't had the time to experiment with this. But it
bugs me that the probabilistic folder: prefix has stemming and it's case
insensitive. It's possible to work around the stemming with the anchors
you suggest or by quoting, but is there a way to have case sensitive
probabilistic prefixes?
BR,
Jani.
next prev parent reply other threads:[~2014-01-29 19:05 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-09 22:18 [PATCH 0/5] lib: make folder: prefix literal Jani Nikula
2014-01-09 22:18 ` [PATCH 1/5] " Jani Nikula
2014-01-24 21:18 ` Austin Clements
2014-01-09 22:18 ` [PATCH 2/5] test: fix insert folder: searches Jani Nikula
2014-01-24 21:20 ` Austin Clements
2014-01-25 19:32 ` Rob Browning
2014-01-09 22:18 ` [PATCH 3/5] test: fix test for literal folder: search Jani Nikula
2014-01-09 22:18 ` [PATCH 4/5] test: add test database in format version 1 Jani Nikula
2014-01-09 22:18 ` [PATCH 5/5] test: add database upgrade test from " Jani Nikula
2014-01-24 21:17 ` [PATCH 0/5] lib: make folder: prefix literal Austin Clements
2014-01-24 23:21 ` David Bremner
2014-01-25 9:33 ` Jani Nikula
2014-01-25 10:47 ` Tomi Ollila
2014-01-25 11:06 ` Jani Nikula
2014-01-25 11:52 ` Tomi Ollila
2014-01-25 15:38 ` Jani Nikula
2014-01-25 16:58 ` David Bremner
2014-01-25 18:22 ` Jani Nikula
[not found] ` <874n4rvcvo.fsf@yoom.home.cworth.org>
2014-01-29 19:05 ` Jani Nikula [this message]
[not found] ` <87k3dir3ci.fsf@yoom.home.cworth.org>
2014-01-29 20:46 ` Austin Clements
[not found] ` <87bnyuqw60.fsf@yoom.home.cworth.org>
2014-01-30 6:34 ` Jani Nikula
2014-01-30 21:15 ` Mark Walters
2014-01-30 22:02 ` Austin Clements
2014-01-31 19:19 ` Rob Browning
2014-02-04 20:14 ` Austin Clements
2014-02-04 20:17 ` Rob Browning
2014-01-31 19:24 ` Rob Browning
2014-02-01 14:54 ` Jani Nikula
2014-02-04 20:02 ` Austin Clements
2014-02-05 13:12 ` Tomi Ollila
2014-02-05 21:12 ` Tomi Ollila
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=874n4mfw1x.fsf@nikula.org \
--to=jani@nikula.org \
--cc=aclements@csail.mit.edu \
--cc=cworth@cworth.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).