emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Kyle Meyer <kyle@kyleam.com>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-agenda-get-timestamps and properties
Date: Thu, 12 Nov 2020 23:12:21 -0500	[thread overview]
Message-ID: <87a6vl7v4q.fsf@kyleam.com> (raw)
In-Reply-To: <87eel1axqc.fsf@web.de>

Michael Heerdegen writes:

> When debugging, I found that `org-agenda-get-timestamps' does, depending
> on the position of the SCHEDULED spec, do return a timestamp when an
> entry is formatted like this:
> ** APPT 10:40 Xyz
>     :ID:       1d313f9a-3044-4c23-9278-422646ec9063
>     :END:
>     SCHEDULED: <2020-11-08 So +1d>

To be valid, the SCHEDULED spec should be immediately following the
headline.  So this is just a timestamp...

> but not when formatted like this:
> ** APPT 10:40 Xyz
>     SCHEDULED: <2020-11-08 So +1d>
>     :ID:       1d313f9a-3044-4c23-9278-422646ec9063
>     :END:
> although the latter form is, AFAICT, recommended, and at least it's what
> I get when creating ids automatically with (org-id-get-create).

...while this is a valid scheduled heading.

> No timestamp, and my appointments don't work (bad).
> Has anybody any insight into this matter?

I haven't looked too closely, but at first glance
org-agenda-get-timestamps not detecting the second entry seems expected.
org-agenda-get-timestamps has a comment that says "[s]kip date ranges,
scheduled and deadlines, which are handled specially".  Still without
looking closely, I'd guess that the "handled specially" is referring to
org-agenda-get-scheduled and org-agenda-get-deadlines.

  reply	other threads:[~2020-11-13  4:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-10 18:11 org-agenda-get-timestamps and properties Michael Heerdegen
2020-11-13  4:12 ` Kyle Meyer [this message]
2020-11-29  2:28   ` Michael Heerdegen

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=87a6vl7v4q.fsf@kyleam.com \
    --to=kyle@kyleam.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=michael_heerdegen@web.de \


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