From: Eric Schulte <schulte.eric@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [bug] cannot export with babel function calls
Date: Mon, 14 Oct 2013 14:47:54 -0600 [thread overview]
Message-ID: <87vc0z37gl.fsf@gmail.com> (raw)
In-Reply-To: <87a9iih7x0.fsf@ucl.ac.uk> (Eric S. Fraga's message of "Wed, 9 Oct 2013 14:48:27 +0100")
[-- Attachment #1: Type: text/plain, Size: 1622 bytes --]
Eric S Fraga <e.fraga@ucl.ac.uk> writes:
> Hello,
>
> a few weeks ago, I noted a problem that arose with the more recent
> versions of emacs (I track emacs-snapshot for ubuntu):
>
> http://article.gmane.org/gmane.emacs.orgmode/76519/
>
> The problem does not arise with the emacs 24 version distributed with
> ubuntu 13.04. I had hoped that this problem would disappear but I have
> upgraded emacs-snapshot two or three times since and the problem
> continues.
>
> To summarise, exporting an org file fails if there are any babel calls
> (i.e. #+call: or inline call_). The error is "Marker points into wrong
> buffer". I have verified this with =emacs -Q=. I'm attaching a test
> file along with the resulting backtrace from =org-export-dispatch=,
> choosing export to LaTeX.
>
> Yes, I can go back to an older version of emacs but that avoids getting
> the problem fixed. I have not filed an emacs bug report as I have only
> run into this problem with org. I was hoping that somebody here could
> have a look. I am happy to help in any way I can. Too many (most!) of
> my org files make use of babel now...
>
> Thanks,
> eric
I actually get a different error [1], namely that the call line can't be
parsed because we're using a regex to grab call lines and regular
expressions can't count parens.
Exporting a slightly changed file (attached [2]) works for me w/o error.
I'm using the following Emacs version [3]. I may have to wait until the
cause of this error hits the Emacs in the Arch Linux package system to
debug further.
Cheers,
Footnotes:
[1] org-babel-read: End of file during parsing
[2]
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: examplebug.org --]
[-- Type: text/x-org, Size: 240 bytes --]
#+TITLE: examplebug.org
#+AUTHOR: Eric S Fraga
#+Options: ^:{}
* babel test
#+name: test
#+begin_src emacs-lisp :var x=5
(list x)
#+end_src
#+call: test('(a b c))
I should be able to put the output inline using call_test('foo).
[-- Attachment #3: Type: text/plain, Size: 387 bytes --]
[3] $ emacs --version
GNU Emacs 24.3.1
Copyright (C) 2013 Free Software Foundation, Inc.
GNU Emacs comes with ABSOLUTELY NO WARRANTY.
You may redistribute copies of Emacs
under the terms of the GNU General Public License.
For more information about these matters, see the file named COPYING.
--
Eric Schulte
https://cs.unm.edu/~eschulte
PGP: 0x614CA05D
next prev parent reply other threads:[~2013-10-14 20:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-09 13:48 [bug] cannot export with babel function calls Eric S Fraga
2013-10-14 20:47 ` Eric Schulte [this message]
2013-10-15 7:53 ` Eric S Fraga
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87vc0z37gl.fsf@gmail.com \
--to=schulte.eric@gmail.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.