emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: debugging why a latex preview fails
Date: Wed, 29 Jan 2020 14:11:26 -0500	[thread overview]
Message-ID: <87d0b2yt5t.fsf@alphaville.usersys.redhat.com> (raw)
In-Reply-To: 87eevipiwl.fsf@polytechnique.org

Alan Schmitt <alan.schmitt@polytechnique.org> writes:

> Hello Fabrice and Eric,
>
> Thanks a lot for your suggestions. I ended up edebugging
> 'org-create-formula-image' to have a look at the created tex file (that
> is indeed cleaned up after the generation). The file was fine, but
> dvipng failed on it (with errors like "raw PostScriptdvipng warning:
> PostScript environment contains DVI commands dvipng warning: No image
> output from inclusion of raw PostScript"). I switched to imagemagick to
> do the conversion and everything now works.
>
> The warnings were in the *Org Preview Latex Output* buffer, which
> I realized afterwards. However it's still tricky to debug because
> intermediate files are erased, so I could not initially run the command
> by hand to try to tweak it.
>

I've resorted occasionally to hacking the code and getting rid of the
cleanup just so I would have the intermediate .tex file to look at, but
it's probably not the best way to go :-). It would be nice to have the
ability to inhibit the cleanup more easily: it would make preview almost
as easy to debug as export.

-- 
Nick

"There are only two hard problems in computer science: cache
invalidation, naming things, and off-by-one errors." -Martin Fowler

  reply	other threads:[~2020-01-29 19:11 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
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 [this message]
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=87d0b2yt5t.fsf@alphaville.usersys.redhat.com \
    --to=ndokos@gmail.com \
    --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).