From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeffrey Brent McBeth Subject: Re: relative deadlines Date: Tue, 9 Dec 2014 10:07:26 -0500 Message-ID: <20141209150726.GK20333@broggs.org> References: <20141208021032.GF20333@broggs.org> <87bnndcggb.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:33996) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XyMOm-0003OD-HR for emacs-orgmode@gnu.org; Tue, 09 Dec 2014 10:08:30 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XyMOg-0001Xn-Ff for emacs-orgmode@gnu.org; Tue, 09 Dec 2014 10:08:24 -0500 Received: from cdptpa-outbound-snat.email.rr.com ([107.14.166.228]:20668 helo=cdptpa-oedge-vip.email.rr.com) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XyMOg-0001Ws-60 for emacs-orgmode@gnu.org; Tue, 09 Dec 2014 10:08:18 -0500 Content-Disposition: inline In-Reply-To: <87bnndcggb.fsf@nicolasgoaziou.fr> 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: Nicolas Goaziou Cc: emacs-orgmode@gnu.org On Tue, Dec 09, 2014 at 10:36:52AM +0100, Nicolas Goaziou wrote: > Hello, > > Jeffrey Brent McBeth writes: > > > 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... > > It sounds like over-engineering to me. I very well may be. A common fault of engineers :) > I think it would be better to have a function shifting all timestamps in > a subtree. It may even exist already. I cannot remember. This is where I fall down. I don't see how that meets my basic need case. I know that certain sub tasks need to start 90 days before the final deadline (for example), I can hand count back 90 days and then do the shifting of timestamps, but then the core relevant information is lost of -90d. I have a strong feeling that since my searches don't turn things up, that this is a weird way in which I work rather than the rest of the subcommunity here; so I do appreciate the kind feedback above, I am not yet convinced that I'm insane :) > > 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? > > I don't think so. That is helpful. I read through your wonderful syntax file looking for decent delimeters that wouldn't be a pain to type, and I'm glad that there are no obvious howlers for me. Jeff -- "The man who does not read good books has no advantage over the man who cannot read them." -- Mark Twain