From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Engster Subject: Timestamps in properties not exported by icalendar exporter Date: Fri, 21 Feb 2014 19:37:10 +0100 Message-ID: <87bny0ia7d.fsf@engster.org> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:34367) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WGuyT-0007yj-CR for emacs-orgmode@gnu.org; Fri, 21 Feb 2014 13:37:31 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WGuyN-0006xx-C9 for emacs-orgmode@gnu.org; Fri, 21 Feb 2014 13:37:25 -0500 Received: from randomsample.de ([5.45.97.173]:47964) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WGuyN-0006tS-1S for emacs-orgmode@gnu.org; Fri, 21 Feb 2014 13:37:19 -0500 Received: from dslc-082-083-058-006.pools.arcor-ip.net ([82.83.58.6] helo=spaten) by randomsample.de with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from ) id 1WGuyG-0007la-Gt for emacs-orgmode@gnu.org; Fri, 21 Feb 2014 19:37:12 +0100 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: emacs-orgmode@gnu.org I have the problem that a certain kind Org entries is not exported by the icalendar exporter, namely those created by the gnus-icalendar package. This package creates Org entries from calendar invites in the following way (I've omitted some of the properties, but you get the idea); ** Some appointment (location) :PROPERTIES: :ICAL_EVENT: t :ID: 040000008200E00074C5B7101A82E00800 :DT: <2013-12-09 Mon 13:00-13:30> :END: Body text These entries show up in the agenda just fine, but the icalendar exporter does not export it because the timestamp is in the properties (the gnus-icalendar package puts it there so that you can easily change it if the organizer decides to change the event and sends a change request). The exporter could of course simply take the first timestamp it finds in the properties, but it could be the wrong one; for instance, there could be a LOGBOOK timestamp before the one in DT. Hence I think it would be nice if you could tell the exporter which property to use as timestamp during export. -David