From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id 95FCE4196F0 for ; Thu, 8 Apr 2010 14:28:28 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: -2.89 X-Spam-Level: X-Spam-Status: No, score=-2.89 tagged_above=-999 required=5 tests=[ALL_TRUSTED=-1, BAYES_00=-1.9, T_MIME_NO_TEXT=0.01] autolearn=ham Received: from olra.theworths.org ([127.0.0.1]) by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HBLjLF7FhhlJ; Thu, 8 Apr 2010 14:28:27 -0700 (PDT) Received: from yoom.home.cworth.org (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id 7B441431FC1; Thu, 8 Apr 2010 14:28:27 -0700 (PDT) Received: by yoom.home.cworth.org (Postfix, from userid 1000) id 0586C558038; Thu, 8 Apr 2010 14:28:27 -0700 (PDT) From: Carl Worth To: Dirk Hohndel , Jameson Rollins , notmuch@notmuchmail.org Subject: Re: Plans for the 0.2 release (this week) In-Reply-To: References: <8739z6rjxf.fsf@yoom.home.cworth.org> <87tyrmavoc.fsf@servo.finestructure.net> Date: Thu, 08 Apr 2010 14:28:20 -0700 Message-ID: <87ochtd47f.fsf@yoom.home.cworth.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Apr 2010 21:28:28 -0000 --=-=-= Content-Transfer-Encoding: quoted-printable On Thu, 08 Apr 2010 07:58:47 -0700, Dirk Hohndel wr= ote: > On Thu, 08 Apr 2010 10:03:15 -0400, Jameson Rollins 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. >=20 > 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?=20 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. =2DCarl --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iD8DBQFLvkp06JDdNq8qSWgRAjhqAJ9kFvvV47mxEQaGkjO5R52Xhwy/1gCgpVOy O3KVd9EAIqBU7L1TEsJgvt4= =B6vt -----END PGP SIGNATURE----- --=-=-=--