Dear all,
James Harkins <jamshark70@qq.com> writes:

> Rasmus <rasmus <at> gmx.us> writes:
>
>> Also check
>> `org-clone-subtree-with-time-shift'.
>
> FWIW, I always create a separate subtree, with a single timestamp, for every
> class session. Advantages:
>
> - Individual status for each session: DONE, POSTPONED or CANCELED.
>
> - If a single class in a series needs to be rescheduled, it's easy.
>
> - I can add notes under the subtree, to plan for the session or note
> important things that happened in class. So then my calendar is not just a
> calendar -- it also helps with content organization. (That IMO is the whole
> point of org-mode: it's not just a calendar!)

I like the idea of `org-clone-subtree-with-time-shift', but wouldn't it
make the parsing of the files slower?

I admit that in the example, this would not have a big impact since
there would be only 9 entries. Nevertheless, I wonder if this can be
considered as a general solution.

In my org files that sum up to 51425 lines (not taking into account the
archives), the creation of the agendas takes minutes to generate. There
are a lot of repeated items with final date¹. I cannot imagine the time
it would take if I would use `org-clone-subtree-with-time-shift'...

My two cents :-)

¹  Like in the case mentioned by Xavier
-- 
Konubinix
GPG Key    : 7439106A
Fingerprint: 5993 BE7A DA65 E2D9 06CE  5C36 75D2 3CED 7439 106A