emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <dominik@science.uva.nl>
To: Austin Frank <austin.frank@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: GOAL keyword with DEADLINE semantics?
Date: Mon, 9 Mar 2009 13:01:59 +0100	[thread overview]
Message-ID: <45FD3D92-E16C-477C-BBF7-7BF00DF4E479@uva.nl> (raw)
In-Reply-To: <m0prgsqb52.fsf@gmail.com>

Hi Austin,

since you want to use the same semantics as for deadlines, i.e. the  
same warning period etc, this really is a psychological issue :-)

It is trouble to implement a new keyword or number of keywords.  New  
commands needed to insert this new keyowrd, for example, and many  
regular expressions to generalize.  What I would do if I was bothered  
by this would be

(setq org-deadline-string "DUE:")

which captures both the colors of DEADLINE and GOAL pretty well, I  

In fact, I wish I had made this the default from beginning,
a much shorter and  nicer word.  Now it is too late to change this, I
am afraid.....

- Carsten

On Mar 8, 2009, at 4:36 PM, 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
> export.
> 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,
> /au
> -- 
> Austin Frank
> http://aufrank.net
> GPG Public Key (D7398C2F): http://aufrank.net/personal.asc
> _______________________________________________
> 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

  parent reply	other threads:[~2009-03-09 12:02 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
2009-03-09 12:01 ` Carsten Dominik [this message]
2009-03-09 14:35   ` Bernt Hansen
2009-03-10 17:52     ` Carsten Dominik
2009-03-10  7:15   ` Austin Frank

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:

  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=45FD3D92-E16C-477C-BBF7-7BF00DF4E479@uva.nl \
    --to=dominik@science.uva.nl \
    --cc=austin.frank@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* 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).