From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bernt Hansen Subject: Re: New exporter and dates in tables Date: Mon, 08 Apr 2013 07:27:13 -0400 Message-ID: <87bo9pntym.fsf@norang.ca> References: <87fvz1opiz.fsf@norang.ca> <8761zxwlvn.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from eggs.gnu.org ([208.118.235.92]:46046) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UPAEN-0006ZH-BU for emacs-orgmode@gnu.org; Mon, 08 Apr 2013 07:27:26 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UPAEF-0005VL-Sa for emacs-orgmode@gnu.org; Mon, 08 Apr 2013 07:27:23 -0400 Received: from mho-03-ewr.mailhop.org ([204.13.248.66]:56043 helo=mho-01-ewr.mailhop.org) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UPAEF-0005VA-QC for emacs-orgmode@gnu.org; Mon, 08 Apr 2013 07:27:15 -0400 In-Reply-To: <8761zxwlvn.fsf@gmail.com> (Nicolas Goaziou's message of "Mon, 08 Apr 2013 08:57:00 +0200") 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: Nicolas Goaziou Cc: emacs-orgmode@gnu.org Nicolas Goaziou writes: > Bernt Hansen writes: > >> I have subtrees with inactive timestamps in the text indicating when >> something occurred. I normally don't want to export these. But I think >> any table data that includes inactive timestamps should be an exception >> to this ... otherwise you get output tables with blank cells where the >> meaningful timestamp data would be. > > I understand. > > So what exactly should be this exception? Should export ignore <:nil > option in a whole table, or only when a table cell contains a single > timestamp? IOW, how would it behaves in the following table: > > | [2013-04-04 Thu] | Lunch at [2013-04-04 Thu] ] | > > when `org-export-with-timestamps' is either nil or `active'? I think keeping it simple is best. If there is an inactive timestamp in a table then it should be exported (I consider everything in a table as data). > > Also, this must be documented. Exceptions tend to accumulate a lot and > make the global behaviour unpredictable. Would you mind providing an > explanation to this, which would fit in `org-export-with-timestamps' > docstring? > Sure I can do that. I will follow up with a patch in this thread this week after the behaviour has been determined. Regards, Bernt