emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: "David C. Nelson" <David.Nelson@gpsdo.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: sexp timestamp behavior
Date: Wed, 16 Jan 2008 17:46:59 +0100	[thread overview]
Message-ID: <649F2A00-3C92-4BDF-9DC9-45695562323D@gmail.com> (raw)
In-Reply-To: <8EAB4B51-76EC-4615-9BF8-9094C0B6FE0C@gpsdo.com>


On Jan 10, 2008, at 2:56 AM, David C. Nelson wrote:

>
> I've been playing around with org mode and I'm confused about the  
> behavior of timestamps that are specified using sexps when displayed  
> in the agenda. Specifically, if I schedule a TODO and specify a  
> timestamp using a sexp, the TODO is not carried forward if it is  
> past due.  It does show on the day it was scheduled, but if the TODO  
> is not done, the TODO is not carried forward as the manual says it  
> should.
>
> If I don't use a sexp timestamp, the TODO is carried forward if past  
> due as expected.
>
> I can't find anything in the manual that suggests sexp timestamps  
> are treated differently.

Yes, the manual is not complete here.  I am adding the following text:

   You may use time stamps with repeaters in scheduling and deadline
   entries.  Org-mode will issue early and late warnings based on the
   assumption that the time stamp represents the nearest instance of
   the repeater.  However, the use of diary sexp entries like
   <%%(diary-float t 42)>
   in scheduling and deadline timestamps is limited.  Org-mode does not
   know enough about the internals of each sexp function to issue  
early and
   late warnings.  However, it will show the item on each day where the
   sexp entry matches.

I hope this clarifies things.

- Carsten

      reply	other threads:[~2008-01-16 17:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-10  1:56 sexp timestamp behavior David C. Nelson
2008-01-16 16:46 ` 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=649F2A00-3C92-4BDF-9DC9-45695562323D@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=David.Nelson@gpsdo.com \
    --cc=emacs-orgmode@gnu.org \
    /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).