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: Mon, 7 Nov 2016 10:47:08 +0800 [thread overview]
Message-ID: <3cb1d470-fb7b-adde-70ca-d34a3ec9c717@gmail.com> (raw)
In-Reply-To: <878tsybcg7.fsf@nicolasgoaziou.fr>
Hi,
Thanks, yes that almost works. Unfortunately the heading line is just
reproduced verbatim in the output, whereas ideally it should be parsed
as a normal heading.
I.e., currently:
#+BEGIN_EXPORT html
,* HTML only heading
Text which should appear in HTML exports, but not \LaTeX{}.
#+END_EXPORT
Exports as:
<div class="outline-text-2" id="text-1">
* HTML only heading
Text which should appear in HTML exports, but not \LaTeX{}.
</div>
Whereas ideally I'd like to be able to input:
#+BEGIN_EXPORT html
* HTML only heading
Text which should appear in HTML exports, but not \LaTeX{}.
#+END_EXPORT
that would export as:
<div id="outline-container-org2295e90" class="outline-2">
<h2 id="org2295e90"><span class="section-number-2">2</span> HTML only
heading</h2>
<div class="outline-text-2" id="text-2">
<p>
Text which should appear in HTML exports, but not \LaTeX{}.
</p>
</div>
</div>
I'm not sure how difficult this would be to add to org-mode. It seems
that currently everything within a #+BEGIN_EXPORT <backend> ...
#+END_EXPORT block, or included using #+INCLUDE: <filename> export
<backend> is just treated as verbatim text to be include in the output,
and bypasses much of the org-mode parsing.
Regards,
Lixin
On 05/11/2016 03:41 PM, Nicolas Goaziou wrote:
> Hello,
>
> Lixin Chin <lixinchin@gmail.com> writes:
>
>> 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.
>>
>> * Test heading
>>
>> #+BEGIN_EXPORT latex
>> Text which should appear in \LaTeX{} exports, but not HTML.
>> #+END_EXPORT
>>
>> #+BEGIN_EXPORT html
>> * HTML only heading
>> Text which should appear in HTML exports, but not \LaTeX{}.
>> #+END_EXPORT
> You need to escape the pseudo-headline with a comma.
>
> #+BEGIN_EXPORT html
> ,* HTML only heading
> Text which should appear in HTML exports, but not \LaTeX{}.
> #+END_EXPORT
>
>
> Regards,
>
next prev parent reply other threads:[~2016-11-07 2:57 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
2016-11-05 7:41 ` Nicolas Goaziou
2016-11-07 2:47 ` Lixin Chin [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3cb1d470-fb7b-adde-70ca-d34a3ec9c717@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.