From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: New exporter and dates in tables Date: Tue, 16 Apr 2013 09:48:41 +0200 Message-ID: <874nf6q5k6.fsf@bzg.ath.cx> 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> <87d2u1s3wf.fsf@gmail.com> <8738uxrrtc.fsf@bzg.ath.cx> <87mwt2aefz.fsf@gmail.com> <874nfa34vj.fsf@bzg.ath.cx> <87ehee9vz6.fsf@gmail.com> <87ip3p8mun.fsf@bzg.ath.cx> <87wqs58c7h.fsf@gmail.com> <87ip3p5ipz.fsf@bzg.ath.cx> <87ppxx8bs0.fsf@gmail.com> <871uad5hzv.fsf@bzg.ath.cx> <87haj98avd.fsf@gmail.com> <87vc7p42bt.fsf@bzg.ath.cx> <87sj2s7sti.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:45391) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1US0dD-0003XY-OX for emacs-orgmode@gnu.org; Tue, 16 Apr 2013 03:48:49 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1US0dC-0007F4-De for emacs-orgmode@gnu.org; Tue, 16 Apr 2013 03:48:47 -0400 Received: from mail-wg0-f44.google.com ([74.125.82.44]:33864) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1US0dB-0007Ep-UH for emacs-orgmode@gnu.org; Tue, 16 Apr 2013 03:48:46 -0400 Received: by mail-wg0-f44.google.com with SMTP id a12so162389wgh.35 for ; Tue, 16 Apr 2013 00:48:45 -0700 (PDT) In-Reply-To: <87sj2s7sti.fsf@gmail.com> (Nicolas Goaziou's message of "Sun, 14 Apr 2013 22:36:41 +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: Bernt Hansen , emacs-orgmode@gnu.org, Carsten Dominik Hi Nicolas, Nicolas Goaziou writes: > Bastien writes: > >> Nicolas Goaziou writes: >> >>> We can widen the definition of `standalone': a standalone timestamp is >>> a timestamp belonging to a paragraph that contains only timestamps >>> objects. >> >> Great. If that's possible, then I think that's the best solution. > > The following patch should do that. It comes with tests, but it should > be tested extensively, if only to know if this feature is as useful as > it seems. I think I nailed down the root of the confusion. org-export-with-planning does the job that org-export-with-timestamps used to do. So first of all, org-export-with-timestamps should be an alias to org-export-with-planning so that users who customized org-export-with-timestamps don't have to change their customization: (define-obsolete-variable-alias 'org-export-with-timestamps 'org-export-with-planning "24.4") Today, org-export-with-timestamps does a completely different job, more fine-grained than the old org-export-with-timestamps. I suggest to rename it to org-export-with-individual-timestamps and to use the latest patch you sent, with a default value of t. I expect the next useful value is 'not-standalone. But if someone wants to get rid of time-stamps in tables or in lists, he now can. > Note that another option is to allow all timestamps, put timestamps you > don't want to export in a specific drawer (e.g. "TIME"), and ignore this > drawer during export. Yes, but that requires educating users, which I don't really like. Thanks, -- Bastien