From: Eric Schulte <eric.schulte@gmx.com>
To: Truong Nghiem <truong.nghiem@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: URGENT Bug with exporting org source block
Date: Sat, 31 Mar 2012 10:23:51 -0400 [thread overview]
Message-ID: <87k420u9qo.fsf@gmx.com> (raw)
In-Reply-To: CADNXMz9asuFUZaeXAciHUvt0RoqS2Y2pVbrZaALxaS7PHArORQ@mail.gmail.com
Truong Nghiem <truong.nghiem@gmail.com> 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: <name>
> ,#+begin_src <language> <switches> <header arguments>
> , <body>
> ,#+end_src
> #+END_SRC
>
> the last source line is not exported. The output, in both PDF and
> HTML, becomes:
>
> #+srcname: <name>
> #+begin_src <language> <switches> <header arguments>
> <body>
>
> 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/
next prev parent reply other threads:[~2012-03-31 16:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-28 19:41 Bug with exporting org source block Truong Nghiem
2012-03-31 14:23 ` Eric Schulte [this message]
2012-03-31 16:58 ` URGENT " Eric Schulte
2012-04-01 7:18 ` Achim Gratz
2012-04-01 12:43 ` Eric Schulte
2012-04-01 15:27 ` Achim Gratz
2012-04-01 16:28 ` Eric Schulte
2012-04-01 18:35 ` Achim Gratz
2012-04-01 18:08 ` Achim Gratz
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=87k420u9qo.fsf@gmx.com \
--to=eric.schulte@gmx.com \
--cc=emacs-orgmode@gnu.org \
--cc=truong.nghiem@gmail.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).