Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:

> Hello,
>
> Rainer M Krug <r.m.krug@gmail.com> writes:
>
>> Do macros work for properties ? If yes, you could degine two macro,
>> one for each set of properties.
>
> No, they don't.

That's a pity.

It would be really great if one could define different sets of
hearer-args and then, at thr beginning of a code block, simply use:

#+MACRO: forTangle  :tangle ./test.R :export none
#+MACRO: forExecution  :tangle no :export both :session Test14
#+MACRO: forNoSession  :tangle no :export both

#+:header-args {{{forTangle}}}
#+begin_src R :tangle no
  cat(13)
#+end_src

#+:header-args {{{forExecution}}}
#+begin_src R :tangle no
  cat(14)
#+end_src

#+:header-args {{{forNoSession}}}
#+begin_src R :tangle no
  cat(14)
#+end_src


This would make it much easier to work with header-args and solve many
problems which were discussed in earlier threads.

The example might not be the best as it could be implemented by
header-args+ but if the code blocks using the different sets of
header-args are at different locations in the org document, changing
them would be much easier with macro expansion (or similar).

Would it be difficult to include this feature?

Thanks,

Rainer

>
> Regards,

-- 
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, UCT), Dipl. Phys. (Germany)

Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa

Tel :       +33 - (0)9 53 10 27 44
Cell:       +33 - (0)6 85 62 59 98
Fax :       +33 - (0)9 58 10 27 44

Fax (D):    +49 - (0)3 21 21 25 22 44

email:      Rainer@krugs.de

Skype:      RMkrug

PGP: 0x0F52F982