On 26.9.2013, at 16:33, Nicolas Goaziou wrote:
> Carsten Dominik writes:
>
>> Will you also work on exporters in contrib, or should I ping the
>> respective authors to do this?
>
> This is a grunt job. Also, only ox-confluence and ox-groff have to be
> updated.
>
> I will commit the changes
Carsten Dominik writes:
> Will you also work on exporters in contrib, or should I ping the
> respective authors to do this?
This is a grunt job. Also, only ox-confluence and ox-groff have to be
updated.
I will commit the changes in a little while.
Regards,
--
Nicolas Goaziou
Excellent, thank you for the fast solution to this issue.
Will you also work on exporters in contrib, or should I ping the respective
authors to do this?
- Carsten
On 26.9.2013, at 13:48, Nicolas Goaziou wrote:
> Hello,
>
> Carsten Dominik writes:
>
>> this does look good to me, except tha
Hello,
Carsten Dominik writes:
> this does look good to me, except that the customize type of
> org-export-with-properties needs to be extended to allow for the
> list of strings.
>
> Please just go ahead and apply it to master, then I and hopefully
> others will test it further.
Fixed and done
Hi,
this does look good to me, except that the customize type of
org-export-with-properties needs to be extended to allow for the
list of strings.
Please just go ahead and apply it to master, then I and hopefully others will
test it further.
- Carsten
On 25.9.2013, at 22:57, Nicolas Goaziou w
Dnia 2013-09-25, o godz. 12:53:18
Thorsten Jolitz napisał(a):
> > One possible remaining option would be to introduce user variables
> > org-BACKEND-format-property-drawer-function in analogy
> > org-BACKEND-format-drawer-function. This would provide an easy way
> > to configure export of the pr
Carsten Dominik writes:
> Not really. It would simplify processing to have the list instead
> of a string, but indeed, a filter can accomplish all of it.
Here is a first patch. It doesn't handle export back-ends in contrib.
Regards,
--
Nicolas Goaziou
>From c48974d10e0d57b6332fcfed384a49ee5
>> - when t, export completely all property drawers as examples;
>>
>> - when nil, do not export property drawers (default value);
>>
>> - when set to a list of strings, export property drawers as examples
>>but only include properties matching these strings;
+1
Christian
On 25.9.2013, at 14:13, Nicolas Goaziou wrote:
> Carsten Dominik writes:
>
>> This sounds good to me. How about allowing also a function
>> as a value and that function will receive the list of properties
>> and do with it as it pleases.
>
> At first I thought about it but I realized that wa
Nicolas Goaziou writes:
Hello,
> There may be a slightly different option available: we can introduce
> a new defcustom, e.g., `org-export-with-node-properties' (what symbol to
> use for short item in OPTIONS?), which will trigger the following
> behaviour:
>
> - when t, export completely all
Carsten Dominik writes:
> This sounds good to me. How about allowing also a function
> as a value and that function will receive the list of properties
> and do with it as it pleases.
At first I thought about it but I realized that was exactly what
a filter could do. Do we need to introduce red
On 25.9.2013, at 13:51, Nicolas Goaziou wrote:
> Hello,
>
> Carsten Dominik writes:
>
>> One possible remaining option would be to introduce user variables
>> org-BACKEND-format-property-drawer-function in analogy
>> org-BACKEND-format-drawer-function. This would provide an easy way
>> to co
Hello,
Carsten Dominik writes:
> One possible remaining option would be to introduce user variables
> org-BACKEND-format-property-drawer-function in analogy
> org-BACKEND-format-drawer-function. This would provide an easy way
> to configure export of the property drawer as a whole, in a way
> t
On 25.9.2013, at 12:53, Thorsten Jolitz wrote:
> Carsten Dominik writes:
>
>> 3. The only exception to this rule are property drawers, which will
>> currently not be exported by any of the backends. Nicolas
>> proposed to define a derived backend that does export the property
>> drawer,
Carsten Dominik writes:
> 3. The only exception to this rule are property drawers, which will
>currently not be exported by any of the backends. Nicolas
>proposed to define a derived backend that does export the property
>drawer, or he proposed to use macros to extract specific prope
OK,
now that I have made a fool out of myself, I think I understand now how
things work, and what I did not understand correctly in the
discussion so far.
1. I misunderstood that drawers could not be exported in
general with the new exporter. This is wrong, drawers are
exported just fine
16 matches
Mail list logo
