Return-Path: X-Original-To: notmuch@notmuchmail.org Delivered-To: notmuch@notmuchmail.org Received: from localhost (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id 15BE840DDF5 for ; Fri, 12 Nov 2010 08:58:40 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: 3.459 X-Spam-Level: *** X-Spam-Status: No, score=3.459 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FH_HOST_IN_ADDRARPA=2.157, RCVD_IN_RP_RNBL=1.31, RDNS_DYNAMIC=0.982, TO_NO_BRKTS_DYNIP=1, T_MIME_NO_TEXT=0.01] autolearn=no 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 3iHCnz9LnbsK for ; Fri, 12 Nov 2010 08:58:29 -0800 (PST) Received: from silentio.fernseed.info (202.4.169.217.in-addr.arpa [217.169.4.202]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by olra.theworths.org (Postfix) with ESMTPS id 945F940DBC1 for ; Fri, 12 Nov 2010 08:58:05 -0800 (PST) Received: from localhost (bookbinder.fernseed.info [IPv6:2001:8b0:ff94:1:224:2cff:fe37:838b]) (Authenticated sender: darren) by silentio.fernseed.info (Postfix) with ESMTPSA id 9F8A9198; Fri, 12 Nov 2010 16:58:03 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=fernseed.info; s=default; t=1289581083; bh=hHHUbLwq6AW/e0BsOAGj/dfNNDHUAzKrqaTnZAp9XEE=; h=From:To:Subject:In-Reply-To:References:Date:Message-ID: MIME-Version:Content-Type; b=dv8xLGlG2ghWtrI0jBx8kCRGx26fwEorhEoBxTbhT+TXLddS6RlWPGJORQEjnOuo+ SjPauMT2BglCiajpD29YJ9Dj+WzsKGzscNSEcnAdMUwua2QJJofBZ2wPqfSyHwCbnI yHmwKWaD5Ygc75Yw0D/E54QXPn1gW3NGm7mKvQ8g= From: Darren McGuicken To: Matthieu Lemerre , notmuch@notmuchmail.org Subject: Re: [PATCH] How to improve the mail handling workflow? In-Reply-To: <87d3qa5wl1.fsf@free.fr> References: <87fwv65zw1.fsf@free.fr> <87sjz6ft52.fsf@bookbinder.fernseed.info> <87d3qa5wl1.fsf@free.fr> User-Agent: Notmuch/0.5 (http://notmuchmail.org) Emacs/23.1.1 (i486-pc-linux-gnu) Date: Fri, 12 Nov 2010 16:58:02 +0000 Message-ID: <87pquafpid.fsf@bookbinder.fernseed.info> 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: Fri, 12 Nov 2010 16:58:40 -0000 --=-=-= On Fri, 12 Nov 2010 17:35:22 +0100, Matthieu Lemerre wrote: > I prefer to add tags, for the following reasons: It sounds like we do much the same things with our mail except that your approach is quite disciplined and mine quite lazy :-) > - If I want to search through a mailing list, I don't have to > remember its address. Saved searchs solve the problem only partly, > because I am not able to make complex queries involving several saved > searches. This could be solved only by making notmuch aware of saved > searches. [...] > By default, hitting the space bar throughout a thread would remove > every tag from the thread, so you keep asking "where was the mail in > my inbox that I have read and I can't find anymore?" As it's so quick, I tend to search my entire archive, even for new messages, through progressive stages of filtering (which is really all that a saved search is) starting off knowing only vaguely what it is that I'm looking for. For instance 'there was something on the notmuch list about printing format issues recently' would be 's to:notmuch' 'f print' 'f format' etc until I see what I'm looking for (or something similar) in the results. That particular set of steps gives me a buffer with 24 threads in it, the second of which is what I was looking for. I tend not to even bother with subject header based searches unless I know for sure that what I'm looking for had an unusual subject. It sounds like a lot of work when I write it out long-form, but it's incredibly intuitive and so far always gets me what I need. I can see your approach has its own merits though. --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkzdchoACgkQP1ao/7snsT7ZtACfUKFDWAxQIaZA8x5HyCLcBUj7 /LIAoMhsrSAy8DM0EneJ0q5UDJrRV/EZ =jH10 -----END PGP SIGNATURE----- --=-=-=--