> ,----[ C-h f org-clone-subtree-with-time-shift RET ] > > I find that this exactly what you are describing: I define an entry, > clone it (with weekly shift, for instance) and then delete the > exceptions and maybe add a few extras. If any weekly instance has to > change, I simply change it! Works pretty well and handles all the cases > you mentioned.
There is one important feature lacking in the use of time-shifted clones as a way to generate repeating events: there is nothing to bind individual instances into a collection. A common EVENTID property would allow for the development of tools for handling a whole series as a group to do things like deleting, shifting, and making other changes en masse. It seems like a simple thing to add. Flexibility like this is why I like working in org. I would move my calendar to org if I were not stuck with outlook/exchange at work. I'm still waiting for someone to create the ultimate org/exchange sync solution.
