From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: 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 Message-ID: <87obba1jj9.fsf@gmail.com> References: <87d2rq4jfq.fsf@thinkpad.tsdh.de> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:48398) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Un3Ey-0000uW-0W for emacs-orgmode@gnu.org; Thu, 13 Jun 2013 04:50:46 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Un3Ew-0006aV-BY for emacs-orgmode@gnu.org; Thu, 13 Jun 2013 04:50:43 -0400 In-Reply-To: <87d2rq4jfq.fsf@thinkpad.tsdh.de> (Tassilo Horn's message of "Thu, 13 Jun 2013 08:24:25 +0200") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Tassilo Horn Cc: emacs-orgmode@gnu.org Hello, Tassilo Horn 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