[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [O] New exporter and dates in tables
From: |
Carsten Dominik |
Subject: |
Re: [O] New exporter and dates in tables |
Date: |
Mon, 12 Aug 2013 07:45:22 +0200 |
OK, thank you.
- Carsten
On 9.8.2013, at 13:02, Bernt Hansen <address@hidden> wrote:
> Hi Carsten!
>
> All of my headings are followed by an inactive timestamp. I've started
> leaving a blank line before the content for the heading so the inactive
> timestamp is not exported when timestamps are disabled with the <:nil
> option. This works fine for me.
>
> Regards,
> Bernt
>
> Carsten Dominik <address@hidden> writes:
>
>> 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 <address@hidden> wrote:
>>
>>> Hi Nicolas,
>>>
>>> Nicolas Goaziou <address@hidden> writes:
>>>
>>>> Bastien <address@hidden> writes:
>>>>
>>>>> Nicolas Goaziou <address@hidden> 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