emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Mark Elston <m_elston@comcast.net>
To: Greg Troxel <gdt@ir.bbn.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Status google calendar sync
Date: Sun, 30 Jan 2011 13:36:46 -0800	[thread overview]
Message-ID: <4D45D9EE.9050704@comcast.net> (raw)
In-Reply-To: <rmibp2yed1u.fsf@fnord.ir.bbn.com>

On 1/30/2011 5:28 AM, Greg Troxel wrote:
>
> Mark Elston<m_elston@comcast.net>  writes:
>> On 1/29/2011 12:44 PM, Greg Troxel wrote:
 >>
>> I have never made use of any .ical/.ics files so this hasn't been an
>> issue for me.  The only UUIDs I am dealing with are google calendar's
>> own internal UUIDs.  I don't know how they compare with other UUIDs.
>
> I suspect, but am 100% not sure, that sending events to google calendar
> via the command-line tools is conceptually similar to exporting to ical
> and doing an import to some ical-style GUI calendar program.

You are probably correct here.  I did some digging into ical and get the
feeling that the ids are the same thing.

>> What I am working on now is a python script to initialize some of the
>> info I have in my org files with info from google (including the google
>> UUID).  Most of this will go into a property drawer.  This drawer can
>> certainly be expanded to contain additional data from other tools as
>> necessary.
>
> I think you're thinking the same problem I didn't articulate very well....
>
>    events in iCalendar/etc. systems (including google calendar) have a
>    UUID, and those systems typically can accept an existing UUID on
>    import
>
>    org events have a UUID, at least after org-mobile-export, and it's
>    "ID" in properties drawer.  I'm not sure if these can be used as-is
>    when exporting via iCalendar.
>
>    someone might end up with the same event in both systems, but without
>    matching UUIDs.  In that case, there needs to be some way to merge
>    events and remember both UUIDs so that future syncing keeps the events
>    merged.

What I have done is to have a property called GOOGLE_UUID to keep track
of that item.  This way, if any other property gets added it probably
won't conflict and I can keep track of google stuff separately.

>> What I would like is to be able to shuffle my schedule in org as it is
>> often a more convenient interface for this than *any* calendar I have
>> used for the kinds of things I have to do.  Once I get the dates/times
>> for individual events the way I want them I would then push them to
>> google (or wherever).  My notes and other useful data stay in org.
>
> Agreed; this is what I would like to do also.  But I would like to also
> be able to change a time in [non-org scheduling program] or add an event
> (perhaps via a mailed iCalendar invitation) and have those flow into
> org.

I am working on the logic to do that right now.  It is easier for me to
work in Python as I am not an elisp expert but I am going to have to
do *some* of this in elisp eventually.

> ical export seems to be present in org, but I found duplicated events
> after multiple exports.  I need to find time to try it more and either
> fix it or construct a good bug report.

I have had some confusion regarding repeated events.  Does this have
anything to do with what you saw?

Mark

  parent reply	other threads:[~2011-01-30 21:36 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-29 14:53 Status google calendar sync 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 [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
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
2011-01-21  8:38 Torsten Wagner
2011-01-21  9:43 ` Ian Barton
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

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=4D45D9EE.9050704@comcast.net \
    --to=m_elston@comcast.net \
    --cc=emacs-orgmode@gnu.org \
    --cc=gdt@ir.bbn.com \
    /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).