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 8C8CA431FC3 for ; Fri, 26 Feb 2010 15:34:26 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: -1.339 X-Spam-Level: X-Spam-Status: No, score=-1.339 tagged_above=-999 required=5 tests=[AWL=-0.340, BAYES_50=0.001, RCVD_IN_DNSWL_LOW=-1] 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 lisS2tZBkxEN for ; Fri, 26 Feb 2010 15:34:25 -0800 (PST) Received: from VA3EHSOBE001.bigfish.com (va3ehsobe001.messaging.microsoft.com [216.32.180.11]) by olra.theworths.org (Postfix) with ESMTP id 2BD15431FAE for ; Fri, 26 Feb 2010 15:34:25 -0800 (PST) Received: from mail82-va3-R.bigfish.com (10.7.14.249) by VA3EHSOBE001.bigfish.com (10.7.40.21) with Microsoft SMTP Server id 8.1.340.0; Fri, 26 Feb 2010 23:34:19 +0000 Received: from mail82-va3 (localhost [127.0.0.1]) by mail82-va3-R.bigfish.com (Postfix) with ESMTP id 85D20C580B1; Fri, 26 Feb 2010 23:34:19 +0000 (UTC) X-SpamScore: -31 X-BigFish: VPS-31(zz11fbM1432R98dN936eMaccK1442J14e1Izz1202hzzz32i6bh61h) X-Spam-TCS-SCL: 0:0 Received: from mail82-va3 (localhost.localdomain [127.0.0.1]) by mail82-va3 (MessageSwitch) id 1267227258730287_21432; Fri, 26 Feb 2010 23:34:18 +0000 (UTC) Received: from VA3EHSMHS023.bigfish.com (unknown [10.7.14.242]) by mail82-va3.bigfish.com (Postfix) with ESMTP id A3B6C62804E; Fri, 26 Feb 2010 23:34:18 +0000 (UTC) Received: from ausb3extmailp02.amd.com (163.181.251.22) by VA3EHSMHS023.bigfish.com (10.7.99.33) with Microsoft SMTP Server (TLS) id 14.0.482.39; Fri, 26 Feb 2010 23:34:18 +0000 Received: from ausb3twp01.amd.com (ausb3twp01.amd.com [163.181.250.37]) by ausb3extmailp02.amd.com (Switch-3.2.7/Switch-3.2.7) with ESMTP id o1QNbLMK017852; Fri, 26 Feb 2010 17:37:25 -0600 X-WSS-ID: 0KYH2T1-01-HUH-02 X-M-MSG: Received: from sausexhtp01.amd.com (sausexhtp01.amd.com [163.181.3.165]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by ausb3twp01.amd.com (Tumbleweed MailGate 3.7.2) with ESMTP id 21DD110285CA; Fri, 26 Feb 2010 17:34:12 -0600 (CST) Received: from optimon.amd.com (163.181.34.104) by sausexhtp01.amd.com (163.181.3.165) with Microsoft SMTP Server (TLS) id 8.2.234.1; Fri, 26 Feb 2010 15:34:13 -0800 Received: from mhdc-ns01.amd.com (mhdc-ns01.amd.com [165.204.35.147]) by optimon.amd.com (8.12.10/8.12.10) with ESMTP id o1QNYDGW001556; Fri, 26 Feb 2010 17:34:13 -0600 Received: from mhdcelk-nx01.amd.com (mhdcelk-nx01.amd.com [165.204.144.108]) by mhdc-ns01.amd.com (8.13.8+Sun/8.13.8) with ESMTP id o1QNXvkj000820; Fri, 26 Feb 2010 16:33:57 -0700 (MST) Received: (from manderso@localhost) by mhdcelk-nx01.amd.com (8.13.1/8.13.1/Submit) id o1QNXvNv007669; Fri, 26 Feb 2010 16:33:57 -0700 X-Authentication-Warning: mhdcelk-nx01.amd.com: manderso set sender to MarkR.Anderson@amd.com using -f From: Mark Anderson To: Carl Worth , "notmuch\@notmuchmail.org" In-Reply-To: <87zl2v4vjt.fsf@yoom.home.cworth.org> References: <87zl2v4vjt.fsf@yoom.home.cworth.org> Date: Fri, 26 Feb 2010 16:33:57 -0700 Message-ID: <3wdy6if4lne.fsf@mhdcelk-nx01.amd.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Virus-Scanned: ClamAV version 0.87.1, clamav-milter version 0.87 on optimon.amd.com X-Virus-Status: Clean X-Reverse-DNS: ausb3extmailp02.amd.com Subject: Re: Thoughts on not seeing messages I can't deal with (yet, or now, or here...) 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, 26 Feb 2010 23:34:26 -0000 Carl, There's a post from a while ago about using GTD on Remember The Milk. Remember the Milk as described here is mainly a todo manager, but the saved search (as a list of todo tasks that match the criterion) is what's being utilized here that makes me think so much of notmuch. This seems to capture some of the things that you want to see, since you are trying to manage action items which happen to live in mail bodies. http://blog.rememberthemilk.com/2008/05/guest-post-advanced-gtd-with-remember-the-milk/ apparently another post has expired on the topic, with some focus on contexts: http://web.archive.org/web/20080331121051/http://www.geektronica.com/2007-01-15-gtd-with-rtm-getting-things-done-with-remember-the-milk The main tool in use here is a viewport on the collection of things that might need to be reviewed. RTM tabs (which are saved searches) which you have designed to be the contexts you might be executing in, in this case. I know this is related pretty heavily to what you are looking for, but how to bring this about specifically, that's going to be up to you. Enjoy, -Mark On Fri, 26 Feb 2010 14:00:06 -0600, Carl Worth wrote: > [This mail started as some off-topic rambling in my reply to the > notmuch-reply script. So that's why it starts on one topic and ends > somewhere else entirely.] > > I'm currently avoiding any locking failures with notmuch commands by > running "notmuch new" manually, (rather than from a cron job). And it > occurs to me that running "notmuch new" manually has a certain > benefit---it allows me to bring in a chunk of mail, and then process all > of that (either by replying, or setting aside to a particular project or > "todo" tag, etc.) without getting distracted by other mail coming in. > > It almost makes me want to just run "notmuch new" something like once > per day. > > But then, of course, there are times where there are important messages > I need to get to quickly, or fast-moving threads where I need to reply > several times throughout the day. > > But I do have particular mailing lists that I don't want to read more > than once a day, for instance. If I wait until I have about a days worth > of mail in those lists, then I can deal with them very efficiently, > (just scan all the subjects, read a thread or two and the "* -inbox" the > rest). This gets a lot less efficient if I have to deal with those lists > on a regular basis throughout the day, (particularly before we have > support for "muted" threads). > > So I'd like to be able to deal with important messages as they come in, > but postpone bulk stuff. > > But I also notice that there's a bad tendency I have if I try to do this > postponing manually. Mail starts collecting in one of these bulk-list > folders, and I start training myself to ignore the folder, then it gets > huge, (which discourages me even more from looking at it, etc.). [*] > > So I want better support from notmuch to tell me what things deserve my > attention, so that I can avoid training myself to ignore things. I think > what I want here is the ability to set a threshold on a particular > folder based on number of messages or date. Something like: "Don't show > me this folder at all until it has more than X messages or until the > oldest message is at least Y hours old". > > [*] A similar, (but more dangerous), problem occurs with manually > postponing things into a "todo" folder. If I just added a bunch of > things to my todo folder then I have a tendency to think, "I don't need > to look at that---that's got a bunch of things I just decided to > postpone". But then I forget that I put some things in there previously > that really need my attention now. > > I know that what I really want instead of "todo" is a way to express the > reason I'm postponing a message. There's probably some resource I'm > missing that I need before I can deal with it. Perhaps that's: > > * I can't decide on this until I'm with co-workers and can talk about > this. > > * I can't resolve this until I'm at the office with the right hardware > to test. > > * I need to remember to do something with this when I'm at home. > > * I need a nice block of "discretionary time" to be able to give this > topic the attention I want to. > > * I need to look at this message again on this Saturday. > > So what I really want to do is to tag things based on those criteria, > ("office", "magic-hardware", "home", "discretionary", "2010-02-27"), > which I can at least do now. > > But what I'm currently missing is a way for the folders based on these > tags to only appear at the right times, (when the resource is > available). > > When the messages appear at the wrong times, it just trains me to ignore > things, and that's when I start forgetting things and let things fall > through. > > No concrete proposal here, but just some musings on the kinds of issues > I'd really like to be exploring with notmuch, (once we can get past all > these little things like maildir flags, keybindings, failed HTML > rendering, missing FCC support, etc. etc. etc.). > > -Carl Attachment: ATT00001 (application/pgp-signature) > _______________________________________________ > notmuch mailing list > notmuch@notmuchmail.org > http://notmuchmail.org/mailman/listinfo/notmuch