From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ivan Nedrehagen Subject: The recurring task pattern Date: Wed, 03 Jun 2009 10:50:42 +0200 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-15 Content-Transfer-Encoding: 7BIT Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MBmBm-0005cI-G3 for emacs-orgmode@gnu.org; Wed, 03 Jun 2009 04:51:14 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MBmBh-0005bd-7v for emacs-orgmode@gnu.org; Wed, 03 Jun 2009 04:51:13 -0400 Received: from [199.232.76.173] (port=39275 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MBmBh-0005ba-3n for emacs-orgmode@gnu.org; Wed, 03 Jun 2009 04:51:09 -0400 Received: from bgo1smout1.broadpark.no ([217.13.4.94]:55587) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MBmBg-00011F-N5 for emacs-orgmode@gnu.org; Wed, 03 Jun 2009 04:51:08 -0400 Received: from bgo1sminn1.broadpark.no ([217.13.4.93]) by bgo1smout1.broadpark.no (Sun Java(tm) System Messaging Server 6.3-3.01 (built Jul 12 2007; 32bit)) with ESMTP id <0KKN005IEN8IHY50@bgo1smout1.broadpark.no> for emacs-orgmode@gnu.org; Wed, 03 Jun 2009 10:50:42 +0200 (CEST) Received: from gorontha.conoptica.local ([80.203.148.138]) by bgo1sminn1.broadpark.no (Sun Java(tm) System Messaging Server 6.3-3.01 (built Jul 12 2007; 32bit)) with ESMTP id <0KKN001LFN8IDJB3@bgo1sminn1.broadpark.no> for emacs-orgmode@gnu.org; Wed, 03 Jun 2009 10:50:42 +0200 (CEST) List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Emacs org mode mailinglist Hi everyone, I have a pattern that repeats itself in org-mode and I am wondering if anyone have any solutions to it. I have some tasks that must be done each week, it does not matter when I complete them, but they must be done before end of the week. And when the next week comes the task should be repeated. Now I have an TODO item on it and I flip it back and forth from TODO to DONE, but it requires me to remember that I have completed the task, and requires me to put it back to TODO next week. This is not working very well. What I would like: At the beginning of each week the task sets itself to TODO. When I complete it, it logs the state change (only for this state, I do not want state change logging on all). A reminder that I did not complete it last week would be nice, but I expect that to be too much to ask for. Does anyone use org-mode for anything like this?