emacs-orgmode
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [O] syncing with google calendar, file changed on disk


From: Nick Dokos
Subject: Re: [O] syncing with google calendar, file changed on disk
Date: Thu, 13 Sep 2012 11:39:56 -0400

Tyler Smith <address@hidden> wrote:

> Hi,
> 
> Following the instructions from Worg (
> http://orgmode.org/worg/org-tutorials/org-google-sync.html ), I've set
> a cron job to download my google calendar, and use Eric Fraga's awk
> script to convert it into google.org for inclusion in my agenda. This
> works fine, and is currently my only syncing option as my access to
> other web services (git, dropbox etc) is blocked at my workplace.
> 
> One small issue: the google calendar file changes regularly, even when
> I haven't added or modified any appointments. As a consequence, I am
> interrupted by Emacs reminding me that google.org has changed on disk,
> and I need to respond before I can continue to browse my agenda. This
> isn't a big deal, but maybe one of you know how to eliminate this
> problem?
> 
> For the record, the sort of changes that I see are this:
> 
> ~/.emacs.d/org$ diff google.org google.org-old
> 488c488
> < ACTION:EMAIL
> ---
> > ACTION:DISPLAY
> 490,491d489
> < SUMMARY:Alarm notification
> < ATTENDEE:mailto:address@hidden
> 495c493
> < ACTION:DISPLAY
> ---
> > ACTION:EMAIL
> 496a495,496
> > SUMMARY:Alarm notification
> > ATTENDEE:mailto:address@hidden
> 
> 
> It seems the ACTION line switches back and forth between DISPLAY and
> EMAIL. I don't understand the ics format to know what this means.
> 
> I have searched the mailing list and stackoverflow, but if this has
> come up before I missed it. Thanks for your help,
> 

The brute force approach: make the cron job download to a different
file, diff the two and if the diff is just
ACTION:EMAIL<-->ACTION:DISPLAY lines and Alarm notification crud, then
throw away the downloaded file. If the diff is different, move the
downloaded file to google.org.

If you go this way, you might want to play around with different diff
formats to see which one is the easiest to parse for the minimal diff(s)
above.

Nick



reply via email to

[Prev in Thread] Current Thread [Next in Thread]