emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Sebastien Vauban" <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: Can't export LaTeX source code blocks
Date: Sat, 27 Apr 2013 11:16:20 +0200	[thread overview]
Message-ID: <86ip38xriz.fsf@somewhere.org> (raw)
In-Reply-To: m17gjumcdz.fsf@poto.westell.com

Hello Thomas,

Thomas S. Dye wrote:
> "Sebastien Vauban" writes:
>>>> The code block is NEVER exported. I don't understand why?
>>> I'm not sure either.
>>> This is not a problem from the exporter as `org-export-execute-babel-code'
>>> on your ECM makes the src block disappear.
>> The only buggy behavior is the first one: the fact that the "code" block
>> disappears, as you say.
> I took a quick look at ob-latex.el. The code there sets `:exports
> results' and then, IIUC, goes on its way without checking if :exports
> has been set in the buffer.
> It looks to me like ob-latex.el would need to be revised.

I don't have the impression that the error lies in `ob-latex' as the other
`ob-LANG' files don't either make any special check -- while all graphics-only
languages do, as well, have the default of "results" for ":exports".

I have the impression the problem is to search in `ob-core'
(`org-babel-execute-src-block') or `ob-exp'... But that's not yet clear to me
where that could be.

FYI, I have collected extra information about the problem: it is the file-wide
property which is not taken into account (only in the case of the LaTeX code
blocks, though).

If we put the header argument ":exports both" on the code block itself, I get
the expected result...

--8<---------------cut here---------------start------------->8---
#+TITLE:     ECM skeleton.org
#+PROPERTY: tangle skeleton.cls
#+PROPERTY: exports both


Code block:

#+name: ecm-code-block-1
#+begin_src latex
This macro does nothing.\index{doing nothing|usage}

Results block:

#+results: ecm-code-block-1
This macro does nothing.\index{doing nothing|usage}

* ECM LaTeX okay

#+name: ecm-code-block-2
#+begin_src latex :exports both
This macro does nothing.\index{doing nothing|usage}

Results block:

#+results: ecm-code-block-2
This macro does nothing.\index{doing nothing|usage}
--8<---------------cut here---------------end--------------->8---

Best regards,

Sebastien Vauban

  parent reply	other threads:[~2013-04-27  9:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-22 19:34 Can't export LaTeX source code blocks Sebastien Vauban
2013-04-22 20:14 ` Nicolas Goaziou
2013-04-22 21:46   ` Sebastien Vauban
2013-04-22 22:25     ` Thomas S. Dye
2013-04-24 21:32       ` Sebastien Vauban
2013-04-27  9:16       ` Sebastien Vauban [this message]
2013-04-27  9:45         ` [PATCH] " Sebastien Vauban
2013-05-03 20:40           ` Sebastien Vauban
2013-05-06 20:32           ` Eric Schulte

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:

  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=86ip38xriz.fsf@somewhere.org \
    --to=sva-news-d0wtavr13harg/idocfnwg@public.gmane.org \
    --cc=emacs-orgmode-mXXj517/zsQ@public.gmane.org \


* 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


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).