From: Shelagh Manton <firstname.lastname@example.org>
Subject: Re: GOAL keyword with DEADLINE semantics?
Date: Sun, 8 Mar 2009 22:54:30 +0000 (UTC) [thread overview]
Message-ID: <email@example.com> (raw)
On Sun, 08 Mar 2009 11:36:57 -0400, Austin Frank wrote:
> Hi all!
> Currently we can use the DEADLINE keyword to indicate a target date for
> an item to be finished. By my way of thinking, deadlines make sense for
> externally imposed constraints. I also try to set goals for myself for
> when an item will be completed. These are softer than deadlines, but I
> think they could share the same semantics for creation, display, and
> Would it be possible to make `org-deadline-string' a list of strings
> that get handled in the same way as DEADLINE is currently handled? That
> way I could do things like
> * TODO write first chapter
> GOAL: <2009-03-09 Mon>
> * TODO submit manuscript
> GOAL: <2009-05-15 Fri>
> DEADLINE: <2009-06-01 Mon>
> Where the first represents my own planning process and the second
> contains my target completion date (trying to work ahead!) and the hard
> constraint imposed by whoever I'm submitting to. In all cases, I'd like
> agenda notification as the date approaches, I'd like to know if I've
> passed it by, and I'd like the option of including it in ical export.
> Or maybe I should just learn to treat my GOALs like DEADLINEs and stop
> letting myself off the hook so easily ;)
> Do other people think about things this way? Would you have a use for a
> customizable list of keywords that all had the same semantics that
> DEADLINE currently has?
> Thanks for considering it,
I think this sounds like something I've wished for since I first found
out about org-mode. Thank you for analysing it so succinctly.
I would use this if it could be done.
next prev parent reply other threads:[~2009-03-09 3:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-08 15:36 GOAL keyword with DEADLINE semantics? Austin Frank
2009-03-08 22:54 ` Shelagh Manton [this message]
2009-03-09 12:01 ` Carsten Dominik
2009-03-09 14:35 ` Bernt Hansen
2009-03-10 17:52 ` Carsten Dominik
2009-03-10 7:15 ` Austin Frank
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).