From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: New exporter and dates in tables Date: Mon, 12 Aug 2013 07:45:22 +0200 Message-ID: References: <87fvz1opiz.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> <874nf6q5k6.fsf@bzg.ath.cx> <87ob97unyt.fsf@norang.ca> Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\)) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:52693) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V8kwg-0003ih-Qx for emacs-orgmode@gnu.org; Mon, 12 Aug 2013 01:45:39 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1V8kwb-00060a-4U for emacs-orgmode@gnu.org; Mon, 12 Aug 2013 01:45:34 -0400 In-Reply-To: <87ob97unyt.fsf@norang.ca> 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: Bernt Hansen Cc: Bastien , Nicolas Goaziou , emacs-orgmode@gnu.org OK, thank you. - Carsten On 9.8.2013, at 13:02, Bernt Hansen wrote: > Hi Carsten! > > All of my headings are followed by an inactive timestamp. I've started > leaving a blank line before the content for the heading so the inactive > timestamp is not exported when timestamps are disabled with the <:nil > option. This works fine for me. > > Regards, > Bernt > > Carsten Dominik writes: > >> Hi guys, >> >> did you arrive at a conclusion of this thread, or is this still open? >> >> Thanks >> >> - Carsten >> >> On 16.4.2013, at 09:48, Bastien wrote: >> >>> 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