From: Carl Worth <cworth@cworth.org>
To: Dirk Hohndel <hohndel@infradead.org>,
Jameson Rollins <jrollins@finestructure.net>,
notmuch@notmuchmail.org
Subject: Re: Plans for the 0.2 release (this week)
Date: Thu, 08 Apr 2010 14:28:20 -0700 [thread overview]
Message-ID: <87ochtd47f.fsf@yoom.home.cworth.org> (raw)
In-Reply-To: <m3tyrmgfdk.fsf@x200.gr8dns.org>
[-- Attachment #1: Type: text/plain, Size: 3883 bytes --]
On Thu, 08 Apr 2010 07:58:47 -0700, Dirk Hohndel <hohndel@infradead.org> wrote:
> On Thu, 08 Apr 2010 10:03:15 -0400, Jameson Rollins <jrollins@finestructure.net> wrote:
> > Also, fwiw, the folder: indexing is probably the new feature that I'm
> > most eagerly awaiting. I've got all these ideas for ways to handle sent
> > mail and drafts if we can get this working.
>
> Maybe I am missing some context here - what exactly does 'indexing' mean
> here?
Indexing here means shoving information into the database to make it
searchable.
I was a bit vague in my description of the features I want to enable
here. So let me start making it a bit more clear. I'd like to add
support for the following:
1. A "folder:" prefix in the search syntax that will match components
of the directory in which mail files are stored. So, if you've got
mail filed into directories, (from using a folder-based email
program, or from doing an imap sync from gmail that turns tags into
directories), then you could search for things like "folder:spam",
"folder:important", "folder:arbitrary/subset/of/some/path", etc.
2. A "list:" prefix to match content from headers that identify
mailing list. My perception is that there are likely a handful of
different headers that have been used, and they should all be
indexed so that "list:" will search any of them.
3. Some prefix that can be used to match typical headers added by
spam-filtering software, (maybe this would be a general
prefix---see below).
I think the above are probably the three I can think of that pretty much
everybody has asked for, so that should be indexed by default.
Beyond that, I'd like to be able to provide support for arbitrary
headers in the email. I had envisioned allowing the user to configure
specific headers to index. Alternately, I had imagined having a
blacklist of "uninteresting" headers and indexing everything
else. (Though, now Dirk is very interested in Received and its perhaps
provides the most content of any of the headers I originally thought
would be "uninteresting".)
One experiment I should do is to measure how much my database would grow
if I were to index all of the header content. I don't really know what
kind of a percentage we're talking about.
Finally, we'd need a syntax for searching all of these headers. Rather
than trying to map each header name to a custom prefix, I think what
might be best would be a general thing that could look like:
header:"X-Spam-Flag: YES"
We don't currently have the ability to tie a search to the beginning of
a line, but it occurs to me that we could do something fancy like index
each header with a specific term to indicate line beginnings. Then, with
a custom query parser we could use the common symbol of '^' to map to
that. That would enable something like:
header:"^X-Spam-Flag: YES"
That's a lot of work though, (and perhaps not as important as it's
probably uncommon for a header name to appear within the value of some
other header).
> Hmm - haven't even thought about drafts, yet. How would the UI deal with
> those?
I would imagine another "folder" alongside the others that would list
all drafts, and selecting any such message would bring up the message in
a mode to edit it.
Sup also displayed draft messages in their proper location in the
threads containing the message being replied to, (and highlighted such
threads in the search view).
All of that sounds quite easy to do by simply saving the draft within
the mailstore and giving it a "draft" tag.
Finally, many mail interfaces prompt from the "compose new message"
command whether an existing draft should be continued. That's useful to
help the user avoid forgetting to complete and send a draft that was
forgotten.
-Carl
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2010-04-08 21:28 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-07 22:12 Plans for the 0.2 release (this week) Carl Worth
2010-04-07 22:23 ` James Westby
2010-04-08 14:34 ` Mike Kelly
2010-04-12 18:27 ` Mike Kelly
2010-04-08 7:47 ` Sebastian Spaeth
2010-04-08 12:21 ` Anthony Towns
2010-04-13 16:02 ` Carl Worth
2010-04-08 8:13 ` David Edmondson
2010-04-08 14:54 ` Dirk Hohndel
2010-04-08 13:52 ` Jameson Rollins
2010-04-08 14:55 ` Dirk Hohndel
2010-04-13 16:06 ` Carl Worth
2010-04-08 14:03 ` Jameson Rollins
2010-04-08 14:58 ` Dirk Hohndel
2010-04-08 15:21 ` Michal Sojka
2010-04-08 15:57 ` draft handling [was: Re: Plans for the 0.2 release (this week)] Jameson Rollins
2010-04-08 21:28 ` Carl Worth [this message]
2010-04-08 21:38 ` Plans for the 0.2 release (this week) Jameson Rollins
2010-04-09 0:22 ` Mike Kelly
2010-04-08 15:30 ` Mike Kelly
2010-04-09 3:22 ` Anthony Towns
2010-04-09 4:25 ` Michal Sojka
2010-04-09 16:21 ` micah anderson
2010-04-08 14:22 ` Michal Sojka
2010-04-09 4:32 ` Michal Sojka
2010-04-09 7:35 ` Sebastian Spaeth
2010-04-09 17:14 ` Dirk Hohndel
2010-04-10 3:06 ` Carl n∅tmuch 䚳 Worth
2010-04-10 4:44 ` Dirk Hohndel
2010-04-10 4:47 ` Dirk Hohndel
2010-04-10 13:05 ` Jameson Rollins
2010-04-10 14:39 ` Dirk Hohndel
2010-04-10 9:02 ` Michal Sojka
2010-04-10 13:06 ` Jameson Rollins
2010-04-10 13:09 ` Jameson Rollins
2010-04-10 14:06 ` Michael Elkins
2010-04-10 19:58 ` Michal Sojka
2010-04-10 13:52 ` Sebastian Spaeth
2010-04-10 13:56 ` Jameson Rollins
2010-04-10 14:41 ` Dirk Hohndel
2010-04-13 17:20 ` 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=87ochtd47f.fsf@yoom.home.cworth.org \
--to=cworth@cworth.org \
--cc=hohndel@infradead.org \
--cc=jrollins@finestructure.net \
--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).