From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: Re: org-mode and Google Calendar Date: Thu, 4 Oct 2007 09:56:19 +0200 Message-ID: <403a8bd9e84288d3a69dbdee1fc2dc82@science.uva.nl> References: <87d4w3s1pb.fsf@myhost.localdomain> <87abr6zwmg.fsf@bzg.ath.cx> <87641ttx8w.fsf@bzg.ath.cx> <871wchsgc1.fsf@bzg.ath.cx> Mime-Version: 1.0 (Apple Message framework v624) Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1IdLZC-00065t-A8 for emacs-orgmode@gnu.org; Thu, 04 Oct 2007 03:56:18 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IdLZA-00065T-GK for emacs-orgmode@gnu.org; Thu, 04 Oct 2007 03:56:17 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IdLZA-00065Q-Bg for emacs-orgmode@gnu.org; Thu, 04 Oct 2007 03:56:16 -0400 Received: from korteweg.uva.nl ([146.50.98.70]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1IdLZ9-00040v-Qq for emacs-orgmode@gnu.org; Thu, 04 Oct 2007 03:56:16 -0400 In-Reply-To: <871wchsgc1.fsf@bzg.ath.cx> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Bastien Cc: emacs-orgmode@gnu.org On Sep 29, 2007, at 16:21, Bastien wrote: > Bastien 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? ok. > > 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> 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 > 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? Yes, now is the time, and this will be in 5.11. Thanks. - Carsten