emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Cameron Horsburgh <cammo@netcall.com.au>
To: Giovanni Ridolfi <giovanni.ridolfi@yahoo.it>
Cc: emacs-orgmode@gnu.org
Subject: Re: Adding time to deadline and schedule timestamps
Date: Tue, 7 Apr 2009 22:42:30 +1000	[thread overview]
Message-ID: <20090407124230.GA4015@earth> (raw)
In-Reply-To: <421502.81336.qm@web28312.mail.ukl.yahoo.com>

On Tue, Apr 07, 2009 at 12:24:33PM +0000, Giovanni Ridolfi wrote:
> --- Mar 7/4/09, Cameron Horsburgh <cammo@netcall.com.au> ha scritto:
> > I'm trying to get a little more control over my 
> > timestamps. 
> The manual (8.3 Deadlines and scheduling) states:
> [...] special keywords to facilitate *planning*
>      Meaning: the task (most likely a TODO item, though not
>      necessarily) is supposed to be finished on that *date*.
>      Meaning: you are planning to start working on that task on the
>      given *date*.
> I think you should use a timestamp 
> * Submit :Project_A_
> DEADLINE <2008-10-11>
> ** last minute for submission 
> <2008-10-11 16:59>

Yes, that's true. However, being able to do this in one timestamp
would seem to make a lot of sense. After all, this will show up in my
agenda as two apparently unrelated things. Besides, I should only have
to put the information in once, not twice.


Cameron Horsburgh

Blog: http://spiritcry.wordpress.com/

  reply	other threads:[~2009-04-07 12:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-07 12:24 Adding time to deadline and schedule timestamps Giovanni Ridolfi
2009-04-07 12:42 ` Cameron Horsburgh [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-04-07  9:58 Cameron Horsburgh
2009-04-07 12:32 ` Bernt Hansen
2009-04-07 12:46   ` Cameron Horsburgh
2009-04-07 12:51 ` Matthew Lundin

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=20090407124230.GA4015@earth \
    --to=cammo@netcall.com.au \
    --cc=emacs-orgmode@gnu.org \
    --cc=giovanni.ridolfi@yahoo.it \


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