Hi Nicolas,
Nicolas Goaziou writes:
>> I'd welcome some improvement of the manual wrt macros -- any taker?
>
> Before documenting anything, we should first define them clearly.
FWIW, I don't forget this important thread.
Let's revive it after the release of Org 7.9, when we will think of
movin
Hello,
"Sebastien Vauban"
writes:
> Hi Nicolas,
>
> Nicolas Goaziou wrote:
>> Bastien writes:
>>> François Pinard writes:
If macros are there to stay in Org, it might be worth documenting a more
complete specification about how to define and use them.
>>>
>>> I'd welcome some impro
Hi Nicolas,
Nicolas Goaziou wrote:
> Bastien writes:
>> François Pinard writes:
>>> If macros are there to stay in Org, it might be worth documenting a more
>>> complete specification about how to define and use them.
>>
>> I'd welcome some improvement of the manual wrt macros -- any taker?
>
>
Hello,
Bastien writes:
> François Pinard writes:
>
>> If macros are there to stay in Org, it might be worth documenting a more
>> complete specification about how to define and use them.
>
> I'd welcome some improvement of the manual wrt macros -- any taker?
Before documenting anything, we sho
Hi,
François Pinard writes:
> If macros are there to stay in Org, it might be worth documenting a more
> complete specification about how to define and use them.
I'd welcome some improvement of the manual wrt macros -- any taker?
Thanks,
--
Bastien
Hi François,
François Pinard writes:
> This (partly) replies to the message I sent a few minutes ago. Before
> sending that message, I checked in the Org manual, and the manual is
> silent about the possibility of such escaping.
>
> The manual is also silent about nesting, which has been mentio
Hello,
Yagnesh Raghava Yakkala writes:
> Nicolas Goaziou writes:
>> #+TITLE: Macro test
>> #+MACRO: test2 recursive $1
>> #+MACRO: test A {{{test2(inner)}}} macro, $1.
>> #+MACRO: html-builder (eval (+ $1 $2))
>>
>>
>> {{{test(and an outer one)}}}
>>
>> Some complex macro {{{html-builder(1,2)}}
Hello Nicolas,
Nicolas Goaziou writes:
> #+TITLE: Macro test
> #+MACRO: test2 recursive $1
> #+MACRO: test A {{{test2(inner)}}} macro, $1.
> #+MACRO: html-builder (eval (+ $1 $2))
>
>
> {{{test(and an outer one)}}}
>
> Some complex macro {{{html-builder(1,2)}}}.
out of curiosity I tried to exp
Hello,
François Pinard writes:
> The examples in the manual do not hint either about whether newlines
> are allowed or not in macro arguments.
They are not.
> In fact, the manual section "Macro replacement" says very little, so
> when I initially read it, I guessed that macros are only usable
Christian Moe writes:
> There are other drawbacks [to macros], such as needing to
> backslash-escape any commas (as in the above example).
Oh, thanks!
This (partly) replies to the message I sent a few minutes ago. Before
sending that message, I checked in the Org manual, and the manual is
sile
10 matches
Mail list logo
