From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: [new exporter] adhere org-export-date-timestamp-format? Date: Wed, 09 Jan 2013 16:29:56 +0100 Message-ID: <87wqvm2x3f.fsf@gmail.com> References: <877gpj3raa.fsf@pank.eu> <87623stdza.fsf@bzg.ath.cx> <87bod2637u.fsf@gmail.com> <8738yeh6ts.fsf@bzg.ath.cx> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:58484) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TsxfD-0001gU-1z for emacs-orgmode@gnu.org; Wed, 09 Jan 2013 10:34:00 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TsxfB-00012o-Po for emacs-orgmode@gnu.org; Wed, 09 Jan 2013 10:33:58 -0500 Received: from mail-wg0-f50.google.com ([74.125.82.50]:39495) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TsxfB-00012d-KR for emacs-orgmode@gnu.org; Wed, 09 Jan 2013 10:33:57 -0500 Received: by mail-wg0-f50.google.com with SMTP id es5so1053643wgb.17 for ; Wed, 09 Jan 2013 07:33:56 -0800 (PST) In-Reply-To: <8738yeh6ts.fsf@bzg.ath.cx> (Bastien's message of "Sun, 06 Jan 2013 12:45:41 +0100") 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: emacs-orgmode@gnu.org, Rasmus Hello, Bastien writes: >> Though it may be the job of back-ends to provide such a variable >> variable, whenever it makes sense. > > Yes, I think it's the job of backends. For example, in the `e-latex' back-end, there is `org-e-latex-date-format'. Should the value of the variable be used as an argument for `org-export-format-timestamp' if the #+DATE: keyword only contains a timestamp object, and for `format-time-string' otherwise? >> Another option would be to allow to specify an arbitrary timestamp as >> a second, optional, argument to {{{time(...)}}} macro. One could then >> use: >> >> #+DATE: {{{time(%Y-%m-%d,<2013-01-06 Sun>)}}} > > I'm all for allowing macros in "document info" keywords > (i.e. "#+title:" "#+author:" "#+email:" "#+date) though > I'm not sure if it makes sense for other keywords than > for "#+date", and maybe allowing macro here just for > this use-case is to liberal. Note that macros are already supported there (as in anything that will be parsed). Regards, -- Nicolas Goaziou