From mboxrd@z Thu Jan 1 00:00:00 1970 From: giles@pexip.com Subject: Re: Possible bug with new exporter and org-babel Date: Mon, 20 May 2013 15:49:22 +0100 Message-ID: References: <87d2slwwik.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:51509) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UeRP8-0007T6-S7 for emacs-orgmode@gnu.org; Mon, 20 May 2013 10:49:40 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UeRP5-0002ur-G3 for emacs-orgmode@gnu.org; Mon, 20 May 2013 10:49:38 -0400 Received: from plane.gmane.org ([80.91.229.3]:51288) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UeRP5-0002uN-A3 for emacs-orgmode@gnu.org; Mon, 20 May 2013 10:49:35 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1UeRP1-0001dq-Vr for emacs-orgmode@gnu.org; Mon, 20 May 2013 16:49:31 +0200 Received: from host81-142-89-185.in-addr.btopenworld.com ([81.142.89.185]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 20 May 2013 16:49:31 +0200 Received: from giles by host81-142-89-185.in-addr.btopenworld.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 20 May 2013 16:49:31 +0200 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org Eric Schulte writes: > Where *is* "req" defined? So far the behavior you describe seems > expected. Sorry for the ambiguity - req isn't defined! Let me explain a little more clearly: I'm trying to generate some release notes using org-mode, pulling data from the github issue tracking system. I'm really just using org as a text markup language. One comment in the issue tracker included a stack trace of the form /foo/bar/call_req() where call_req is a function defined in our (non-org) code. The presence of this plain text string in the body of my org document causes exporting to fail. I'm not familiar with either the new exporter or the details of babel (though a happy user of it), but my expected behaviour would be that any babel cleverness would require more to invoke it than just call_foo() or that there would be some means to say, on a document by document basis "do not invoke babel" In any event: is there a way I can include the phrase "call_req()" in the plain body of my document? Ideally without escaping it, but so so be it. Thanks for your patience. -- Giles Chamberlin