Sebastien Vauban writes:
> Hello Nicolas,
>
> Nicolas Goaziou wrote:
[...]
>> Note that even if it had one, it wouldn't work as expected since Beamer
>> is not supported yet (but I'll probably implement a first draft for this
>> back-end soon).
>
> I'll be glad to be your first Beamer tester --
Hello Nicolas,
Nicolas Goaziou wrote:
> "Sebastien Vauban"
> writes:
>
With the new exporter, most things work. What does not work:
- macro does not get executed (no string in orange color),
>>>
>>> Macro are meant to produce contents, not to talk to back-ends. Every text
>>> they produ
Hello,
"Sebastien Vauban"
writes:
>>> With the new exporter, most things work. What does not work:
>>> - macro does not get executed (no string in orange color),
>>
>> Macro are meant to produce contents, not to talk to back-ends. Every text
>> they produce will be protected.
>
> Do you mean t
Hello Nicolas,
Nicolas Goaziou wrote:
> "Sebastien Vauban" writes:
>
>> With the new exporter, most things work. What does not work:
>> - macro does not get executed (no string in orange color),
>
> Macro are meant to produce contents, not to talk to back-ends. Every text
> they produce will be pr
Hello,
"Sebastien Vauban"
writes:
> With the new exporter, most things work. What does not work:
> - macro does not get executed (no string in orange color),
Macro are meant to produce contents, not to talk to back-ends. Every
text they produce will be protected.
> - the =\end{verbatim}= dis
Hello,
I want to write a document where I show:
- Org code to type in a buffer
- (sometimes) its LaTeX translation
- its effect in the output PDF
Though, I have big troubles outputting the Org code one is suppose to write in
the Org buffers. It often gets replaced or modified... See examples in
