From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nick Dokos Subject: Re: Timestamps in properties not exported by icalendar exporter Date: Sat, 22 Feb 2014 08:47:56 -0500 Message-ID: <87zjljgsxf.fsf@gmail.com> References: <87bny0ia7d.fsf@engster.org> <87lhx34h2h.fsf@gmail.com> <877g8nig99.fsf@engster.org> <871tyvz86p.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:37942) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WHCwG-0000pZ-44 for emacs-orgmode@gnu.org; Sat, 22 Feb 2014 08:48:26 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WHCwA-0000HI-40 for emacs-orgmode@gnu.org; Sat, 22 Feb 2014 08:48:20 -0500 Received: from plane.gmane.org ([80.91.229.3]:51740) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WHCw9-0000HD-TO for emacs-orgmode@gnu.org; Sat, 22 Feb 2014 08:48:14 -0500 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1WHCw7-00023C-Fe for emacs-orgmode@gnu.org; Sat, 22 Feb 2014 14:48:11 +0100 Received: from pool-98-110-160-12.bstnma.fios.verizon.net ([98.110.160.12]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 22 Feb 2014 14:48:11 +0100 Received: from ndokos by pool-98-110-160-12.bstnma.fios.verizon.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 22 Feb 2014 14:48:11 +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 Nicolas Goaziou writes: > 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 was confused at first because David has (had?) his own gnus-icalendar package, but I believe he means the gnus-icalendar that is part of gnus. That's probably a bit more official than a third-party package in the wild, but I appreciate Nicolas's desire to control the chaos. It might make more sense to advertise an API/convention/whatever that such packages can use and provide a patch to modify gnus-icalendar accordingly. After all, I presume gnus-icalendar can only be used with gnus, so other mailers will have to have their own icalendar->org. If each picks its own convention, chaos reigns. We just need to come up with the "standard" and advertise it appropriately. Maybe something like this: "provide the starting time/duration information as a scheduled timestamp, and optionally provide everything in properties. The names of the properties should be the names that gnus-icalendar currently uses (explicitly listed out, of course)." >> 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. > If gnus-icalendar is modified as above, then when the agenda is rewritten using org-element, things are not going to break. >> 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. > -- Nick