Kyle Meyer writes:
> > but not when formatted like this:
> >
> > ** APPT 10:40 Xyz
> > SCHEDULED: <2020-11-08 So +1d>
> > :PROPERTIES:
> > :ID: 1d313f9a-3044-4c23-9278-422646ec9063
> > :END:
> >
> > although the latter form is, AFAICT, recommended, and at least it's what
> >
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
> :PROPERTIES:
> :ID: 1d313f9a-3044-4c23-9278-422646ec9063
Hi,
I have a problem with my appt.el replacement I develop.
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
:PROPERTIES:
:ID: 1d313f9a-3044-
