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: Sat, 29 Jan 2011 20:36:14 -0800	[thread overview]
Message-ID: <4D44EABE.5070203@comcast.net> (raw)
In-Reply-To: <rmi62t7fnis.fsf@fnord.ir.bbn.com>

On 1/29/2011 12:44 PM, Greg Troxel wrote:
>
> Mark Elston<m_elston@comcast.net>  writes:
>
>    [google calendar]
>
>> I wasn't all that keen on it at first but I really got to like it when
>> I was able to update my calendar from my phone or my laptop or my
>> desktop at work and all three would see it.
>>
>> When I found I could create multiple calendars and share *some* of them
>> I really started to enjoy the idea of a central server for my calendar
>> data.
>
> You are blurring having a calendar server and being forced into sharing
> your data with google because of using non-free software that is
> crippled by not being able to set the server URL.

I pointed out in a different thread that the software I use doesn't
*require* syncing with google, but can work very nicely as an offline
calendar.  I use the google server for the reasons I gave.

>> ...
>
> org syncing with a calendar server makes a lot of sense to me, but again
> that's separate from a "the only usable calendar server is google".
>

That wasn't my intent.  I use google since it is convenient and
available everywhere I have a network connection (or 3G with my
phone).  If another service came along that fit my needs as well or
better I would certainly take a look at it.

>
> I think the only tricky part is somehow push UUIDs during scyning, and
> then you'll need an operation to merge an org event and an ical event
> with different UUIDs and remember the foreign UUID for the next sync.

I'm not sure what you mean by this.

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

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.

That is what I will be working on as I have the time.

Mark

  reply	other threads:[~2011-01-30  4: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 [this message]
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
  -- 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=4D44EABE.5070203@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).