emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jeffrey Brent McBeth <mcbeth@broggs.org>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: emacs-orgmode@gnu.org
Subject: Re: relative deadlines
Date: Tue, 9 Dec 2014 10:07:26 -0500	[thread overview]
Message-ID: <20141209150726.GK20333@broggs.org> (raw)
In-Reply-To: <87bnndcggb.fsf@nicolasgoaziou.fr>

On Tue, Dec 09, 2014 at 10:36:52AM +0100, Nicolas Goaziou wrote:
> Hello,
> 
> Jeffrey Brent McBeth <mcbeth@broggs.org> writes:
> 
> > I have a python function that can take a stripped down org file and
> > places an active date after each #<block># (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

  parent reply	other threads:[~2014-12-09 15:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-08  2:10 relative deadlines Jeffrey Brent McBeth
     [not found] ` <87bnndcggb.fsf@nicolasgoaziou.fr>
2014-12-09 15:07   ` Jeffrey Brent McBeth [this message]
2014-12-09 16:10     ` Nicolas Goaziou
2014-12-09 17:05 ` J. David Boyd

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20141209150726.GK20333@broggs.org \
    --to=mcbeth@broggs.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=mail@nicolasgoaziou.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).