From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: New exporter and dates in tables Date: Thu, 11 Apr 2013 13:28:00 +0200 Message-ID: <87d2u1s3wf.fsf@gmail.com> References: <87fvz1opiz.fsf@norang.ca> <8761zxwlvn.fsf@gmail.com> <87bo9pntym.fsf@norang.ca> <0604BF00-1FE8-4EAA-A346-C125A5127CAD@gmail.com> <877gkcvm3n.fsf@gmail.com> <173ADFE7-A1FB-4ECB-A78A-C99662A8030F@gmail.com> <87fvyysghk.fsf@gmail.com> <87bo9mh6ex.fsf@bzg.ath.cx> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:36622) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UQFfj-0005zh-B0 for emacs-orgmode@gnu.org; Thu, 11 Apr 2013 07:28:08 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UQFfi-0006GQ-4I for emacs-orgmode@gnu.org; Thu, 11 Apr 2013 07:28:07 -0400 In-Reply-To: <87bo9mh6ex.fsf@bzg.ath.cx> (Bastien's message of "Wed, 10 Apr 2013 15:16:54 +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: Bastien Cc: Bernt Hansen , emacs-orgmode@gnu.org, Carsten Dominik Hello, Bastien writes: > Note that Org 8.0-pre comes with a new export option > `org-export-with-planning' which handles the export of > SCHEDULED / DEADLINE / CLOSED time-stamps. > > This used to be the job of org-export-with-timestamps. > > I guess many people who used (setq org-export-with-timestamps nil) > now want (setq org-export-with-planning nil) and which works well > with (setq org-export-with-timestamps 'inactive). > > So I'm wondering: would the setup above spare us with this exception? > > I know people sometimes throw inactive time-stamps, but those small > indications would better fit in a commented line. > > WDYT? Thinking more about it, I think I need to make some more exceptions anyway. For example timestamps in clock lines and in planning info shouldn't react to `org-export-with-timestamps' (it would be silly to have `org-export-with-planning' set to t and still see nothing because `org-export-with-timestamps' is nil). After all, this exception may not be that exceptional. Regards, -- Nicolas Goaziou