Open nshan651 opened 4 months ago
Org-caldav does not work with the event-if-todo
and event-if-not-todo
settings.
The problem is that ox-icalendar will export the Org entry as multiple distinct icalendar entries (separate events for the SCHEDULED and DEADLINE). This is problematic for bidirectional sync. In particular, org-caldav assumes a 1-to-1 mapping between Org and Icalendar IDs, and things will break when this assumption is violated.
See this issue for related discussion: https://github.com/dengste/org-caldav/issues/267
On Org-caldav side, we should document the incompatibility with these settings; issue warnings/errors when they are detected; and implement missing features for todo-due
and todo-start
(in particular recurring todos) so that users don't resort to the event-if-todo
setting.
Hi, I was wondering if there was a way to automatically add SCHEDULED/DEADLINE properties when importing cal events to org mode. I am able to easily do it the other way around, where org mode exports the events and prepends "S:" or "D:" to the event on my nextcloud calendar.
Ideally, it would be nice to be able to add "S:" or "D:" to remote calendar events and then for them to get properly inserted in my inbox.org. For example, if on nextcloud I added the following:
Then after syncing, my inbox.org would show this TODO item:
I'm pretty sure this functionality would be handled by org-icalendar, but I'm having trouble finding info on customizing the import behavior. Any suggestions or resources on this would be greatly appreciated :)
Just to be thorough, here's my current config:
Thanks!