Hello,
Eric Schulte eric.schu...@gmx.com 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
Nicolas Goaziou n.goaz...@gmail.com writes:
Hello,
Eric Schulte eric.schu...@gmx.com 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.
Hello,
Eric Schulte eric.schu...@gmx.com writes:
Thanks for finding the source of this problem. The preceding character
is checked so that inline source blocks can be commented. E.g., a user
may want =src_sh{date}= to appear verbatim.
=src_sh{date}= won't be expanded by
Nicolas Goaziou n.goaz...@gmail.com writes:
Hello,
Eric Schulte eric.schu...@gmx.com writes:
Thanks for finding the source of this problem. The preceding character
is checked so that inline source blocks can be commented. E.g., a user
may want =src_sh{date}= to appear verbatim.
Eric Schulte eric.schu...@gmx.com writes:
Yea, that sounds reasonable, thanks for taking care of this. If I find
time I'll dig through the mailing list and see if I can find the exact
reason why that portion of the regexp was added.
That would be a great starting point to avoid repeating
cbe...@tajo.ucsd.edu writes:
Bastien b...@altern.org writes:
Hi Chuck,
cbe...@tajo.ucsd.edu writes:
My apologies if this is already reported (I recall seeing something like
this, but cannot find it in the archives).
A list element starting with an inline src block is improperly
parsed.
