From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: nicholas.dokos@hp.com
Cc: emacs-orgmode@gnu.org, Philipp Haselwarter <philipp.haselwarter@gmx.de>
Subject: Re: Status google calendar sync
Date: Wed, 15 Jun 2011 20:00:35 +0100 [thread overview]
Message-ID: <878vt2q5rg.fsf@ucl.ac.uk> (raw)
In-Reply-To: <4788.1307817530@alphaville.dokosmarshall.org> (Nick Dokos's message of "Sat, 11 Jun 2011 14:38:50 -0400")
[-- Attachment #1: Type: text/plain, Size: 722 bytes --]
Nick Dokos <nicholas.dokos@hp.com> writes:
> Philipp Haselwarter <philipp.haselwarter@gmx.de> wrote:
Nick & Philipp,
>> Unfortunately, both the awk script and the org-export-icalendar seem to
>> have quite a hard time with repeating entries.
Yes. I have extended my awk script to cater for ical events that span
days which does appear to work (to some degree). See updated version
attached. This does not handle generic repeated events unfortunately,
but mostly because I'm not sure what the ical format for these might be
(and have been too lazy to look into it). If you have a good example
(or set of examples) of ical calendar entries that describe repeated
events, I'm happy to work on the awk script further.
[-- Attachment #2: ical 2 org awk script --]
[-- Type: application/x-awk, Size: 7490 bytes --]
[-- Attachment #3: Type: text/plain, Size: 2187 bytes --]
[...]
> I agree - I have been thinking (unfortunately mostly only thinking)
> about it and it seems to me that many of the pieces are there, but there
> is a non-trivial amount of work to do this and do it right:
>
> o icalendar.el should be the basis of this, but unfortunately, it is too
> closely tied to the diary (and is incomplete or buggy in various
> ways).
it would indeed be nice to have an Emacs solution to the google -> org
step.
[...]
> o These converters are ripe for what Kernighan and Plauger call a
> "left-corner" development approach: just bite the smallest useful
> subset and add features as needed, deliberately and carefully. Both
> the current implementation of org-icalendar and Eric F.'s awk script
> would be useful in this respect: they basically cover the basic
> functionality needed (but perhaps not completely, as Philipp points
> out).
In some sense, this is indeed my modus operandum but it's not
necessarily the best approach after a while...
> BTW, the reason I've become interested in this is that recently I
> started being bombarded with meeting invitations generated from (what
> else?) M$ Outlook. My former method of adding the invitations to my
> Org
yes, I am seeing the same thing; I would love to have an automated or
semi-automated procedure to take these things in gnus and create a
capture event. I look forward to seeing what you have been up to in
this respect!
[...]
> turns-you-to-stone-if-you-look-at-it-ugly) and there are bugs (the most
> serious of which is the icalendar timezone stuff that I referred to in a
> recent thread). I'm trying to fixg the bugs and am working on the
> back-end usability stuff in order to survive the onslaught - but the
> icalendar stuff in the middle is likely to remain unspeakably ugly in
> the foreseeable future - I just have no time for it.
time zones are a nightmare, especially with respect to Google.
> So if anybody is interested, I hope this is useful as a starting
> point.
Very interested and happy to contribute as much as I can!
--
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.50.1
: using Org-mode version 7.5 (release_7.5.391.gfaccb.dirty)
next prev parent reply other threads:[~2011-06-15 19:00 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-01 0:54 Status google calendar sync 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 [this message]
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
-- 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-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=878vt2q5rg.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--cc=emacs-orgmode@gnu.org \
--cc=nicholas.dokos@hp.com \
--cc=philipp.haselwarter@gmx.de \
/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).