From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: New exporter and dates in tables Date: Sat, 13 Apr 2013 19:33:17 +0200 Message-ID: <87ehee9vz6.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> <87d2u1s3wf.fsf@gmail.com> <8738uxrrtc.fsf@bzg.ath.cx> <87mwt2aefz.fsf@gmail.com> <874nfa34vj.fsf@bzg.ath.cx> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:48998) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UR4KJ-0004xW-Ha for emacs-orgmode@gnu.org; Sat, 13 Apr 2013 13:33:24 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UR4KI-0005U1-Fw for emacs-orgmode@gnu.org; Sat, 13 Apr 2013 13:33:23 -0400 In-Reply-To: <874nfa34vj.fsf@bzg.ath.cx> (Bastien's message of "Sat, 13 Apr 2013 16:02:56 +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 Bastien writes: > I would find it both cleaner and more useful for users to extend > `org-export-with-timestamps' with three choices: > > 'inactive-not-standalone > 'active-not-standalone > 'not-standalone This is a different idea. The change would happen at the exporter level, not at parser's. > When set to 'not-standalone, it means export time-stamps except > "standone time-stamps", i.e. those who are alone on a line. Well, parsing is not line based, and "a timestamp alone on a line" doesn't mean much. Though, "a timestamp alone in a paragraph" is much easier to translate. IOW: <2013-04-13 Sat> is not a standalone timestamp (use M-q). but, <2013-04-13 Sat> is a standalone timestamp. > That's the set-up most users will want after t, it fits the habits > that Bernt has been describing, and it's useful for users who wants to > get rid of the planning-like active time-stamp right below the > headline. > > Also, it's easier to explain users how to set this up (through > the docstring) than to explain why time-stamps are not removed in > tables with (setq org-export-with-timestamps nil). If we agree to the "alone in a paragraph" part, I can implement it. But we still need exceptions for clocks and timestamps (i.e., ignore `org-export-with-timestamps' value when `org-export-with-planning' or `org-export-with-clocks' is non-nil). Regards, -- Nicolas Goaziou