From: Nick Dokos <nicholas.dokos@hp.com>
To: lists@manor-farm.org
Cc: nicholas.dokos@hp.com, emacs-orgmode@gnu.org
Subject: Re: Status google calendar sync
Date: Fri, 21 Jan 2011 10:22:59 -0500 [thread overview]
Message-ID: <8577.1295623379@gamaville.dokosmarshall.org> (raw)
In-Reply-To: Message from Ian Barton <lists@manor-farm.org> of "Fri, 21 Jan 2011 09:43:56 GMT." <4D39555C.8050902@manor-farm.org>
Ian Barton <lists@manor-farm.org> wrote:
> ...
> Since I am still on page one of the "Complete Idiots Guide to elisp", I
> plan to do this in Python, which has some nice libraries for creating
> ics files.
>
On a loosely-related note, I find myself in the unfortunate position of
being the target of Outlook-generated appointment emails (including a
calendar attachment). In self-defense, I have begun looking at having
these things automatically added to my org appointments, but I have had
trouble with the emacs icalendar library (in particular, timezone
handling: a critical item for me, since these appts are generated from
various timezones and the included ics files have a bewildering variety
of timezone specs in them - I blame M$ for this :) ).
So I just wanted to point out three things:
o there *is* an emacs elisp library to handle icalendar files.
o I think it is buggy.
o using the Python libraries is a great way to figure out where the
elisp library goes wrong (assuming I'm right and that it *is* going
wrong somewhere) and possibly fixing it.
Thanks for pointing the Python libraries out. If you get somewhere with
them, maybe you can fix the emacs icalendar library too: it might be
just what you need to expand your elisp skills.[fn:1]
Thanks,
Nick
Footnotes:
[fn:1] Tom Sawyer would be proud of me ;-) I find myself pressed for
time and with too many things to do, so it's not clear when (or even if)
I would be able to work on this.
next prev parent reply other threads:[~2011-01-21 15:53 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 [this message]
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
-- 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=8577.1295623379@gamaville.dokosmarshall.org \
--to=nicholas.dokos@hp.com \
--cc=emacs-orgmode@gnu.org \
--cc=lists@manor-farm.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).