Strange interaction between ID block property, org-schedule and ical/ics export backend

Strange interaction between ID block property, org-schedule and ical/ics export backend

[rey-coyrehourcq]

[-- Attachment #1.1: Type: text/plain, Size: 1319 bytes --]

Hi,

I'm starting using org-mode to replace asana, clickup, and other tools to manage
my work.

I'm trying to create a day-to-day workflow with org-mode, org-agenda Schedule
and iCalendat-export backend.

1) What exactly did you do 

After creating a new entry, i run (org-id-get-create) to get a permanent ID
properties :

* Heading 1
 :PROPERTIES:
 :ID: xxxxxxxxxxx
 :END:
  foo

2) what did you expect to happen

I run org-schedule (c-c c-s), choosing a date, and Schedule date is added AFTER
block of property.

* Heading 1
 :PROPERTIES:
 :ID: xxxxxxxxxxx
 :END:
 foo
 SCHEDULED <...-....-...>

3) What happened instead 

Scheduled block is added between the HEADING and the property block...

* Heading 1
 SCHEDULED <...-....-...>
 :PROPERTIES:
 :ID: xxxxxxxxxxx
 :END:
 foo

4) Problem with icalendar export ?

Normally org-caldav-generate-ics export command reuse the ID from property block
to generate the *.ics, 
but it only works if the SCHEDULED block is after the property block.

So in this case, icalendar export generate a new UID, and don't consider the ID
which already exist.




-- 


Sébastien Rey-Coyrehourcq
Research Engineer UMR IDEES
02.35.14.69.30

{Stronger security for your email, follow EFF tutorial : https://ssd.eff.org/}



[-- Attachment #1.2: Type: text/html, Size: 2149 bytes --]

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: Strange interaction between ID block property, org-schedule and ical/ics export backend

[Fraga, Eric]

On Saturday, 31 Aug 2019 at 20:42, rey-coyrehourcq wrote:
> I'm trying to create a day-to-day workflow with org-mode, org-agenda Schedule
> and iCalendat-export backend.

[...]

> Normally org-caldav-generate-ics export command reuse the ID from
> property block to generate the *.ics, but it only works if the
> SCHEDULED block is after the property block.

I don't know about org-caldav-generate-ics but
org-icalendar-export-to-ics works fine with the standard org format
(deadline & scheduled entries ahead of properties drawer).  That
function is in ox-icalendar.el.  Maybe try that instead of the
org-caldav-... method?

-- 
Eric S Fraga via Emacs 27.0.50, Org release_9.2.4-401-gfabd6d

Re: Strange interaction between ID block property, org-schedule and ical/ics export backend

[rey-coyrehourcq]

[-- Attachment #1.1: Type: text/plain, Size: 1213 bytes --]

Hi,
Sorry, i make a typo in the previous mail, i use the "org-icalendar-export-to-
ics" method and not the org-caldav method...
* Heading 1
SCHEDULED <...-....-...>
:PROPERTIES:
:ID: xxxxxxxxxxx
:END:
foo


Le dimanche 01 septembre 2019 à 09:29 +0000, Fraga, Eric a écrit :
> On Saturday, 31 Aug 2019 at 20:42, rey-coyrehourcq wrote:
> > I'm trying to create a day-to-day workflow with org-mode, org-agenda
> > Scheduleand iCalendat-export backend.
> 
> [...]
> > Normally org-caldav-generate-ics export command reuse the ID fromproperty
> > block to generate the *.ics, but it only works if theSCHEDULED block is
> > after the property block.
> 
> I don't know about org-caldav-generate-ics butorg-icalendar-export-to-ics
> works fine with the standard org format(deadline & scheduled entries ahead of
> properties drawer).  Thatfunction is in ox-icalendar.el.  Maybe try that
> instead of theorg-caldav-... method?
In my case, this Schedule event don't export with "org-icalendar-export-to-ics" ... 
I'm using emacs 26.2 


Sébastien Rey-Coyrehourcq
Research Engineer UMR IDEES
02.35.14.69.30

{Stronger security for your email, follow EFF tutorial : https://ssd.eff.org/}



[-- Attachment #1.2: Type: text/html, Size: 2432 bytes --]

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: Strange interaction between ID block property, org-schedule and ical/ics export backend

[Fraga, Eric]

On Monday,  2 Sep 2019 at 10:34, rey-coyrehourcq wrote:
> Hi,
> Sorry, i make a typo in the previous mail, i use the "org-icalendar-export-to-
> ics" method and not the org-caldav method...

Ah, okay.

I should say that I only export appointments (i.e. active time stamps)
to ics so it could be that the export doesn't understand
scheduled/deadline items.

Have you looked at the info manual for org icalendar export?  It does
mention a couple of variables that may affect what you are getting:

,----[ C-h v org-icalendar-use-deadline RET ]
| org-icalendar-use-deadline is a variable defined in ‘ox-icalendar.el’.
| Its value is (event-if-not-todo todo-due)
| 
| Documentation:
| Contexts where iCalendar export should use a deadline time stamp.
| 
| This is a list with possibly several symbols in it.  Valid symbols are:
| 
| ‘event-if-todo’       Deadlines in TODO entries become calendar events.
| ‘event-if-not-todo’   Deadlines in non-TODO entries become calendar events.
| ‘todo-due’            Use deadlines in TODO entries as due-dates.
| 
| You can customize this variable.
`----

,----[ C-h v org-icalendar-use-scheduled RET ]
| org-icalendar-use-scheduled is a variable defined in ‘ox-icalendar.el’.
| Its value is (todo-start)
| 
| Documentation:
| Contexts where iCalendar export should use a scheduling time stamp.
| 
| This is a list with possibly several symbols in it.  Valid symbols are:
| 
| ‘event-if-todo’       Scheduling time stamps in TODO entries become an event.
| ‘event-if-not-todo’   Scheduling time stamps in non-TODO entries become an event.
| ‘todo-start’          Scheduling time stamps in TODO entries become start date.
|                       Some calendar applications show TODO entries only after
|                       that date.
| 
| You can customize this variable.
`----

-- 
: Professor Eric S Fraga, http://www.homepages.ucl.ac.uk/~ucecesf
: PGP/GPG key: 8F5C 279D 3907 E14A 5C29  570D C891 93D8 FFFC F67D
: Use plain text email when possible: https://useplaintext.email/