--- /dev/null
+Return-Path: <sojkam1@fel.cvut.cz>\r
+X-Original-To: notmuch@notmuchmail.org\r
+Delivered-To: notmuch@notmuchmail.org\r
+Received: from localhost (localhost [127.0.0.1])\r
+ by olra.theworths.org (Postfix) with ESMTP id 29A4D431FC3\r
+ for <notmuch@notmuchmail.org>; Mon, 1 Mar 2010 03:12:52 -0800 (PST)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -0.934\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-0.934 tagged_above=-999 required=5\r
+ tests=[AWL=-0.935, BAYES_50=0.001] autolearn=ham\r
+Received: from olra.theworths.org ([127.0.0.1])\r
+ by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)\r
+ with ESMTP id O8QhXJWl9yPI for <notmuch@notmuchmail.org>;\r
+ Mon, 1 Mar 2010 03:12:51 -0800 (PST)\r
+Received: from max.feld.cvut.cz (max.feld.cvut.cz [147.32.192.36])\r
+ by olra.theworths.org (Postfix) with ESMTP id C0713431FAE\r
+ for <notmuch@notmuchmail.org>; Mon, 1 Mar 2010 03:12:50 -0800 (PST)\r
+Received: from localhost (unknown [192.168.200.4])\r
+ by max.feld.cvut.cz (Postfix) with ESMTP id 938AF19F338E;\r
+ Mon, 1 Mar 2010 12:12:42 +0100 (CET)\r
+X-Virus-Scanned: IMAP AMAVIS\r
+Received: from max.feld.cvut.cz ([192.168.200.1])\r
+ by localhost (styx.feld.cvut.cz [192.168.200.4]) (amavisd-new,\r
+ port 10044)\r
+ with ESMTP id Cb85WEj6UAwR; Mon, 1 Mar 2010 12:12:41 +0100 (CET)\r
+Received: from imap.feld.cvut.cz (imap.feld.cvut.cz [147.32.192.34])\r
+ by max.feld.cvut.cz (Postfix) with ESMTP id 0969019F3392;\r
+ Mon, 1 Mar 2010 12:12:41 +0100 (CET)\r
+Received: from steelpick.localdomain (k335-30.felk.cvut.cz [147.32.86.30])\r
+ (Authenticated sender: sojkam1)\r
+ by imap.feld.cvut.cz (Postfix) with ESMTPSA id 9E9DBFA004;\r
+ Mon, 1 Mar 2010 12:12:40 +0100 (CET)\r
+Received: from wsh by steelpick.localdomain with local (Exim 4.71)\r
+ (envelope-from <sojkam1@fel.cvut.cz>)\r
+ id 1Nm3YG-0004Rb-Eq; Mon, 01 Mar 2010 12:12:40 +0100\r
+From: Michal Sojka <sojkam1@fel.cvut.cz>\r
+To: Carl Worth <cworth@cworth.org>, notmuch@notmuchmail.org\r
+In-Reply-To: <87zl2v4vjt.fsf@yoom.home.cworth.org>\r
+References: <87zl2v4vjt.fsf@yoom.home.cworth.org>\r
+Date: Mon, 01 Mar 2010 12:12:40 +0100\r
+Message-ID: <87hbp0mh1z.fsf@steelpick.localdomain>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain; charset=us-ascii\r
+Subject: Re: [notmuch] Thoughts on not seeing messages I can't deal with\r
+ (yet, or now, or here...)\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.13\r
+Precedence: list\r
+List-Id: "Use and development of the notmuch mail system."\r
+ <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,\r
+ <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
+List-Archive: <http://notmuchmail.org/pipermail/notmuch>\r
+List-Post: <mailto:notmuch@notmuchmail.org>\r
+List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
+List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
+ <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Mon, 01 Mar 2010 11:12:52 -0000\r
+\r
+On Fri, 26 Feb 2010 12:00:06 -0800, Carl Worth <cworth@cworth.org> wrote:\r
+> [This mail started as some off-topic rambling in my reply to the\r
+> notmuch-reply script. So that's why it starts on one topic and ends\r
+> somewhere else entirely.]\r
+> \r
+> I'm currently avoiding any locking failures with notmuch commands by\r
+> running "notmuch new" manually, (rather than from a cron job). And it\r
+> occurs to me that running "notmuch new" manually has a certain\r
+> benefit---it allows me to bring in a chunk of mail, and then process all\r
+> of that (either by replying, or setting aside to a particular project or\r
+> "todo" tag, etc.) without getting distracted by other mail coming in.\r
+\r
+That's what I like on notmuch too. (I also don't use cron.)\r
+\r
+> I know that what I really want instead of "todo" is a way to express the\r
+> reason I'm postponing a message. There's probably some resource I'm\r
+> missing that I need before I can deal with it. Perhaps that's:\r
+> \r
+> * I can't decide on this until I'm with co-workers and can talk about\r
+> this.\r
+> \r
+> * I can't resolve this until I'm at the office with the right hardware\r
+> to test.\r
+> \r
+> * I need to remember to do something with this when I'm at home.\r
+> \r
+> * I need a nice block of "discretionary time" to be able to give this\r
+> topic the attention I want to.\r
+> \r
+> * I need to look at this message again on this Saturday.\r
+> \r
+> So what I really want to do is to tag things based on those criteria,\r
+> ("office", "magic-hardware", "home", "discretionary", "2010-02-27"),\r
+> which I can at least do now.\r
+> \r
+> But what I'm currently missing is a way for the folders based on these\r
+> tags to only appear at the right times, (when the resource is\r
+> available).\r
+\r
+It seems I have the same needs as you. I use Emacs's org-mode for\r
+managing my TODO list and I find org-remember very useful in this\r
+context.\r
+\r
+It works like this: I have a global key binding (C-c r) for org-remember\r
+and whenever I press this key a new buffer appears. I write my TODO item\r
+there and after C-c C-c the buffer is appended to my TODO list. What is\r
+important, is that the remember buffer may be pre-filled with some\r
+information based on major mode of from where it was invoked. This\r
+information might be a so called org-link (a link to another entity\r
+which emacs can work with). David Bremner did some work\r
+(id:8763805hr2.fsf@pivot.cs.unb.ca) to support links to mails in\r
+notmuch, but I haven't tried it yet.\r
+\r
+So I'd like to process my mail like this: If I cannot complete the mail\r
+immediately, I'll press "C-c r" to create a new TODO item where I\r
+mention what is needed for completing this mail. The TODO item will\r
+automatically contain a link to the original message. I can also add\r
+some Org Mode properties such as SCHEDULED or DEADLINE. Then I remove\r
+unread and inbox tags from the message. This way I'll process the whole\r
+inbox until it becomes empty.\r
+\r
+Then I will use org-mode's Agenda view to show me what to do just now.\r
+Thanks to the properties such as SCHEDULED, I won't see items which I do\r
+not want to see today.\r
+\r
+If I complete some TODO item, I'll use org-link to immediately jump to\r
+the original message and I'll reply to it.\r
+\r
+The only problem here is some kind of duplication. Org-mode has its own\r
+tags and these have nothing in common with notmuch tags. So, in order to\r
+use tags your TODO items and mails, you would need to tag them twice\r
+(once in notmuch and once in org).\r
+\r
+What might work here would be some kind of integration between Org's\r
+Agenda view and notmuch search. But I do not have an exact idea how this\r
+could look like.\r
+\r
+Bye\r
+Michal\r
projects / notmuch-archives.git / commitdiff