From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Schulte Subject: Re: URGENT Bug with exporting org source block Date: Sat, 31 Mar 2012 10:23:51 -0400 Message-ID: <87k420u9qo.fsf@gmx.com> References: Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:59882) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SE18s-0002Hy-Og for emacs-orgmode@gnu.org; Sat, 31 Mar 2012 12:27:08 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SE18q-00025j-SG for emacs-orgmode@gnu.org; Sat, 31 Mar 2012 12:27:06 -0400 Received: from mailout-us.gmx.com ([74.208.5.67]:46269 helo=mailout-us.mail.com) by eggs.gnu.org with smtp (Exim 4.71) (envelope-from ) id 1SE18q-00024D-LH for emacs-orgmode@gnu.org; Sat, 31 Mar 2012 12:27:04 -0400 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Truong Nghiem Cc: emacs-orgmode@gnu.org Truong Nghiem writes: > I'm using orgmode release Org 7.8.06. When I export an org source > block (i.e. a source code block in the org language): > > #+BEGIN_SRC org :exports code > ,#+srcname: > ,#+begin_src

> , > ,#+end_src > #+END_SRC > > the last source line is not exported. The output, in both PDF and > HTML, becomes: > > #+srcname: > #+begin_src

> > > Notice that the line "#+end_src" is not present. > -- > Truong Nghiem > Hi Truong, Thanks for reporting this problem. The issue lies somewhere later in the export process and is not related to the Babel expansion of the code block. To see this your example code may be placed in an org-mode file, and the code block export expansion may be run by evaluating the following elisp snippet. (let ((org-current-export-file "/path/to/file.org")) (org-export-blocks-preprocess)) Hopefully someone more familiar with the export process can try to pin down this behavior. This would be a good fix to put in before the upcoming Emacs merge. Best, -- Eric Schulte http://cs.unm.edu/~eschulte/