emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ian Barton <lists@manor-farm.org>
To: emacs-orgmode@gnu.org
Subject: Re: Status google calendar sync
Date: Fri, 21 Jan 2011 09:43:56 +0000	[thread overview]
Message-ID: <4D39555C.8050902@manor-farm.org> (raw)
In-Reply-To: <4D3945ED.9060605@gmail.com>

>
> I know some people managed to get a kind of sync running between
> org-mode and google calendar. I would really like to know how this works
> out for them and maybe create a stimulus to write something (I would
> play the beta-tester) on worg.
>
> Ideally, I want to have a no-brainer. I create a new appointment in
> org-mode and a keypress away it should be synced with the google
> calendar. Alternatively, an automatic sync every hour or so would be nice.
>
> On the other side, I wish I could add an appointment on my mobile phone
> and it ends up automatically with the next sync as an appointment in a
> special heading in the org-file (like org-remember, does). From this
> point, I could move it to other locations if I feel so.
>
> I would love to hear how far people got with an approach like describe
> above.
>
Hi Torsten,

I have been playing around with this for a while. I use a Nokia phone, 
but the principle is the same. I have experimented with both syncing 
from my org files to Google and syncing from Google to org.

I don't attempt bi-directional sync, so one side of the sync operation 
is always considered the "master". Initially I tried creating an org 
file from Google calendar by using the python bindings that Google 
provides. This worked pretty well - basically the org file is re-created 
each time I synced with Google.

However, almost without exception, I will be at my computer when I want 
to create an appointment. So, for me it makes sense to create my 
appointments in org and export them to Google. At the moment I have a 
cron job that exports my appointments as an ics file on my server and 
Google reads this. Luckily, I don't have complicated appointments. They 
tend to be single events, or weekly recurrences which org handles OK.

The one useful thing I am missing at the moment is the ability to set 
reminders in Google Calendar. I find these very useful as Google will 
send me an SMS message. In fact I often create appointments, which are 
really just reminders! I am planning to implement this  by creating 
reminders as org Properties and then using them to create the Google 
reminder.

Since I am still on page one of the "Complete Idiots Guide to elisp", I 
plan to do this in Python, which has some nice libraries for creating 
ics files.

Ian.

  reply	other threads:[~2011-01-21  9:44 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-21  8:38 Status google calendar sync Torsten Wagner
2011-01-21  9:43 ` Ian Barton [this message]
2011-01-21 15:22   ` Nick Dokos
2011-01-21 18:19   ` Arun Persaud
2011-01-21 23:58     ` Eric S Fraga
2011-01-25 20:21       ` Arun Persaud
2011-01-26 12:33         ` Eric S Fraga
2011-01-26 23:29           ` Mark Elston
2011-01-27  0:52             ` Arun Persaud
2011-01-27  2:51               ` Mark Elston
2011-01-27 19:43                 ` Arun Persaud
2011-01-27 21:57                 ` Arun Persaud
2011-01-28 16:13                   ` Eric S Fraga
2011-01-31 19:03                     ` Bastien
2011-01-29  1:28 ` Greg Troxel
2011-01-29 12:45   ` Eric S Fraga
  -- strict thread matches above, loose matches on Subject: below --
2011-01-29 14:53 Torsten Wagner
2011-01-29 19:38 ` Mark Elston
2011-01-29 20:44   ` Greg Troxel
2011-01-30  4:36     ` Mark Elston
2011-01-30 13:28       ` Greg Troxel
2011-01-30 14:09         ` Eric S Fraga
2011-01-30 20:43           ` Arun Persaud
2011-01-30 21:36         ` Mark Elston
2011-01-30 14:01       ` Eric S Fraga
2011-01-30  1:21 ` Eric S Fraga
2011-01-31 10:02   ` Christopher Witte
2011-02-01  9:07     ` Eric S Fraga
2011-02-01  0:54 Torsten Wagner
2011-02-01  9:12 ` Eric S Fraga
2011-02-01 22:44 ` Sven Bretfeld
2011-02-02  5:15   ` Torsten Wagner
2011-02-02  8:30     ` Konrad Hinsen
2011-02-14 21:39       ` Marcelo de Moraes Serpa
2011-02-15  7:18         ` Konrad Hinsen
2011-02-15 16:37           ` Marcelo de Moraes Serpa
2011-02-15 16:43             ` Marcelo de Moraes Serpa
2011-02-15 16:55               ` Bastien
2011-06-10 16:58           ` Stephen Eglen
2011-06-10 17:04             ` Arun Persaud
2011-06-10 18:34               ` Stephen Eglen
2011-06-10 19:09                 ` Arun Persaud
2011-06-11 13:25                   ` Philipp Haselwarter
2011-06-11 18:38                     ` Nick Dokos
2011-06-15 19:00                       ` Eric S Fraga
2011-06-11 17:32                 ` Niels Giesen
2011-06-30 16:14                   ` Bastien
2011-06-15 18:45                 ` Eric S Fraga
     [not found]                 ` <87hb7rory9.fsf@ucl.ac.uk>
2011-06-16 12:13                   ` Stephen Eglen

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  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=4D39555C.8050902@manor-farm.org \
    --to=lists@manor-farm.org \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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).