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 14:44:02 +0100 Message-ID: <87sirbxnx9.fsf@gmail.com> References: <87bny0ia7d.fsf@engster.org> <87lhx34h2h.fsf@gmail.com> <877g8nig99.fsf@engster.org> <871tyvz86p.fsf@gmail.com> <8738jbi8tm.fsf@engster.org> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:37481) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WHCrr-00081H-9w for emacs-orgmode@gnu.org; Sat, 22 Feb 2014 08:43:52 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WHCrl-0007NZ-Oy for emacs-orgmode@gnu.org; Sat, 22 Feb 2014 08:43:47 -0500 Received: from mail-we0-x22d.google.com ([2a00:1450:400c:c03::22d]:49801) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WHCrl-0007NV-Ha for emacs-orgmode@gnu.org; Sat, 22 Feb 2014 08:43:41 -0500 Received: by mail-we0-f173.google.com with SMTP id x48so3379475wes.32 for ; Sat, 22 Feb 2014 05:43:40 -0800 (PST) Received: from selenimh ([91.224.148.150]) by mx.google.com with ESMTPSA id bm8sm25121553wjc.12.2014.02.22.05.43.39 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 22 Feb 2014 05:43:39 -0800 (PST) In-Reply-To: <8738jbi8tm.fsf@engster.org> (David Engster's message of "Sat, 22 Feb 2014 14:19:17 +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: > It's these multitude of timestamp locations which makes changing the > timestamp of an existing entry through Elisp so tedious (I had to deal > with that in org-caldav) The number of locations may be daunting but all of them make sense actually. Also, I don't think it is really difficult to change a timestamp through Elisp, due to specialized functions (e.g. `org-schedule'). Anyway, if you think this area can be improved, feel free to make suggestions. > so using a property for it seemed like a good idea. This has been discussed a few times on this ML already. Carsten's argument is that new users shouldn't have to deal with hidden data, like property drawers, for such basic features. IMO, it also have an advantage from an implementation POV: important timestamps are located right below the headline, whereas a property drawer can be found anywhere in the whole section. > Anyway, I understand your reasoning, and I guess we should change how > gnus-icalendar generates its Org entries. I think so, too. Regards, -- Nicolas Goaziou