emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@altern.org>
To: emacs-orgmode@gnu.org
Subject: Re: Re: org-mode and Google Calendar
Date: Sat, 29 Sep 2007 16:21:02 +0200	[thread overview]
Message-ID: <871wchsgc1.fsf@bzg.ath.cx> (raw)
In-Reply-To: <87641ttx8w.fsf@bzg.ath.cx> (Bastien's message of "Sat, 29 Sep 2007 15:30:23 +0200")

Bastien <bzg@altern.org> writes:

>> I just point google calendar to this file. The only problem I have had
>> 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 not
SCHEDULED or DEADLINE. I often use such timestamps and the description
shows them, which looks weird:

  DESCRIPTION:     <2007-12-19 mer>

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 field.
Having to store the location in the description is okay, but I think the
location property is quite usual -- what do people think on this?


  reply	other threads:[~2007-09-29 14:21 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]     ` <3d6808890709280329k7b305ab7qabf2f1c6bda0c275@mail.gmail.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 [this message]
2007-10-04  7:56         ` Carsten Dominik
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

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:

  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=871wchsgc1.fsf@bzg.ath.cx \
    --to=bzg@altern.org \
    --cc=emacs-orgmode@gnu.org \


* 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).