[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [O] [New Latex Exporter][BABEL][BUG] lists and inline src

From: Nicolas Goaziou
Subject: Re: [O] [New Latex Exporter][BABEL][BUG] lists and inline src
Date: Thu, 20 Sep 2012 14:13:28 +0200


Eric Schulte <address@hidden> writes:

> Does this problem present itself when you execute the inline code block
> interactively, or only when using the new latex exporter?  If the later
> then it is a latex exporter bug and not a Babel bug.  I've updated the
> subject line so that hopefully the latex export experts will notice this
> message.

Indeed, the parser doesn't understand:

  - src_emacs-lisp{(+ 1 2)}

That's a bug. The problem is related to
`org-babel-inline-src-block-regexp', which is used by the parser. More
accurately, at the beginning of that regexp, there is:


Item contents start at the "s" from "src" but the regexp cannot match
from there. So, is "[^-[:alnum:]]" (and, therefore,
"\\(?:^\\|[^-[:alnum:]]\\)") really necessary? Why couldn't an user be
able to write an inline-src-block in the middle of something (for
example with raw results)?

If checking the character before the inline-src-block object is
mandatory, I'll have to rely on an hack in org-element.el, along the
lines of:

  #+begin_src emacs-lisp
    (unless (bolp) (backward-char))
    (re-search-forward org-babel-inline-src-block-regexp nil limit)

Obviously, I'd rather have the first part of the regexp removed.

What do you think?


Nicolas Goaziou

reply via email to

[Prev in Thread] Current Thread [Next in Thread]