[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [O] Bug: Exporter omits inline code blocks [8.0.3 (release_8.0.3-238
From: |
Nicolas Goaziou |
Subject: |
Re: [O] Bug: Exporter omits inline code blocks [8.0.3 (release_8.0.3-238-g172061 @ /home/horn/Repos/el/org-mode/lisp/)] |
Date: |
Thu, 13 Jun 2013 10:50:34 +0200 |
Hello,
Tassilo Horn <address@hidden> writes:
> lately, I've used ox-reveal.el to create a presentation. Thereby, I
> found out that inline source code blocks are ignored, i.e., the text is
> simply not there in the HTML5 output.
>
> Here's a test heading:
>
> * Test Heading
>
> - Here's some inline code: src_clojure{(+ 1 2 3)}
> - Here's some more inline code: src_clojure{(- 1 2 3)}
>
>
> ox-reveal.el derives the export from ox-html. That defines
>
> (inline-src-block . org-html-inline-src-block)
>
> with
>
> (defun org-html-inline-src-block (inline-src-block contents info)
> "Transcode an INLINE-SRC-BLOCK element from Org to HTML.
> CONTENTS holds the contents of the item. INFO is a plist holding
> contextual information."
> (let* ((org-lang (org-element-property :language inline-src-block))
> (code (org-element-property :value inline-src-block)))
> (error "Cannot export inline src block")))
>
> and ox-reveal doesn't (yet) override that. So in theory, exporting the
> entry above should signal an error, but it doesn't
>
> I also tried the plain html export. Still, there's no error. The
> function is simply not called at all.
>
> So there seems to be a bug in the exporter which doesn't seem to
> recognize inline source code.
There's no bug. Babel simply removes all inline source blocks when
executing source blocks. Hence, they cannot be parsed (and therefore
exported).
This function is just a placeholder for now.
Regards,
--
Nicolas Goaziou