emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Denis Maier <denismaier@mailbox.org>
To: Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: Include LaTeX source and compiled result
Date: Thu, 9 Jun 2022 09:58:01 +0200	[thread overview]
Message-ID: <a263c025-78a8-480e-4b88-077988603b93@mailbox.org> (raw)
In-Reply-To: <871qvyb7md.fsf@ucl.ac.uk>

Am 09.06.2022 um 09:47 schrieb Fraga, Eric:
> On Wednesday,  8 Jun 2022 at 21:01, Denis Maier wrote:
>> :exports code works. But the problem with the other options is that the
>> compilation fails. But I cannot tell why. It just tells me "Code block
>> produced no output".
> This is not surprising as the LaTeX src blocks are expected to be LaTeX
> body only, not preamble etc.  I.e. in your case, just the line that says
> "This is a test".  You may wish to look at org-format-latex-header,
> org-babel-latex-preamble, org-babel-latex-end-env, ...

Exactly, I've found that out by looking at the file in temp. Testing 
with body only failed as well! I can however manually compile the 
temporary file.

Anyway: This means you cannot switch to using complete files? I was 
hoping for something like
:fragment nil
:complete-doc t

>> How can you diagnose such an issue?
> You can sometimes find the org babel files created in /tmp.

Anything else? I've found those files, but I was wondering whether Emacs 
could give me some more useful debug infos? (Especially since compiling 
the temporary files works...)


  reply	other threads:[~2022-06-09  8:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-08  7:43 Include LaTeX source and compiled result Denis Maier
2022-06-08  7:48 ` Denis Maier
2022-06-08  8:28 ` Fraga, Eric
2022-06-08 19:01   ` Denis Maier
2022-06-09  7:47     ` Fraga, Eric
2022-06-09  7:58       ` Denis Maier [this message]
2022-06-09 11:49         ` Fraga, Eric
2022-06-11  8:38     ` Ihor Radchenko

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=a263c025-78a8-480e-4b88-077988603b93@mailbox.org \
    --to=denismaier@mailbox.org \
    --cc=emacs-orgmode@gnu.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).