From: Carsten Dominik <dominik@science.uva.nl>
To: Jim Barbour <jbar@yahoo-inc.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: non static deadlines
Date: Sat, 21 Mar 2009 15:36:24 +0100 [thread overview]
Message-ID: <8F23BCF7-58DC-4DF0-BDD7-15F36FE4F505@uva.nl> (raw)
In-Reply-To: <20090319054607.GD17169@spendguard.yahoo-inc.com>
Hi Jim,
we do not have anything like this implemented. I guess this could
be implemented as an add-on. If more hooks are needed to get this done,
I will provide them.
- Carsten
On Mar 19, 2009, at 6:46 AM, Jim Barbour wrote:
> Howdy folks,
>
> My name is Jim. I am a blind UNIX engineer currently working at
> Yahoo.
>
> I use org-more quite a bit for planning.
>
> I'm curious if there's been any talk of allowing deadlines to be
> expressed as delta times from either the start of the project or from
> another deadline?
>
> As an example, I'd like to be able to say...
>
> * The project begins on 2009-03-01
> * Phase 1 will be complete 2 weeks later.
> * Phase 2 will be completed 2 weeks after phase 1
> * A review will happen 1 week after phase 1
> * Phase 3 will be completed 5 weeks after phase 2.
>
> Then, when I export my org files, or view agendas, I would get actual
> dates, based on the start date of the project and the delta dates for
> each item. Then, I'd like to be able to change Phase 2 to say...
>
> * Phase 2 will be completed 2 months after phase 1
>
> and have phase 3's dates update automatically.
>
> I've been thinking about quick and dirty ways to do this, and was
> wondering if I was perhaps reinventing the wheel.
>
> All thoughts welcome, and thanks for an awesome tool!
>
> Jim
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
prev parent reply other threads:[~2009-03-21 19:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-19 5:46 non static deadlines Jim Barbour
2009-03-21 14:36 ` Carsten Dominik [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=8F23BCF7-58DC-4DF0-BDD7-15F36FE4F505@uva.nl \
--to=dominik@science.uva.nl \
--cc=emacs-orgmode@gnu.org \
--cc=jbar@yahoo-inc.com \
/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).