From: Carsten Dominik <email@example.com>
To: Bastien <firstname.lastname@example.org>
Subject: Re: Re: org-mode and Google Calendar
Date: Thu, 4 Oct 2007 09:56:19 +0200 [thread overview]
Message-ID: <email@example.com> (raw)
On Sep 29, 2007, at 16:21, Bastien wrote:
> Bastien <firstname.lastname@example.org> writes:
>>> I just point google calendar to this file. The only problem I have
>>> is with google calendars timezone handling.
> Talking about the .ics export, I find the new DESCRIPTION very useful.
> But maybe org-trim could be used here, so that leading and trailing
> whitespaces are stripped away?
> DESCRIPTION: \nAAAI Spring Symposium - March 26-28, 2008, Stanford
> University,\nCalifornia - Submission deadline:
> And maybe this description field could also skip timestamps that are
> SCHEDULED or DEADLINE. I often use such timestamps and the description
> shows them, which looks weird:
> DESCRIPTION: <2007-12-19 mer>
Not sure about that, how to decide what is important and what not?
> Last but not least: now that we have properties, it would be very nice
> to be able to export a :LOCATION: property into the LOCATION vCal
> Having to store the location in the description is okay, but I think
> location property is quite usual -- what do people think on this?
Yes, now is the time, and this will be in 5.11.
next prev parent reply other threads:[~2007-10-04 7:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-28 7:12 org-mode and Google Calendar Cezar
2007-09-28 9:12 ` Leo
2007-09-28 9:49 ` Rick Moynihan
[not found] ` <email@example.com>
2007-09-28 10:30 ` Fwd: " Tim O'Callaghan
2007-09-28 11:41 ` Egli Christian (KIRO 41)
2007-09-28 14:42 ` Bastien
2007-09-28 14:35 ` Bastien
2007-09-28 14:40 ` Leo
2007-09-28 14:58 ` Bastien
2007-09-28 18:16 ` Cezar
2007-09-29 9:07 ` Vagn Johansen
2007-09-29 13:30 ` Bastien
2007-09-29 14:21 ` Bastien
2007-10-04 7:56 ` Carsten Dominik [this message]
2007-10-04 10:44 ` Bastien
2007-10-04 12:30 ` Giovanni Ridolfi
2008-04-23 15:12 ` Adam Spiers
2007-10-01 3:18 ` T. V. Raman
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).