From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: Timestamps in properties not exported by icalendar exporter Date: Sat, 22 Feb 2014 12:41:02 +0100 Message-ID: <871tyvz86p.fsf@gmail.com> References: <87bny0ia7d.fsf@engster.org> <87lhx34h2h.fsf@gmail.com> <877g8nig99.fsf@engster.org> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:48126) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WHAwp-0000wI-63 for emacs-orgmode@gnu.org; Sat, 22 Feb 2014 06:40:52 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WHAwj-0004JL-KS for emacs-orgmode@gnu.org; Sat, 22 Feb 2014 06:40:47 -0500 Received: from mail-wg0-x229.google.com ([2a00:1450:400c:c00::229]:41816) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WHAwj-0004JH-Br for emacs-orgmode@gnu.org; Sat, 22 Feb 2014 06:40:41 -0500 Received: by mail-wg0-f41.google.com with SMTP id l18so1499839wgh.0 for ; Sat, 22 Feb 2014 03:40:40 -0800 (PST) Received: from selenimh ([91.224.148.150]) by mx.google.com with ESMTPSA id fo6sm4055322wib.7.2014.02.22.03.40.38 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 22 Feb 2014 03:40:39 -0800 (PST) In-Reply-To: <877g8nig99.fsf@engster.org> (David Engster's message of "Sat, 22 Feb 2014 11:38:42 +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 David Engster writes: > Yes, I could do that for my specific setup. But it would be nice if this > stuff could "just work", so that things like Outlook calendar invites > can be directly exported to .ics. AFAIU, we're talking about a third-party package which implements its own UI. We cannot support every UI in the wild. > I mean, those entries show up in the agenda, so I found it rather > surprising that they are completely ignored by the exporter. This is an agenda bug, which probably use a regexp to find timestamps. But timestamps in properties are not valid Org timestamps, per Org syntax. > I think it would make sense if the exporter also looked for > time-stamps in the properties. There are already plenty of locations to use timestamps. We have scheduled, deadline, plain timestamps... I don't think we need more of them. Also, a hook is easy enough to implement in this situation. Regards, -- Nicolas Goaziou