From: "Eric Schulte" <schulte.eric@gmail.com>
To: Org Mode <emacs-orgmode@gnu.org>
Subject: [BUG] nested blocks aren't protected on export
Date: Fri, 25 Jun 2010 19:18:35 -0700 [thread overview]
Message-ID: <876316cz9g.fsf@gmail.com> (raw)
Hi,
When exporting nested blocks, the results of the inner blocks are not
fully protected from further exportation. For example, the following
org-mode text
--8<---------------cut here---------------start------------->8---
** protecting block bodies
#+begin_src org
,#+begin_src emacs-lisp
, (message "something")
,#+end_src
#+end_src
--8<---------------cut here---------------end--------------->8---
exports to the following LaTeX
--8<---------------cut here---------------start------------->8---
\section*{protecting block bodies}
\label{sec-1}
\begin{verbatim}
(message "something")
\end{verbatim}
--8<---------------cut here---------------end--------------->8---
in which it looks like the "#+begin_src emacs-lisp" and the "#+end_src"
lines are completely removed, and exports to the following html
(newlines added for readability)
--8<---------------cut here---------------start------------->8---
<pre class="src src-org">
<span class="org-org-meta-line">#+begin_src emacs-lisp</span>
<span class="org-org-block"> (message "something")</span>
<span class="org-org-meta-line">
</pre>
--8<---------------cut here---------------end--------------->8---
in which the #+begin_src line is in tact, but it appears everything
following the end_src line (including the </span>) is removed.
I've played around with adding 'org-protected properties during export
but to no avail.
Any suggestions are much appreciated.
Thanks -- Eric
next reply other threads:[~2010-06-26 2:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-26 2:18 Eric Schulte [this message]
2010-06-28 2:42 ` [BUG] nested blocks aren't protected on export Eric Schulte
2010-06-28 6:37 ` Carsten Dominik
2010-06-28 15:04 ` Eric Schulte
2010-06-28 16:21 ` Carsten Dominik
2010-06-28 18:40 ` Eric Schulte
2010-06-28 19:59 ` Eric Schulte
2010-06-29 4:32 ` Carsten Dominik
2010-06-29 5:09 ` Eric Schulte
2010-06-28 15:07 ` Nicolas Goaziou
2010-06-28 15:30 ` Eric Schulte
2010-06-28 17:04 ` Nicolas Goaziou
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=876316cz9g.fsf@gmail.com \
--to=schulte.eric@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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).