From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nick Dokos Subject: Re: Sending reminder Emails to other people with org-mode Date: Mon, 25 Feb 2013 14:55:31 -0500 Message-ID: <5373.1361822131@alphaville> References: <201302252020.39712.thomas@koch.ro> Reply-To: nicholas.dokos@hp.com Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Return-path: Received: from eggs.gnu.org ([208.118.235.92]:36308) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UA49E-0000a4-Rx for emacs-orgmode@gnu.org; Mon, 25 Feb 2013 14:55:44 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UA497-00063W-OP for emacs-orgmode@gnu.org; Mon, 25 Feb 2013 14:55:40 -0500 Received: from g6t0186.atlanta.hp.com ([15.193.32.63]:15138) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UA497-00063F-Fd for emacs-orgmode@gnu.org; Mon, 25 Feb 2013 14:55:33 -0500 In-Reply-To: Message from Thomas Koch of "Mon, 25 Feb 2013 20:20:39 +0100." <201302252020.39712.thomas@koch.ro> Content-ID: <5322.1361821653.1@alphaville> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: thomas@koch.ro Cc: emacs-orgmode@gnu.org Thomas Koch wrote: > Hi, > > A common workflow (of mine) is: Work on something, submit and wait several > days or weeks for a review or reply before I can continue. So I switch to the > next task. > > I'd love if org-mode could keep track of tasks that are waiting for others and > semi-automatically remind those others in a weekly email that I'm waiting for > them. > > I imagine a command that I could run over my tasks. The command finds such > tasks, prepares a reminder mail that I can send directly from within emacs and > remembers the date when I last naged the other. > > Any ideas? Thanks for your attention, > It depends on how you set up your tasks, but I imagine something like the following will be fairly easy to set up: o When you submit, the task goes into a WAITING state and several properties are added: (who to nag, when the last nag went out). o You can then write a function that finds waiting tasks, and checks the relevant properties in order to construct the nagging email. The details will vary of course, but the mapping and property APIs should be able to deal with the org aspects. See (info "(org) Using the mapping API") (info "(org) Using the property API") The is-it-time-to-nag logic can be easily done in elisp. Sending email is also quite possible in elisp, but the details will depend on the mail package you decide to use. o The function can be run using a timer. See (info "(elisp) Timers for Delayed Execution") There are lots of details elided in the above description of course, but this is probably a reasonable first approximation. Nick