From: Nicolas Goaziou <firstname.lastname@example.org>
To: Bastien <email@example.com>
Cc: Orgmode <firstname.lastname@example.org>, Jambunathan K <email@example.com>
Subject: Re: New exporter: no custom timestamps
Date: Wed, 19 Sep 2012 22:28:27 +0200 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
In-Reply-To: <email@example.com> (Bastien's message of "Tue, 18 Sep 2012 13:15:32 +0200")
Bastien <firstname.lastname@example.org> writes:
> I suggest to fix this in org-e-html.el with the attached patch.
> There is another option: to set :raw-value for time-stamps, but
> this feels a bit clumsy, especially when there is a :range-end.
> (org-element-property :raw-value TIMESTAMP)
I tend to think that :raw-value would be a good option. Timestamps
properties could be enriched. Besides common properties
(:begin, :end, :post-blank) timestamps objects may accept :
- :repeater-type (a symbol among: `cumulative', 'catch-up', 'restart'
corresponding to, respectively "+", "++" ".+" repeater marks)
:*-end properties would be the same as :*-start properties when
timestamp isn't a range. Both would be nil (along with :repeater-*) when
type is `diary'.
By default back-ends would use :raw-value and `org-translate-time'.
:range-end property would be removed.
What do you think?
next prev parent reply other threads:[~2012-09-19 20:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-17 13:49 New exporter: no custom timestamps Giovanni Ridolfi
2012-09-17 18:49 ` Jambunathan K
2012-09-18 11:15 ` Bastien
2012-09-19 20:28 ` Nicolas Goaziou [this message]
2012-09-22 16:40 ` Bastien
2012-10-28 15:44 ` Nicolas Goaziou
2012-10-29 5:39 ` Bastien
2012-09-22 16:44 ` Bastien
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).