Hello,
Sebastien Vauban writes:
> Though, I don't understand either why your example did not work, as --
> during the export process -- macros are supposed to be expanded before
> Babel code be evaluated.
>
> There must be some restriction, then, on which part of a document
> a macro can resid
"Charles C. Berry" writes:
> On Tue, 11 Aug 2015, Gary Oberbrunner wrote:
>
>> I'd like to have either a macro or a property that controls some behavior
>> of an org-mode babel file:
>>
>> #+PROPERTY: report_type All
>>
>> and use that property inline: {{{property(report_type)}}} and in a source
>
On Tue, 11 Aug 2015, Gary Oberbrunner wrote:
I'd like to have either a macro or a property that controls some behavior
of an org-mode babel file:
#+PROPERTY: report_type All
and use that property inline: {{{property(report_type)}}} and in a source
block:
#+NAME: rtype
#+BEGIN_SRC emacs-lisp :
I'd like to have either a macro or a property that controls some behavior
of an org-mode babel file:
#+PROPERTY: report_type All
and use that property inline: {{{property(report_type)}}} and in a source
block:
#+NAME: rtype
#+BEGIN_SRC emacs-lisp :results value
{{{property(report_type)}}}
#+END_
