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 5A62B431FC1 for ; Mon, 7 Jun 2010 06:50:05 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: -1.89 X-Spam-Level: X-Spam-Status: No, score=-1.89 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, T_MIME_NO_TEXT=0.01] autolearn=unavailable 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 1rim9Vkrftt7 for ; Mon, 7 Jun 2010 06:49:50 -0700 (PDT) Received: from mail-ww0-f53.google.com (mail-ww0-f53.google.com [74.125.82.53]) by olra.theworths.org (Postfix) with ESMTP id 59A084196F0 for ; Mon, 7 Jun 2010 06:49:50 -0700 (PDT) Received: by wwb39 with SMTP id 39so2002306wwb.26 for ; Mon, 07 Jun 2010 06:49:48 -0700 (PDT) Received: by 10.227.154.147 with SMTP id o19mr14248615wbw.112.1275918587703; Mon, 07 Jun 2010 06:49:47 -0700 (PDT) Received: from ut.hh.sledj.net (gmp-ea-fw-1b.sun.com [192.18.8.1]) by mx.google.com with ESMTPS id u36sm37999870wbv.0.2010.06.07.06.49.24 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 07 Jun 2010 06:49:45 -0700 (PDT) Received: by ut.hh.sledj.net (Postfix, from userid 1000) id E97C6594015; Mon, 7 Jun 2010 14:49:26 +0100 (BST) To: Carl Worth , Keith Packard , notmuch@notmuchmail.org Subject: Re: [PATCH] Customize saved search order separately from regular search order In-Reply-To: <87d3w7eicf.fsf@yoom.home.cworth.org> References: <1272920307-25995-1-git-send-email-keithp@keithp.com> <87d3xcexq9.fsf@ut.hh.sledj.net> <87d3w7eicf.fsf@yoom.home.cworth.org> User-Agent: Notmuch/0.3.1-50-gc535d0a (http://notmuchmail.org) Emacs/23.1.1 (x86_64-pc-linux-gnu) From: David Edmondson Date: Mon, 07 Jun 2010 14:49:23 +0100 Message-ID: <87ocfnt0kc.fsf@ut.hh.sledj.net> 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: Mon, 07 Jun 2010 13:50:05 -0000 --=-=-= Content-Transfer-Encoding: quoted-printable On Thu, 03 Jun 2010 17:45:20 -0700, Carl Worth wrote: > So I think what we actually want here is an additional member for our > saved-search tuple which indicates the desired search order for that > particular search. That's the only way I see to support a single user > who wants to take advantage of both kinds of searches. That seems straightforward to implement in the code and only slightly complicated in the customisation interface (though I haven't done it yet). > A separated, but perhaps related idea would be to explicitly support the > notion of one search being a subset of another. I have an "inbox" search > (tag:inbox) and several searches that are subsets, ("notmuch" is > "tag:notmuch and tag:inbox"). If this were setup as an actual hierarchy > it might have two advantages: >=20 > 1. It would be a bit simpler to specify all of theses searches, > I wouldn't have to keep repeating "and tag:inbox" in each. > This would be particularly important if I changed the > criteria for the top-level search. >=20 > 2. If the various levels of the hierarchy were displayed > separately it would be easier for me to focus on processing > all of my inbox folders (which happen to be > oldest-first)--archiving each down to 0 messages, without > being distracted by several (newest-first) saved searches > that will only ever grow and don't have any > processing/archiving associated with them. Writing code to manipulate and use a structure like this would obviously be some effort, but it doesn't seem overly difficult. More challenging would be the interface to allow the user to customise the structure to express their intentions. Do you have any thoughts on that? dme. =2D-=20 David Edmondson, http://dme.org --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkwM+OMACgkQaezQq/BJZRZgIACdHnrFFyvcrK1oVRpHqlNiU6sP 0DMAniy9r59CjNaMf4nP9IkES3ehLMdY =xHhJ -----END PGP SIGNATURE----- --=-=-=--