org-caldav
org-caldav copied to clipboard
Syncing multiple calendars using org-caldav-select-tags, items at different levels/depths don't respect tags
I am matching headline tags to certain calendars like so:
(setq org-caldav-calendars '((:calendar-id "new-bills"
:select-tags ("cal_new_bills"))
(:calendar-id "new-fam"
:select-tags ("cal_new_fam"))))
As long as everything is at the same depth / level, it works as intended (example):
** foo :tag1: ** bar :tag2: ** baz :tag1:
However when one of the levels is different, like so:
** foo :tag1: ** bar :tag2: *** baz :tag1:
All hell breaks loose and everything gets synced to every other calendar. It's not even like it inherits the tags by branch. I double checked and I do have property inheritance in org turned off (org-use-property-inheritance nil).
Am I going crazy? Or can anyone else reproduce this behavior?
Did anyone figure this out?
Hi @Cumol,
I don't think I ever did. Which is quite unfortunate, as I still have not found any solution that really works to keep my Org and calendar in sync.
At first I tried putting calendar events into a separate Org file at a consistent level. This worked (for org-caldav), but became inconvenient because now I have two different files to maintain in parallel...
Eventually I think this led me to end my experiments with org-caldav altogether, and I never went back.
I am not sure how well this project is maintained here any more. I did find a fork by grauschnabel here that seems to be (slightly) better maintained, and perhaps even they share (some? all? I can't tell) patches back and forth, but it seems to me maybe the code is diverging now. There is a thread over there where he sort of reluctantly halfway takes on maintainership (but not really?). So the situation is a bit of a mess as far as I can tell, unfortunately.
Keep in mind that I have not actively looked into any of this in some time. However I still vaguely keep my finger on the pulse in hopes I can still use this some day. So if you learn anything, please report back!
Maybe I should move (or cross post, etc.) this Issue over to grauschnabel repository?
I really wish that everyone's effort could be combined into one place... But maybe no one seems to wish to step up as maintainer so far.