emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Matthew Lundin <Matthew.Lundin@valpo.edu>
To: Gijs Hillenius <gijs@hillenius.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: arithmatic error when scheduling +0d
Date: Wed, 14 Jan 2009 09:29:29 -0600	[thread overview]
Message-ID: <m2k58xhpnq.fsf@fastmail.fm> (raw)
In-Reply-To: <87hc41sz2j.fsf@hillenius.net> (Gijs Hillenius's message of "Wed\, 14 Jan 2009 16\:10\:44 +0100")

Gijs Hillenius <gijs@hillenius.net> writes:
>
> Thanks! But I thought the +0d in "SCHEDULED: <2009-01-15 Thu +0d>"
> means that I would be warned about this TODO item not 14 days or less
> before the date, but only on the date itself. Maybe I should have
> written +0, as per http://orgmode.org/org.html#Timestamps
>
> I have a feeling this behaviour changed "recently" in org-mode. But
> it is probably just me.
>

I think you are confusing DEADLINE and SCHEDULED items. For items with
a deadline, you can indeed add a warning time specifier, as in 

,----
| ** Deadline
|    DEADLINE: <2009-01-15 Thu -0d>
`----

Which means that the deadline warning will first show up on your
agenda on the day it is due, or 

,----
| ** Deadline
|    DEADLINE: <2009-01-15 Thu -3d>
`----

Which means the warning will show up three days before the item is
due.

- Scheduled items first show up on the agenda on the day they are
scheduled and every day thereafter until they are marked done.

- Deadline warnings show up on the agenda n days before the deadline,
with n specified in the variable org-deadline-warning-day or via the
negative modifier in the examples above.

Hope this helps,

Matt

  reply	other threads:[~2009-01-14 15:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-14 10:16 arithmatic error when scheduling +0d Gijs Hillenius
2009-01-14 13:23 ` Matthew Lundin
2009-01-14 15:10   ` Gijs Hillenius
2009-01-14 15:29     ` Matthew Lundin [this message]
2009-01-14 16:01       ` Gijs Hillenius
2009-01-14 15:35     ` Bernt Hansen
2009-01-14 14:32 ` Dennis Groves

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=m2k58xhpnq.fsf@fastmail.fm \
    --to=matthew.lundin@valpo.edu \
    --cc=emacs-orgmode@gnu.org \
    --cc=gijs@hillenius.net \
    /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).