And David Engster writes:
> Google has changed authentication on the new endpoint to
> OAuth. Julien has written an OAuth2 client implementation,
> which is in GNU ELPA, but I didn't have time to look at it
> yet. Not sure when I get to it; I hope someone beats me to it.
Ok, well understood. Than
Jason Riedy writes:
> Google has deprecated the URL in org-caldav, and that old URL
> does not work for me. The new one is documented at
>
> https://developers.google.com/google-apps/calendar/caldav/v2/guide#new_endpoint
>
> Fiddling with the regexp in org-caldav-events-url triggers an
> error
And Eric S. Fraga writes:
> Can you expand on this? I am not sure what you mean by
> endpoint. I use org-caldav-sync several times a day and it
> generally works very well with Google's calendar service.
Google has deprecated the URL in org-caldav, and that old URL
does not work for me. The new
Jason Riedy writes:
> Does anyone have org-caldav working with the new Google endpoint
Can you expand on this? I am not sure what you mean by endpoint. I use
org-caldav-sync several times a day and it generally works very well
with Google's calendar service.
--
: Eric S Fraga (0xFFFCF67D), Em
Does anyone have org-caldav working with the new Google endpoint
or Zimbra? The former errors out (there's an issue on github,
but I don't want a github account to ask there), and the latter
uses a different URL scheme...
Zimbra's URL scheme is
https://server.example.com/dav/username/calendarna
