emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: giles@pexip.com
To: emacs-orgmode@gnu.org
Subject: Re: Possible bug with new exporter and org-babel
Date: Mon, 20 May 2013 15:49:22 +0100	[thread overview]
Message-ID: <m2k3mtzoy5.fsf@jujutsu.org.uk> (raw)
In-Reply-To: 87d2slwwik.fsf@gmail.com

Eric Schulte <schulte.eric@gmail.com> 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

  reply	other threads:[~2013-05-20 14:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-20 11:47 Possible bug with new exporter and org-babel giles
2013-05-20 14:34 ` Eric Schulte
2013-05-20 14:49   ` giles [this message]
2013-05-20 16:48     ` Eric Schulte
2013-05-20 18:02       ` giles

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  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=m2k3mtzoy5.fsf@jujutsu.org.uk \
    --to=giles@pexip.com \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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).