Re: rel-0-8-1; Default options are always used, even when package is loaded

[email protected] (Frank Küster) Mon, 21 Feb 2005 22:29:53 +0100
Newsgroups gmane.emacs.latex.preview.devel
Message-ID <87is4l1u0e.fsf__42145.8069853999$1109082166$gmane$org@alhambra.kuesterei.ch>
David Kastrup <[email protected]> schrieb:

> [email protected] (Frank K=FCster) writes:
>
>> David Kastrup <[email protected]> wrote:
>>
>>> [email protected] (Frank K=FCster) writes:
>>>
>>>> Indeed the problem seems to be something different; it only showed
>>>> up at a sectioning command. This is a minimal test file:
>>>>
>> [...]
>>> There is no sectioning command here.
>>
>> Cool, right? Frank says that it doesn't need a sectioning command,
>> only showed up by chance at a sectioning command, and in the minimal
>> file there isn't one.
>
> Well, _what_ problem?  Your original complaint was that preview-latex
> was previewing sectioning commands although it shouldn't.  And you
> illustrate this with an example without sectioning commands, saying
> that the problem will be the same nevertheless.  How can the problem
> be that sectioning commands get previewed?

Excuse me, I wasn't clear in the first mail. The general symptom, from
the beginning, was that _no_ previews were generated. The first roadwork
sign that was left in the buffer happened to be at a sectioning command;
and then it occured to me that preview-latex shouldn't have tried to
create a preview for it, because of my explicit \usepackage line without
a [sectioning] option. This was as far as I got, but instead of
describing the real problem (no previews at all) I described what I
thought was the reason - that it tried to generate sectioning previews
while I didn't request that. Maybe this is a different bug (or
misconfiguration), but currently the bug is: No previews at all.

>>> Why shouldn't preview-latex run pdflatex when you are working with
>>> a PDFTeX mode document?
>>
>> I don't know.  There's not much about pdf in the manual, only some -Ppdf
>> switches to dvips, and a remark in the Todo node.
>
> Then I recommend that you replace the old manual that does not seem to
> match your version of preview-latex (which is 0.8.1, according to the
> log files you sent).

Ups. There was an ancient version (but not the old Debian version from
woody), and it had info files installed in /usr/info (instead of
/usr/share/info)!.=20

> I'd say you did something too clever, namely asking for error help on
> a preview run.

I saw the roadwork signs and thought there might have been one. Well, I
should try to be less clever, it seems ;-)

>          Preview-LaTeX exited abnormally with code 1 at Wed Sep  4 17:03:=
30
>        after the LaTeX run in the run buffer.  This merely indicates that
>     errors were present, and errors will always be present when
>     preview-latex is operating.  There might be also real errors, so in
>     case of doubt, look for them explicitly in either run buffer or the
>     resulting `.log' file.

The log file doesn't show any real errors.=20

>> You can look at it at
>>
>> http://www.kuesterei.ch/preview.gif
>
> Sigh.  That is no roadworks sign.  That is an error indicator (Danger
> ahead).  Ok, the mnemonic value of this icons suck.  Since it is
> remarkably difficult to get a well-looking symmetric exclamation mark
> and we are currently redesigning icons, anyway, what icon do you
> propose instead for indicating an error?  A car falling off into
> water?  A "STOP" sign?=20

A flash of lightning, like a mathematical sign used after a proof by
contradiction? A traffic sign smashed into pieces, flying apart? In any
case I suggest to change the shape of the sign. Although we have been
talking about manikins, I didn't actually look inside...

> Click it with middle mouse button.  The
> resulting report should be interesting.

gs -q -dSAFER -dDELAYSAFER -dNOPAUSE -DNOPLATFONTS -dPrinted -dTextAlphaBit=
s\=3D4 -dGraphicsAlphaBits\=3D4 -sDEVICE\=3Dpng16m -r123.035x122.862
GS>/.preview-BP currentpagedevice/BeginPage get dup null eq {pop{pop}bind}i=
f def <</BeginPage{currentpagedevice/PageSize get dup 0 get 1 ne exch 1 get=
 1 ne or{.preview-BP gsave 0.705882 0.933333 0.705882 setrgbcolor false set=
strokeadjust 3 setlinewidth clippath strokepath matrix setmatrix true {2 in=
dex{newpath}if round exch round exch moveto pop false}{round exch round exc=
h lineto}{curveto}{closepath}pathforall pop fill grestore }{pop}ifelse}bind=
/PageSize[1 1]>>setpagedevice/preview-do{[count 3 roll save]3 1 roll{setpag=
edevice}stopped{handleerror quit}if cvx systemdict/.runandhide known{.setsa=
fe(AFPL Ghostscript)product ne{<<>>setpagedevice}if{.runandhide}}if stopped=
{handleerror quit}if count 1 ne{quit}if aload pop restore<</OutputFile(/dev=
/null)>>setpagedevice}bind def (_region_.prv/tmp4410VCl/preview.dsc)(r)file=
 dup dup 0 setfileposition 425()/SubFileDecode filter cvx exec dup dup 425 =
setfileposition 50()/SubFileDecode filter cvx <</OutputFile(_region_.prv/tm=
p4410VCl/prev001.png)>>preview-do
Error: /invalidfileaccess in --.outputpage--
Operand stack:
   1   true
Execution stack:
   %interp_exit   .runexec2   --nostringval--   --nostringval--   --nostrin=
gval--   2   %stopped_push   --nostringval--   --nostringval--   %loop_cont=
inue   2   3   %oparray_pop   --nostringval--   --nostringval--   false   1=
   %stopped_push   .runexec2   --nostringval--   --nostringval--   --nostri=
ngval--   2   %stopped_push   --nostringval--   --nostringval--   false   1=
   %stopped_push   1148   --nostringval--   %end_runandhide   --nostringval=
--   --nostringval--   --nostringval--   0   8   %oparray_pop   --nostringv=
al--   --nostringval--   --nostringval--   --nostringval--
Dictionary stack:
   --dict:1055/1123(ro)(G)--   --dict:0/20(G)--   --dict:76/200(L)--   --di=
ct:100/127(ro)(G)--   --dict:230/230(ro)(G)--   --dict:19/24(L)--   --dict:=
4/6(L)--   --dict:22/31(L)--
Current allocation mode is local

Preview-GhostScript finished

There is a _region_.pdf which contains an \alpha in a tight bounding box
(by the way, is it possible to view page boundaries in xpdf? I always
get white paper on white background with no border line, and have to use
acroread to check sizes).

This is the dsc file in _region_.prv/tmp4447vHl/:

%!PS-Adobe-3.0
%%CreationDate: (D:20050221222600)
%%DocumentMedia: y5.289x6.266 6.266 5.289 70 white ()
%%Pages: 1
%%EndComments
%%BeginProlog
/Page null def
/Page# 0 def
/PDFSave null def
/DSCPageCount 0 def
/DoPDFPage {dup /Page# exch store pdfgetpage pdfshowpage } def
GS_PDF_ProcSet begin
pdfdict begin
%%EndProlog
%%BeginSetup
(_region_.pdf) (r) file { DELAYSAFER { .setsafe } if } stopped pop
 pdfopen begin
%%EndSetup
%%Page: 1 1
%%PageMedia: y5.289x6.266
1 DoPDFPage
%%Trailer
currentdict pdfclose
end
end
end
%%EOF

Regards, Frank
--=20
Frank K=FCster
Inst. f. Biochemie der Univ. Z=FCrich
Debian Developer



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
preview-latex-bugs mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/preview-latex-bugs


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click