emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Lixin Chin <lixinchin@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Bug: Unable to nest headings within export blocks [9.0 (9.0-elpa @ c:/Data/Documents/emacs.d/elpa/org-20161102/)]
Date: Thu, 3 Nov 2016 13:20:19 +0800	[thread overview]
Message-ID: <4cc292f0-13c8-3643-793d-6d7f050dedbe@gmail.com> (raw)
In-Reply-To: <338ea338-093e-6323-083e-ac8732c44778@gmail.com>

This seems to be a symptom of the same issue as
http://lists.gnu.org/archive/html/emacs-orgmode/2016-10/msg00175.html

A workaround is to put the contents of the #+BEGIN_EXPORT ... block into
a separate .org file (include.org), and #+INCLUDE it in the main document

#+INCLUDE: "include.org" export <backend>

where "include.org":
* Heading
other text

On 03/11/2016 11:47 AM, Lixin Chin wrote:
> As per the subject, when a heading line is included within a
> `#+BEGIN_EXPORT backend ... #+END_EXPORT' block, it breaks the parsing
> of the block, which is instead split into multiple `paragraph' elements.
>
> See the attached example (test.org), and associate exports (test.tex)
> and (test.html).
>
> Tested with `emacs -Q -l minimal-org.el', with the org package installed
> from http://orgmode.org/elpa/, org-20161102.

  reply	other threads:[~2016-11-03  5:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-03  3:47 Bug: Unable to nest headings within export blocks [9.0 (9.0-elpa @ c:/Data/Documents/emacs.d/elpa/org-20161102/)] Lixin Chin
2016-11-03  5:20 ` Lixin Chin [this message]
2016-11-05  7:41 ` Nicolas Goaziou
2016-11-07  2:47   ` Lixin Chin
2016-11-07 16:44     ` Charles C. Berry
2016-11-09  4:51       ` Lixin Chin

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=4cc292f0-13c8-3643-793d-6d7f050dedbe@gmail.com \
    --to=lixinchin@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).