From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: Agenda ical export omissions: sexp, hour-in-headline Date: Thu, 21 Aug 2014 11:17:45 +0200 Message-ID: <8761hmfbgm.fsf@nicolasgoaziou.fr> References: <87y4ujcs7d.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:32908) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XKOUg-0000Az-ET for emacs-orgmode@gnu.org; Thu, 21 Aug 2014 05:17:28 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XKOUW-0006Hm-6c for emacs-orgmode@gnu.org; Thu, 21 Aug 2014 05:17:18 -0400 Received: from relay6-d.mail.gandi.net ([2001:4b98:c:538::198]:37182) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XKOUW-0006HY-05 for emacs-orgmode@gnu.org; Thu, 21 Aug 2014 05:17:08 -0400 In-Reply-To: <87y4ujcs7d.fsf@gmail.com> (Tory S. Anderson's message of "Wed, 20 Aug 2014 07:32:06 -0400") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: "Tory S. Anderson" Cc: orgmode list Hello, torys.anderson@gmail.com (Tory S. Anderson) writes: > I have a shell function that exports my agenda to an ical file and > uploads it for Google to read; however, there seem to be a couple > glaring omissions from the ical. Here's the bash line that works over > my agenda for export: > > emacs --batch --user $USER --eval "(progn (org-agenda-list nil nil 'year) (org-icalendar-combine-agenda-files))" > > It skips the following sort of agenda entries: > > *** 09:05-09:55 CS 7637 Weekly Class @ Klaus 2447 > <%%(org-class 2014 8 18 2014 12 12 1)> > > and: > > %%(org-anniversary 2015 03 26) Glory %d Birthday > > So, it doesn't seem to ical-ify sexp dates, and it doesn't seem to do > times (09:05-09:55) in the headers. Is there anything to be done for > this? I've just discovered the agenda power of these mighty functions > but will be limited in my use of them if they can't be exported. Times in the header are not Org syntax, you could use an Org timestamp instead. Also, `icalendar' back-end uses `icalendar-export-region' internally, which doesn't support Sexp-entries (see *icalendar-errors* buffer). Regards, -- Nicolas Goaziou