From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Gray Subject: Re: The recurring task pattern Date: Wed, 03 Jun 2009 10:57:47 +0200 Message-ID: <863aahy9ro.fsf@portan.ibr.cs.tu-bs.de> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MBmKR-0001C9-7M for emacs-orgmode@gnu.org; Wed, 03 Jun 2009 05:00:11 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MBmKL-00016O-L9 for emacs-orgmode@gnu.org; Wed, 03 Jun 2009 05:00:10 -0400 Received: from [199.232.76.173] (port=56569 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MBmKL-000169-D1 for emacs-orgmode@gnu.org; Wed, 03 Jun 2009 05:00:05 -0400 Received: from main.gmane.org ([80.91.229.2]:46703 helo=ciao.gmane.org) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MBmKK-0002p9-Pc for emacs-orgmode@gnu.org; Wed, 03 Jun 2009 05:00:05 -0400 Received: from root by ciao.gmane.org with local (Exim 4.43) id 1MBmKI-0000qL-A6 for emacs-orgmode@gnu.org; Wed, 03 Jun 2009 09:00:02 +0000 Received: from portan.ibr.cs.tu-bs.de ([134.169.34.77]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 03 Jun 2009 09:00:02 +0000 Received: from chrismgray by portan.ibr.cs.tu-bs.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 03 Jun 2009 09:00:02 +0000 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-orgmode@gnu.org Ivan Nedrehagen wrote: > 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. You can add a deadline that repeats every week for the task. ** TODO Do weekly task DEADLINE: <2009-06-03 Wed +1w> Cheers, Chris