From: David Kastrup <dak@gnu.org>
Subject: Re: Problem with preview-latex
Date: Thu, 21 Dec 2006 23:16:49 +0100 [thread overview]
Message-ID: <85r6uszyge.fsf@lola.goethe.zz> (raw)
In-Reply-To: em9av5$mva$1@news.in.tum.de
Florian Lindner <Florian.Lindner@xgm.de> writes:
> I've tried to use preview latex to use on a newly started document. It works
> on other documents but somehow does not like this one:
>
> I used C-c C-p C-d to preview the entire document but preview-latex only
> displays error symbols next to the formulas.
Please use
M-x preview-report-bug RET
for reporting problems.
Here is the rub:
> Running `Preview-LaTeX' on `Nachrechnung' with ``latex "&prv_Nachrechnung"
> Nachrechnung.tex''
prv_Nachrechnung is a predumped format containing the preamble, dumped
by using mylatex.ltx.
> CUSTOMISED FORMAT. Preloaded files:
> .
> Nachrechnung.tex
> scrartcl.cls 2004/09/16 v2.9t LaTeX2e KOMA document class
> fleqn.clo 1998/08/17 v1.1c Standard LaTeX option (flush left
> equations)
> scrlfile.sty 2004/09/16 v2.9t LaTeX2e KOMA package
> size11.clo 2004/02/16 v1.4f Standard LaTeX file (size option)
> typearea.sty 2004/09/16 v2.9t LaTeX2e KOMA package
> fontenc.sty
> t1enc.def 2004/02/22 v1.99f Standard LaTeX file
> ngerman.sty 1998/07/08 v2.5e Support for writing german texts (br)
> inputenc.sty 2004/02/05 v1.0d Input encoding file
> utf8.def 2004/02/09 v1.1b UTF-8 support for inputenc
> t1enc.dfu 2004/02/09 v1.1b UTF-8 support for inputenc
> ot1enc.dfu 2004/02/09 v1.1b UTF-8 support for inputenc
> omsenc.dfu 2004/02/09 v1.1b UTF-8 support for inputenc
> amsmath.sty 2000/07/18 v2.13 AMS math features
> amstext.sty 2000/06/29 v2.01
> amsgen.sty 1999/11/30 v2.0
> amsbsy.sty 1999/11/29 v1.2d
> amsopn.sty 1999/12/14 v2.01 operator names
> t1cmtt.fd 1999/05/25 v2.5h Standard LaTeX font definitions
> t1cmss.fd 1999/05/25 v2.5h Standard LaTeX font definitions
Normal. And everything looks normal up to here:
> l.27 ...\cdot i_{45} \cdot \eta_{45} = 12.90 Nm \]
>
> [6] )
> (see the transcript file for additional information)
> Output written on Nachrechnung.dvi (6 pages, 2780 bytes).
> Transcript written on Nachrechnung.log.
>
> Preview-LaTeX exited as expected with code 1 at Tue Dec 19 19:05:31
> Running `Preview-DviPS' with ``dvips -Pwww Nachrechnung.dvi -o
> Nachrechnung.prv/tm9234lTP/preview.ps''
> This is dvips(k) 5.95b Copyright 2005 Radical Eye Software
> (www.radicaleye.com)
> ' TeX output 2006.12.19:1905' -> Nachrechnung.prv/tm9234lTP/preview.ps
> <tex.pro><texps.pro><special.pro>. <cmsy10.pfb><cmr10.pfb><cmr8.pfb>
> <cmmi8.pfb><cmmi10.pfb>[1] [2] [3] [4] [5] [6]
>
> Preview-DviPS finished at Tue Dec 19 19:05:32
Fine till here.
But now:
> Running `Preview-Ghostscript' with ``gs -dOutputFile\=\(
> \) -q -dSAFER -dNOPAUSE -DNOPLATFONTS -dPrinted -dTextAlphaBits\=4 -dGraphicsAlphaBits\=4 -sDEVICE\=png16m -r114.025x112.668''
>
> Preview-Ghostscript finished at Tue Dec 19 19:05:33
> Running `Preview-Ghostscript' with ``gs -dOutputFile\=\(
> \) -q -dSAFER -dNOPAUSE -DNOPLATFONTS -dPrinted -dTextAlphaBits\=4
> -dGraphicsAlphaBits\=4 -sDEVICE\=png16m -r114.025x112.668''
And so on. Instead of an output file name, here is an empty string.
In my comparable test, there is
Running `Preview-Ghostscript' with ``gs -dOutputFile\=\(junk.prv/tmp5246ebu/pr1-\%d.png\) -q -dSAFER -dNOPAUSE -DNOPLATFONTS -dPrinted -dTextAlphaBits\=4 -dGraphicsAlphaBits\=4 -sDEVICE\=png16m -r132.114x132.241''
Preview-Ghostscript finished at Thu Dec 21 23:07:28
So you are doing something that messes up the file name generation of
GhostScript within preview-latex. I have no idea what would do that,
and doing a proper bug report with the intended commands to the proper
channels might help pinpointing this.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2006-12-21 22:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-19 18:28 Problem with preview-latex Florian Lindner
2006-12-21 22:16 ` David Kastrup [this message]
2006-12-24 12:02 ` Florian Lindner
2007-01-13 12:15 ` David Kastrup
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=85r6uszyge.fsf@lola.goethe.zz \
--to=dak@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.
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).