emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Arun Persaud <apersaud@lbl.gov>
To: emacs-orgmode@gnu.org
Subject: Re: Status google calendar sync
Date: Tue, 25 Jan 2011 12:21:42 -0800	[thread overview]
Message-ID: <4D3F30D6.7020703@lbl.gov> (raw)
In-Reply-To: <87hbd124ih.fsf@pinto.chemeng.ucl.ac.uk>

Hi

On 01/21/2011 03:58 PM, Eric S Fraga wrote:
> I also have been syncing between my Google calendar and org.  A while
> back, I posted this message onto this list:
> 
> http://article.gmane.org/gmane.emacs.orgmode/26848
> 
> but check out later messages in the thread for an updated awk script.

I had problems using wget, since we don't use google login, but get
redirected to our institute from google, so I would have to use
--load-cookie but couldn't really figure it out... however using
googlecl seems to work fine, so I'm also using this to download the entries

> This dealt with converting a Google calendar into an org file.  I still
> use this.
> 
> For the other route, org to Google, I use the googlecl (command line)
> interface:
> 
> http://article.gmane.org/gmane.emacs.orgmode/27214

don't really know that much lisp, but I guess you add the entries
directly to google when you create them via org-capture? What happens if
you later edit an entry, say change the time/date? This is something I
do very often and I would need google to reflect those changes. I also
only want to export certain tags and entries that have a date-range
(e.g. start and stop time), but I guess that could be easily arranged in
the lisp function that you wrote?

Arun

  reply	other threads:[~2011-01-25 20:21 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 [this message]
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=4D3F30D6.7020703@lbl.gov \
    --to=apersaud@lbl.gov \
    --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).