emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Bastien <bzg@altern.org>
Cc: emacs-orgmode@gnu.org, Rasmus <rasmus@gmx.us>
Subject: Re: [new exporter] adhere org-export-date-timestamp-format?
Date: Sun, 06 Jan 2013 11:00:21 +0100	[thread overview]
Message-ID: <87bod2637u.fsf@gmail.com> (raw)
In-Reply-To: <87623stdza.fsf@bzg.ath.cx> (Bastien's message of "Mon, 24 Dec 2012 02:50:49 +0100")

Hello,

Bastien <bzg@altern.org> writes:

> Rasmus <rasmus@gmx.us> writes:
>
>> Would it be desirable if the new exporter took the variable
>> org-export-date-timestamp-format into consideration when formatting
>> dates?  
>
> I think so.  What do you think, Nicolas?

I'm not convinced by this variable. Back-ends are usually so much
different that a global variable aiming at formatting a date timestamp
in any of them doesn't sound very useful.

Though it may be the job of back-ends to provide such a variable
variable, whenever it makes sense.

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>)}}}


Regards,

-- 
Nicolas Goaziou

  reply	other threads:[~2013-01-06 10:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-18 14:43 [new exporter] adhere org-export-date-timestamp-format? Rasmus
2012-12-24  1:50 ` Bastien
2013-01-06 10:00   ` Nicolas Goaziou [this message]
2013-01-06 11:45     ` Bastien
2013-01-09 15:29       ` Nicolas Goaziou
2013-01-09 17:15         ` Bastien
2013-01-09 18:03           ` Nicolas Goaziou
2013-01-09 18:30             ` Bastien
2013-01-12 11:30               ` Nicolas Goaziou
2013-01-12 14:45                 ` Bastien
2013-01-30 21:53                   ` Nicolas Goaziou
2013-01-30 23:54                     ` Rasmus

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87bod2637u.fsf@gmail.com \
    --to=n.goaziou@gmail.com \
    --cc=bzg@altern.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=rasmus@gmx.us \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).