emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: Eric Schulte <schulte.eric@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>,
	Nicolas Girard <girard.nicolas@gmail.com>
Subject: Re: [BUG] [Babel] Do not try to process inline source in macro templates
Date: Mon, 2 Sep 2013 18:47:53 +0200	[thread overview]
Message-ID: <F07152AD-8781-4D73-87E3-4A2AF1C4A3E4@gmail.com> (raw)
In-Reply-To: <87fvtntc4f.fsf@gmail.com>

Thank you Eric.

- Carsten

On 2.9.2013, at 18:35, Eric Schulte <schulte.eric@gmail.com> wrote:

> Nicolas Girard <girard.nicolas@gmail.com> 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 code within
>> macro templates.
> 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.
> Cheers,
> -- 
> Eric Schulte
> https://cs.unm.edu/~eschulte
> PGP: 0x614CA05D

  reply	other threads:[~2013-09-02 16:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-23  7:55 [BUG] [Babel] Do not try to process inline source in macro templates Nicolas Girard
2013-09-02 16:35 ` Eric Schulte
2013-09-02 16:47   ` Carsten Dominik [this message]
2013-09-06 21:57     ` Nicolas Girard
2013-09-08 10:55       ` Eric Schulte

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=F07152AD-8781-4D73-87E3-4A2AF1C4A3E4@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=girard.nicolas@gmail.com \
    --cc=schulte.eric@gmail.com \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).