From: Carsten Dominik <carsten.dominik@gmail.com>
To: Bernt Hansen <bernt@norang.ca>
Cc: emacs-orgmode@gnu.org, Nicolas Goaziou <n.goaziou@gmail.com>
Subject: Re: New exporter and dates in tables
Date: Mon, 8 Apr 2013 13:33:32 +0200 [thread overview]
Message-ID: <0604BF00-1FE8-4EAA-A346-C125A5127CAD@gmail.com> (raw)
In-Reply-To: <87bo9pntym.fsf@norang.ca>
On 8 apr. 2013, at 13:27, Bernt Hansen <bernt@norang.ca> wrote:
> Nicolas Goaziou <n.goaziou@gmail.com> writes:
>
>> Bernt Hansen <bernt@norang.ca> writes:
>>
>>> I have subtrees with inactive timestamps in the text indicating when
>>> something occurred. I normally don't want to export these. But I think
>>> any table data that includes inactive timestamps should be an exception
>>> to this ... otherwise you get output tables with blank cells where the
>>> meaningful timestamp data would be.
>>
>> I understand.
>>
>> So what exactly should be this exception? Should export ignore <:nil
>> option in a whole table, or only when a table cell contains a single
>> timestamp? IOW, how would it behaves in the following table:
>>
>> | [2013-04-04 Thu] | Lunch at [2013-04-04 Thu] ] |
>>
>> when `org-export-with-timestamps' is either nil or `active'?
>
> I think keeping it simple is best. If there is an inactive timestamp in
> a table then it should be exported (I consider everything in a table as
> data).
I think this is the right way to look at this.
- Carsten
>
>>
>> Also, this must be documented. Exceptions tend to accumulate a lot and
>> make the global behaviour unpredictable. Would you mind providing an
>> explanation to this, which would fit in `org-export-with-timestamps'
>> docstring?
>>
>
> Sure I can do that. I will follow up with a patch in this thread this
> week after the behaviour has been determined.
>
> Regards,
> Bernt
>
next prev parent reply other threads:[~2013-04-08 11:33 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-08 0:05 New exporter and dates in tables Bernt Hansen
2013-04-08 2:18 ` Mike McLean
2013-04-08 6:57 ` Nicolas Goaziou
2013-04-08 11:27 ` Bernt Hansen
2013-04-08 11:33 ` Carsten Dominik [this message]
2013-04-08 19:49 ` Nicolas Goaziou
2013-04-09 13:06 ` Carsten Dominik
2013-04-10 12:43 ` Nicolas Goaziou
2013-04-10 13:12 ` Carsten Dominik
2013-04-10 13:16 ` Bastien
2013-04-11 11:28 ` Nicolas Goaziou
2013-04-11 15:49 ` Bastien
2013-04-13 10:54 ` Nicolas Goaziou
2013-04-13 14:02 ` Bastien
2013-04-13 17:33 ` Nicolas Goaziou
2013-04-13 21:07 ` Sebastien Vauban
2013-04-14 9:10 ` Bastien
2013-04-14 8:58 ` Bastien
2013-04-14 13:37 ` Nicolas Goaziou
2013-04-14 13:45 ` Bastien
2013-04-14 13:47 ` Nicolas Goaziou
2013-04-14 14:01 ` Bastien
2013-04-14 14:06 ` Nicolas Goaziou
2013-04-14 14:24 ` Bastien
2013-04-14 20:36 ` Nicolas Goaziou
2013-04-15 3:58 ` Jambunathan K
2013-04-15 6:44 ` Bastien
2013-04-16 7:48 ` Bastien
2013-08-09 9:35 ` Carsten Dominik
2013-08-09 11:02 ` Bernt Hansen
2013-08-12 5:45 ` Carsten Dominik
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=0604BF00-1FE8-4EAA-A346-C125A5127CAD@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=bernt@norang.ca \
--cc=emacs-orgmode@gnu.org \
--cc=n.goaziou@gmail.com \
/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).