emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Fabrice Popineau <fabrice.popineau@supelec.fr>
To: "Doyley, Marvin M." <mdoyley@ur.rochester.edu>,
	"emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Pushing and pulling to google calendar
Date: Thu, 3 Jul 2014 00:23:50 +0200	[thread overview]
Message-ID: <CAFgFV9MGdCiRHc=-WxnYuwH1WE0axsF7eyBdYmHxJ56h3pd0PA@mail.gmail.com> (raw)
In-Reply-To: <87r426b3h0.fsf@engster.org>

[-- Attachment #1: Type: text/plain, Size: 1138 bytes --]

Am I missing something if I cite
which is using the v3 Google Calendar api.
Still lacks of true bidirectional sync, but that could happen.
Seems nicely written.


2014-06-30 21:29 GMT+02:00 David Engster <deng@randomsample.de>:

> Marvin M. Doyley writes:
> > Is there a way to sync org-agenda with google calendar so that I can
> > exploit googles calendar reminder.
> org-caldav[1] works with Google Calendar on the old, deprecated CalDAV
> endpoint (https://www.google.com/calendar/dav). I hear that the endpoint
> is still working for some people, so maybe you are in luck.
> Moving to the new endpoint would require OAuth authentication, which
> shouldn't be hard to add using the oauth-library in ELPA, but since I
> don't use Google, I'm lacking motivation...
> -David
> https://github.com/dengste/org-caldav

Fabrice Popineau
Département Informatique
3, rue Joliot Curie
91192 Gif/Yvette Cedex
Tel direct : +33 (0) 169851950
Standard : +33 (0) 169851212

[-- Attachment #2: Type: text/html, Size: 1878 bytes --]

  reply	other threads:[~2014-07-02 22:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-29 13:24 Pushing and pulling to google calendar Doyley, Marvin M.
2014-06-29 16:38 ` Jorge A. Alfaro-Murillo
2014-06-29 21:39   ` Parnell Springmeyer
2014-06-30  1:32     ` Jorge A. Alfaro-Murillo
2014-06-30 19:19       ` Doyley, Marvin
2014-06-30 19:29 ` David Engster
2014-07-02 22:23   ` Fabrice Popineau [this message]
2015-06-13 20:19     ` rene

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAFgFV9MGdCiRHc=-WxnYuwH1WE0axsF7eyBdYmHxJ56h3pd0PA@mail.gmail.com' \
    --to=fabrice.popineau@supelec.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=mdoyley@ur.rochester.edu \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).