From: Fabrice Popineau <fabrice.popineau@centralesupelec.fr>
To: "Fraga, Eric" <e.fraga@ucl.ac.uk>
Cc: Alan Schmitt <alan.schmitt@polytechnique.org>,
emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: debugging why a latex preview fails
Date: Wed, 29 Jan 2020 11:20:38 +0100 [thread overview]
Message-ID: <CAFgFV9Od4KRjTVRAk0aRhB_7NhWBYMVoNym6d2vPPpyEGXkKog@mail.gmail.com> (raw)
In-Reply-To: <xuu6d0b2lhfy.fsf@ucl.ac.uk>
[-- Attachment #1: Type: text/plain, Size: 750 bytes --]
Le mer. 29 janv. 2020 à 10:51, Fraga, Eric <e.fraga@ucl.ac.uk> a écrit :
> On Wednesday, 29 Jan 2020 at 08:39, Alan Schmitt wrote:
> > I'm trying to add some diagrams in a note, and I want to use latex
> > preview for that. Unfortunately the result is not what I expect: I do
> > see an image, but there seem to be errors in the latex processing. How
> > can I see what latex is produced to find where the issue is?
>
> Your example works for me. Maybe you need other packages as well
> (e.g. tikz itself)?
>
> I don't know the best way to debug, however
First of all: look into the *Org PDF LaTeX Output* buffer to see why the
compilation failed?
Then look into the .tex file header to see if something is missing.
Fabrice
[-- Attachment #2: Type: text/html, Size: 1158 bytes --]
next prev parent reply other threads:[~2020-01-29 10:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-29 7:39 debugging why a latex preview fails Alan Schmitt
2020-01-29 9:50 ` Fraga, Eric
2020-01-29 10:20 ` Fabrice Popineau [this message]
2020-01-29 11:02 ` Fraga, Eric
2020-01-29 11:23 ` Fabrice Popineau
2020-01-29 12:05 ` Alan Schmitt
2020-01-29 19:11 ` Nick Dokos
2020-01-30 6:55 ` Fraga, Eric
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
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=CAFgFV9Od4KRjTVRAk0aRhB_7NhWBYMVoNym6d2vPPpyEGXkKog@mail.gmail.com \
--to=fabrice.popineau@centralesupelec.fr \
--cc=alan.schmitt@polytechnique.org \
--cc=e.fraga@ucl.ac.uk \
--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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).