This is now also fixed, thanks!
Friedrich Delgado schrieb:
> However: If I (setq org-icalendar-use-plain-timestamp nil) as in my
> customisation, scheduled date-ranges are not exported at all (no
> matter what org-icalendar-use-scheduled is set to).
>
> ( 49905a566970541de76b6d49004c62e50c625a98 f
Hi Friedrich,
Friedrich Delgado writes:
> Friedrich Delgado schrieb:
>> confirmed, latest org does the right thing[TM]
>
> However: If I (setq org-icalendar-use-plain-timestamp nil) as in my
> customisation, scheduled date-ranges are not exported at all (no
> matter what org-icalendar-use-schedu
Friedrich Delgado schrieb:
> confirmed, latest org does the right thing[TM]
However: If I (setq org-icalendar-use-plain-timestamp nil) as in my
customisation, scheduled date-ranges are not exported at all (no
matter what org-icalendar-use-scheduled is set to).
( 49905a566970541de76b6d49004c62e50c
confirmed, latest org does the right thing[TM]
Bastien schrieb:
> Hi Friedrich,
>
> Friedrich Delgado writes:
>
> > If I have an org-file containing a todo with a scheduled date range, like
> > this:
> >
> > ,[ foo.org ]
> > *** TODO Weekend with the lads
> > SCHEDULED: <2012-05-04 Fr
Hi Friedrich,
Friedrich Delgado writes:
> If I have an org-file containing a todo with a scheduled date range, like
> this:
>
> ,[ foo.org ]
> *** TODO Weekend with the lads
> SCHEDULED: <2012-05-04 Fr>--<2012-05-08 Di>
> `
>
> and try to export it via org-export-icalendar-this-f
Hi Friedrich,
Friedrich Delgado writes:
> If I have an org-file containing a todo with a scheduled date range, like
> this:
>
> ,[ foo.org ]
> *** TODO Weekend with the lads
> SCHEDULED: <2012-05-04 Fr>--<2012-05-08 Di>
> `
>
> and try to export it via org-export-icalendar-this-f
Hi!
If I have an org-file containing a todo with a scheduled date range, like
this:
,[ foo.org ]
*** TODO Weekend with the lads
SCHEDULED: <2012-05-04 Fr>--<2012-05-08 Di>
`
and try to export it via org-export-icalendar-this-file, the resulting
foo.ics will look like this
,[
