You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Test Event 1:PROPERTIES::LOCATION: Location 1:END:
<2018-12-06 Thu>
after using either org-gcal-post-at-point or org-gcal-sync, the result is as follows:
* Test Event 1:PROPERTIES::LOCATION: Location 1:LINK: [[https://www.google.com/calendar/event?eid=xxx][Go to gcal web page]]
:ID: xxx
:END:
<2018-12-06 Thu>:PROPERTIES::LOCATION: Location 1:END:
<2018-12-06 Thu>
If, on the other hand, I drop the properties altogether from the entry as follows:
* Test Event 2
<2018-12-06 Thu>
and then run org-gcal-sync, I get the following:
* Test Event 2:PROPERTIES::LINK: [[https://www.google.com/calendar/event?eid=xxx][Go to gcal web page]]
:ID: xxx
:END:
<2018-12-06 Thu>
The Test Event 1 case leaves duplicate events in the local org file (as you can see from the above) but not in the Google calendar. Nevertheless, it is still quite a nuisance. One workaround, that works in the case of Test Event 1, is to just delete the trailing properties and timestamp and re-sync. Another workaround, that works in the case of Test Event 2 is to just add the :LOCATION: property to the updated event after the sync, once the :ID: and :LINK: properties have been added, then re-sync.
Note that I am using the google-calendar-layer (or at least my own working fork of it), as well as multiple calendars. I would gladly dig into this a bit further myself, but I'm afraid my E-Lisp skills are not quite up to the challenge, currently.
The text was updated successfully, but these errors were encountered:
If I add an event such as this one:
after using either
org-gcal-post-at-point
ororg-gcal-sync
, the result is as follows:If, on the other hand, I drop the properties altogether from the entry as follows:
and then run
org-gcal-sync
, I get the following:The
Test Event 1
case leaves duplicate events in the localorg
file (as you can see from the above) but not in the Google calendar. Nevertheless, it is still quite a nuisance. One workaround, that works in the case ofTest Event 1
, is to just delete the trailing properties and timestamp and re-sync. Another workaround, that works in the case ofTest Event 2
is to just add the:LOCATION:
property to the updated event after the sync, once the:ID:
and:LINK:
properties have been added, then re-sync.Note that I am using the google-calendar-layer (or at least my own working fork of it), as well as multiple calendars. I would gladly dig into this a bit further myself, but I'm afraid my E-Lisp skills are not quite up to the challenge, currently.
The text was updated successfully, but these errors were encountered: