From: Mark Anderson <MarkR.Anderson@amd.com>
To: Austin Clements <amdragon@mit.edu>,
Andrei Popescu <andreimpopescu@gmail.com>
Cc: "notmuch@notmuchmail.org" <notmuch@notmuchmail.org>
Subject: Re: Improving notmuch query documentation [was: Re: Partial words on notmuch search?]
Date: Fri, 20 Jan 2012 12:08:30 -0700 [thread overview]
Message-ID: <3wd62g6mbtd.fsf@testarossa.amd.com> (raw)
In-Reply-To: <20120117222923.GU16740@mit.edu>
On Tue, 17 Jan 2012 16:29:23 -0600, Austin Clements <amdragon@MIT.EDU> wrote:
> Quoth Andrei Popescu on Jan 18 at 12:14 am:
> > On Lu, 16 ian 12, 21:34:31, Austin Clements wrote:
> > > Quoth Andrei Popescu on Jan 16 at 10:21 pm:
> > > > Where can I read more about this? (except the source :)
> > >
> > > Most of this is in the Xapian query syntax document you found. Really
> > > we ought to beef-up Notmuch's query syntax documentation.
> >
> > If I get around to write something myself where do you suggest I should
> > start, the wiki or the manpage?
>
> Probably expanding man/man7/notmuch-search-terms.7 would be the way to
> go.
I would appreciate it if the limitations of id: search were explained
there too. I have some rules that I would love to make based on pattern
matching the message-id of the message, because I have a tool that
generates scads of email and I want to be able to delete a lot of it.
I think that id: is only matchable as an entire string, and a
confirmation of that would be nice to see.
For those who cringe when hearing the mention of _deletion_ of emails,
do you have a suggestion for how many copies of bugs in the bug database
I should store in my mail repository? Note that IT only gives me a
couple gigabytes of home directory storage, and I don't have an SSD
Linux laptop, so the index does eventually slow down.
In other words, there are plenty of emails I love to forget ever having
received. :)
-Mark
next prev parent reply other threads:[~2012-01-20 19:08 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-15 22:06 Partial words on notmuch search? Andrei Popescu
2012-01-16 1:07 ` mailinglists
2012-01-16 20:21 ` Andrei Popescu
2012-01-16 22:26 ` David Bremner
2012-01-16 22:38 ` Andrei Popescu
2012-01-17 2:34 ` Austin Clements
2012-01-17 17:43 ` Jani Nikula
2012-01-17 19:47 ` Austin Clements
2012-01-17 22:14 ` Improving notmuch query documentation [was: Re: Partial words on notmuch search?] Andrei Popescu
2012-01-17 22:29 ` Austin Clements
2012-01-20 19:08 ` Mark Anderson [this message]
2012-03-15 21:15 ` Austin Clements
2012-03-15 9:39 ` [RFC] http://notmuchmail.org/searching/ [was: Re: Improving notmuch query documentation] Andrei POPESCU
2012-03-15 21:11 ` Austin Clements
2012-03-16 0:30 ` Andrei POPESCU
2012-03-16 2:11 ` Austin Clements
2012-03-16 22:29 ` Andrei POPESCU
2012-03-16 23:51 ` David Bremner
2012-03-17 0:20 ` Austin Clements
2012-03-17 14:40 ` Andrei POPESCU
2012-03-17 17:16 ` Austin Clements
2012-03-17 19:59 ` Andrei POPESCU
2012-03-16 16:52 ` 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=3wd62g6mbtd.fsf@testarossa.amd.com \
--to=markr.anderson@amd.com \
--cc=amdragon@mit.edu \
--cc=andreimpopescu@gmail.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).