From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: Re: org-mode and Google Calendar Date: Sat, 29 Sep 2007 16:21:02 +0200 Message-ID: <871wchsgc1.fsf@bzg.ath.cx> References: <87d4w3s1pb.fsf@myhost.localdomain> <87abr6zwmg.fsf@bzg.ath.cx> <87641ttx8w.fsf@bzg.ath.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1IbdBt-0006Xx-PQ for emacs-orgmode@gnu.org; Sat, 29 Sep 2007 10:21:09 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IbdBt-0006X6-3t for emacs-orgmode@gnu.org; Sat, 29 Sep 2007 10:21:09 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IbdBs-0006Wx-Vg for emacs-orgmode@gnu.org; Sat, 29 Sep 2007 10:21:09 -0400 Received: from hu-out-0506.google.com ([72.14.214.236]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1IbdBs-0007M2-MC for emacs-orgmode@gnu.org; Sat, 29 Sep 2007 10:21:08 -0400 Received: by hu-out-0506.google.com with SMTP id 23so1683585huc for ; Sat, 29 Sep 2007 07:21:07 -0700 (PDT) In-Reply-To: <87641ttx8w.fsf@bzg.ath.cx> (Bastien's message of "Sat, 29 Sep 2007 15:30:23 +0200") 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: emacs-orgmode@gnu.org 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? 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? -- Bastien