From: Rob Browning <rlb@defaultvalue.org>
To: Carl Worth <cworth@cworth.org>
Cc: notmuch@notmuchmail.org
Subject: Re: Folder-based searching
Date: Mon, 17 Jan 2011 12:48:11 -0600 [thread overview]
Message-ID: <87oc7fe590.fsf@raven.defaultvalue.org> (raw)
In-Reply-To: <87tyh9wzs2.fsf@yoom.home.cworth.org> (Carl Worth's message of "Sat, 15 Jan 2011 14:46:53 -0800")
Carl Worth <cworth@cworth.org> writes:
> Someone bringing in mail from such a system might want to migrate from
> information in directory names to instead be information in notmuch
> tags. That might look something like this:
>
> notmuch tag +important folder:important
Nice. So what are the path semantics? For example, is the path case
sensitive or insensitive? Can you say folder:foo/bar, and if so, is the
path rooted, or can it match path sub-segments?
i.e. which of these, if any, is "folder:foo/bar" like?
(.*/)?foo/bar(/.*)?
^foo/bar$
^foo/bar(/.*)?
Thanks
--
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
next prev parent reply other threads:[~2011-01-17 18:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-15 22:46 Folder-based searching Carl Worth
2011-01-17 6:17 ` Xavier Maillard
2011-01-17 12:43 ` Sebastian Spaeth
2011-01-17 13:00 ` Sebastian Spaeth
2011-03-12 23:44 ` [PATCH] test: "search-by-folder" single-word search terms should be updated correctly when directories are renamed Pieter Praet
2011-05-12 13:22 ` Pieter Praet
2011-05-12 16:04 ` Jameson Graef Rollins
2011-05-13 8:06 ` [PATCH] test: do folder-based search with a single-term path after moving message Pieter Praet
2011-01-17 18:48 ` Rob Browning [this message]
2011-01-18 19:09 ` Folder-based searching Carl Worth
2011-01-18 19:54 ` Rob Browning
2011-01-18 20:16 ` Carl Worth
2011-01-19 7:29 ` Austin Clements
-- strict thread matches above, loose matches on Subject: below --
2011-01-21 10:45 mazieres-6kd3dvy8f9kx6dc7vcsytfvnai
2011-01-21 16:59 ` Carl Worth
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=87oc7fe590.fsf@raven.defaultvalue.org \
--to=rlb@defaultvalue.org \
--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).