emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Mark Elston <m_elston@comcast.net>
To: emacs-orgmode@gnu.org
Subject: Re: Status google calendar sync
Date: Wed, 26 Jan 2011 18:51:43 -0800	[thread overview]
Message-ID: <4D40DDBF.10800@comcast.net> (raw)
In-Reply-To: <4D40C1C8.4070909@lbl.gov>

On 1/26/2011 4:52 PM, Arun Persaud wrote:
> Hi
>
>> You are right that googlecl is poorly documented, and worse, it doesn't
>> even work as the documentation says it should.  Try retrieving calendar
>> events with --fields="title,when" and see what happens.  I get the
>> title printed out but the "when" always comes out as None.
>
> my man pages for googlecl don't mention a "fields" options. Doing
>
> "google calendar list when,where,title"
>
> works for me though (using googlecl that comes with openSUSE 11.3).
>

I try this and get absolutely nothing.  Just an empty calendar line.
I am using the latest (0.9.12), BTW.  If you enter

   google --help

part of the help is:

   --fields=FIELDS       Fields to list with list task.


>> However, I have had better luck with the python gdata interface.  The
>> docs aren't much better but I have managed to figure out how to modify
>> an existing event using it.  And, there are examples of how to search
>> for specific events...
>
> cool, do you have this integrated with org? if so could you post the code?

Not yet.  I have just started playing with it so I wanted to get a feel
for how to do some of the basics (which took some playing first).  There
are some really simple examples on the website but for anything more
complicated you need to look at either how the XML is structured or
take a look at JSON info and try to deduce from there what is needed in
the python code.  It isn't always (or even usually) obvious...  At least
it hasn't been for me so far.

>> While using googlecl might be interesting it would probably be simpler
>> to come up with a specific library for doing the things that need to
>> be done directly with gdata (which is what googlecl uses anyway) and
>> calling scripts that make use of this specific library, instead.
>
> I guess one could also use google calendar completely without googlecl
> or gdata, since you can point google at an .ics file to import it into
> google's calendar and Eric's script already handles the other way
> (google->org).

Perhaps, but one of the things I want to do is to share a couple of my
Google calendars with specific groups of people. I have a home, work,
and two different teaching calendars.  If I have an .ics file on my
machine that doesn't help much in the sharing, does it?  I don't know
as I have never used an .ics file for anything yet.

I would like to maintain info about upcoming classes in my org file and,
when things change, update the calendar with the appropriate
information.  Occasionally I have had to reschedule classes, for
example, or break a single session into two sessions.  What I want is
to publish the resulting information after all my org file manipulations
are done so my students can see the results.

Mark

  reply	other threads:[~2011-01-27  2:51 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
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 [this message]
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=4D40DDBF.10800@comcast.net \
    --to=m_elston@comcast.net \
    --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).