-
Notifications
You must be signed in to change notification settings - Fork 105
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sync issue with items with :SCHEDULED: or :DEADLINE: keywords #33
Comments
I cannot reproduce. Most likely, you have not looked into Here's a sledgehammer solution that will most likely solve the issue: (setq org-icalendar-include-todo t
org-icalendar-use-deadline '(event-if-todo event-if-not-todo todo-due)
org-icalendar-use-scheduled '(event-if-todo event-if-not-todo todo-start)
org-icalendar-with-timestamps t) |
This fixes the issue for me, thanks. |
close? |
No, please, there actually is an issue! I observe the following behaviour since several weeks with growing discomfort: Only by the second sync (exactly as described above) the SCHEDULED time gets converted to an active timestamp and a freshly created property drawer with a new id is inserted above that newly created active timestamp. My settings (perfectly legitimate) are: (setq org-icalendar-include-todo 'all) I follow the org-mode master-branch. Current org-version is: Org-mode version 8.3beta (release_8.3beta-835-g13938b |
If a task has only a date stamp in org then the sync seems to work fine. However, if I have either of the useful :SCHEDULED: or :DEADLINE: keywords in org before the date stamp, then, in the first sync, these events go into the calendar but in the second sync they get removed from the calendar with the claim that they got deleted in org. I guess org-caldav somehow cannot find these kind of events in org after the first sync.
The text was updated successfully, but these errors were encountered: