From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeffrey Brent McBeth Subject: relative deadlines Date: Sun, 7 Dec 2014 21:10:32 -0500 Message-ID: <20141208021032.GF20333@broggs.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:44200) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xy10Q-00051n-BM for emacs-orgmode@gnu.org; Mon, 08 Dec 2014 11:17:57 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Xy10I-0005j8-S8 for emacs-orgmode@gnu.org; Mon, 08 Dec 2014 11:17:50 -0500 Received: from cdptpa-outbound-snat.email.rr.com ([107.14.166.232]:52394 helo=cdptpa-oedge-vip.email.rr.com) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xy10I-0005j1-Nf for emacs-orgmode@gnu.org; Mon, 08 Dec 2014 11:17:42 -0500 Received: from williwaw ([10.0.1.2]) by broggs.org with esmtps (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.76) (envelope-from ) id 1Xy10F-0008Uk-An for emacs-orgmode@gnu.org; Mon, 08 Dec 2014 11:17:41 -0500 Received: from localhost ([127.0.0.1] helo=broggs.org) by williwaw with esmtp (Exim 4.82) (envelope-from ) id 1Xy0zU-0005fW-KD for emacs-orgmode@gnu.org; Mon, 08 Dec 2014 11:16:52 -0500 Resent-Message-ID: <20141208161652.GJ20333@broggs.org> Resent-To: emacs-orgmode@gnu.org Content-Disposition: inline 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: emacs-org@gnu.org >From time to time (each time I delve into using org-mode for deadlines before my habits fall apart), I find the desire to have some form of relative deadlines. By this I mean, that there are often sequences of tasks that I know the time required to complete and when things are due. These tasks may repeat (usually do). It would be awful helpful to me, but I would guess few others, as a search didn't find much, for there to be some annotation like this (example is farcical, notation is notional) * Go on date DEADLINE: <2014-12-25> ** Ask Girl #<-3w># ** Wash Hair #<-2w># ** Make Money #<-1w2d># ** Get in Car #<-0d># ** Call her back #<+1w># that in the agenda view would show as a sequence of tasks with the following dates Go on date <2014-12-25> Ask Girl <2014-12-04> Wash Hair <2014-12-11> Make Money <2014-12-16> Get in Car <2014-12-25> Call her back <2015-01-01> I have a python function that can take a stripped down org file and places an active date after each ## (or inactive after #[block]#), that I hacked up today to see if it would really be as useful as I thought, but I keep thinking that someone somewhere must have scratched this itch elsewhere, and having to partially parse org in python and modify the text rather than having my agenda smart enough to figure it out gives me pause... If nobody have better ideas, are the block delimiters I'm using going to conflict with some other feature in org that I'm just not using yet? The main functuionality I'm stumbling toward is having an easily moveable end date (so replacing the block with absolute dates is a nono). Thanks for your attention, Jeffrey McBeth -- "The man who does not read good books has no advantage over the man who cannot read them." -- Mark Twain