From: dboyd2@mmm.com (J. David Boyd)
To: emacs-orgmode@gnu.org
Subject: Re: relative deadlines
Date: Tue, 09 Dec 2014 12:05:39 -0500 [thread overview]
Message-ID: <gjubtx14kb30.fsf@W0144758.usac.mmm.com> (raw)
In-Reply-To: 20141208021032.GF20333@broggs.org
Jeffrey Brent McBeth <mcbeth@broggs.org> writes:
> 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 #<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...
>
> 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
I think like that as well. I know when some _thing_ has to be done. Then I
start thinking of all the support items in relative terms to the main one.
You should add this to org mode, if able. It would be a nice addition...
Dave
prev parent reply other threads:[~2014-12-09 17:10 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
2014-12-09 16:10 ` Nicolas Goaziou
2014-12-09 17:05 ` J. David Boyd [this message]
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=gjubtx14kb30.fsf@W0144758.usac.mmm.com \
--to=dboyd2@mmm.com \
--cc=emacs-orgmode@gnu.org \
/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).