From: Eric Schulte <schulte.eric@gmail.com>
To: Sebastien Vauban <wxhgmqzgwmuf@spammotel.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: Cannot include orgmode source code block [7.7]
Date: Fri, 11 Nov 2011 14:25:11 -0700 [thread overview]
Message-ID: <87k476l5c8.fsf@gmail.com> (raw)
In-Reply-To: <80sjluz8wi.fsf@somewhere.org> (Sebastien Vauban's message of "Fri, 11 Nov 2011 21:44:29 +0100")
"Sebastien Vauban" <wxhgmqzgwmuf@spammotel.com> writes:
> Hi Truong,
>
> Truong Nghiem wrote:
>> I created a following simple org file, in which a source code block of
>> language "org" contains orgmode code:
>> ======= BEGIN CODE ========
>> #+TITLE: A Test
>>
>> #+BEGIN_SRC org
>> ,#+begin_src python
>> #+END_SRC
>>
>> End of test.
>> ======= END CODE ==========
>>
>> However, when I exported this file, either to HTML or LaTeX/PDF, it
>> caused an error:
>>
>> ad-Orig-error: unbalanced begin/end_src blocks with #("#+BEGIN_SRC org
>> ,#+begin_src python
>> #+END_SRC" 0 15 (fontified nil font-lock-fontified t) 15 16 (fontified
>> nil font-lock-fontified t) 16 37 (fontified nil font-lock-fontified t)
>> 37 38 (fontified nil font-lock-fontified t) 38 47 (fontified nil
>> font-lock-fontified t))
>>
>> I'm using the latest development version of orgmode. Also, if I
>> recall correctly, I did succeed to export this kind of code in the
>> past (don't remember which version of orgmode though).
>>
>> If I included #+end_src in the body of the org code block, it would export
>> the file, but the result was not what I expected: it was blank.
>
> I do confirm this, in a very recent Org version, and consider it as a bug too.
>
I've just pushed up a fix, thanks for the catch. -- Eric
--
Eric Schulte
http://cs.unm.edu/~eschulte/
prev parent reply other threads:[~2011-11-11 21:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-11 19:52 Bug: Cannot include orgmode source code block [7.7] Truong Nghiem
2011-11-11 20:44 ` Sebastien Vauban
2011-11-11 21:25 ` Eric Schulte [this message]
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=87k476l5c8.fsf@gmail.com \
--to=schulte.eric@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=wxhgmqzgwmuf@spammotel.com \
/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).