Nicolas Girard writes:
> 2013/9/2 Eric Schulte :
>>>
>>> I've just pushed up a fix for this issue which should now ignore inline
>>> source blocks on lines starting with "#+" during export. I don't know
>>> if there is a better way than using a regex to detect such non-exporting
>>> lines but t
2013/9/2 Eric Schulte :
>>
>> I've just pushed up a fix for this issue which should now ignore inline
>> source blocks on lines starting with "#+" during export. I don't know
>> if there is a better way than using a regex to detect such non-exporting
>> lines but this appears to work.
>>
Thanks
Thank you Eric.
- Carsten
On 2.9.2013, at 18:35, Eric Schulte wrote:
> Nicolas Girard writes:
>
>> When a buffer contains such
>>
>>#+MACRO: m src_emacs-lisp[:results raw]{(do-something "$1")}
>>
>> macro template, calling =org-babel-execute-buffer= using =C-c C-v C-b= yields
>>
>>
Nicolas Girard writes:
> When a buffer contains such
>
> #+MACRO: m src_emacs-lisp[:results raw]{(do-something "$1")}
>
> macro template, calling =org-babel-execute-buffer= using =C-c C-v C-b= yields
>
> if: No id found: $1
>
> It seems to me that Babel shouldn't be looking for inline cod
When a buffer contains such
#+MACRO: m src_emacs-lisp[:results raw]{(do-something "$1")}
macro template, calling =org-babel-execute-buffer= using =C-c C-v C-b= yields
if: No id found: $1
It seems to me that Babel shouldn't be looking for inline code within
macro templates.
Cheers,
--
