From: Carsten Dominik <carsten.dominik@gmail.com>
To: Bastien <bzg@gnu.org>
Cc: Bernt Hansen <bernt@norang.ca>,
emacs-orgmode@gnu.org, Nicolas Goaziou <n.goaziou@gmail.com>
Subject: Re: New exporter and dates in tables
Date: Fri, 9 Aug 2013 11:35:18 +0200 [thread overview]
Message-ID: <E4521392-71E3-4D4C-90CE-E24993A85F23@gmail.com> (raw)
In-Reply-To: <874nf6q5k6.fsf@bzg.ath.cx>
Hi guys,
did you arrive at a conclusion of this thread, or is this still open?
Thanks
- Carsten
On 16.4.2013, at 09:48, Bastien <bzg@gnu.org> wrote:
> Hi Nicolas,
>
> Nicolas Goaziou <n.goaziou@gmail.com> writes:
>
>> Bastien <bzg@gnu.org> writes:
>>
>>> Nicolas Goaziou <n.goaziou@gmail.com> writes:
>>>
>>>> We can widen the definition of `standalone': a standalone timestamp is
>>>> a timestamp belonging to a paragraph that contains only timestamps
>>>> objects.
>>>
>>> Great. If that's possible, then I think that's the best solution.
>>
>> The following patch should do that. It comes with tests, but it should
>> be tested extensively, if only to know if this feature is as useful as
>> it seems.
>
> I think I nailed down the root of the confusion.
>
> org-export-with-planning does the job that org-export-with-timestamps
> used to do. So first of all, org-export-with-timestamps should be an
> alias to org-export-with-planning so that users who customized
> org-export-with-timestamps don't have to change their customization:
>
> (define-obsolete-variable-alias 'org-export-with-timestamps
> 'org-export-with-planning "24.4")
>
> Today, org-export-with-timestamps does a completely different job,
> more fine-grained than the old org-export-with-timestamps. I suggest
> to rename it to org-export-with-individual-timestamps and to use the
> latest patch you sent, with a default value of t. I expect the next
> useful value is 'not-standalone. But if someone wants to get rid of
> time-stamps in tables or in lists, he now can.
>
>> Note that another option is to allow all timestamps, put timestamps you
>> don't want to export in a specific drawer (e.g. "TIME"), and ignore this
>> drawer during export.
>
> Yes, but that requires educating users, which I don't really like.
>
> Thanks,
>
> --
> Bastien
next prev parent reply other threads:[~2013-08-09 9:35 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
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 [this message]
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=E4521392-71E3-4D4C-90CE-E24993A85F23@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=bernt@norang.ca \
--cc=bzg@gnu.org \
--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).