From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nick Dokos Subject: Re: debugging why a latex preview fails Date: Wed, 29 Jan 2020 14:11:26 -0500 Message-ID: <87d0b2yt5t.fsf@alphaville.usersys.redhat.com> References: <87v9oupv75.fsf@polytechnique.org> <87r1zizfte.fsf@ucl.ac.uk> <87eevipiwl.fsf@polytechnique.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:42297) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iwskO-0007Vv-Jd for emacs-orgmode@gnu.org; Wed, 29 Jan 2020 14:11:33 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iwskN-0006KY-LF for emacs-orgmode@gnu.org; Wed, 29 Jan 2020 14:11:32 -0500 Received: from ciao.gmane.io ([159.69.161.202]:33216) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1iwskN-0006JE-Ff for emacs-orgmode@gnu.org; Wed, 29 Jan 2020 14:11:31 -0500 Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1iwskM-000OPH-0n for emacs-orgmode@gnu.org; Wed, 29 Jan 2020 20:11:30 +0100 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-mx.org@gnu.org Sender: "Emacs-orgmode" To: emacs-orgmode@gnu.org Alan Schmitt 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