* Giacomo Boffi (2011-03-27) writes: > Ralf Angeli writes: > > > It looks like the document class or some package sets \pdfoutput. > > There is even a warning about this by the ifpdf package in the log. > > If \pdfoutput is set, preview.sty assumes that PDFLaTeX is used. > > It then checks the value of \pdfoutput in order to find out if PDF > > output is produced. In your example the value is 0, so preview.sty > > comes to the conclusion that DVI output is produced. And that's > > why preview-latex then calls dvips. > > > > I didn't look by whom \pdfoutput is set to 0, but this looks a bit > > fishy. Do you happen to know where and why this is done? > > i don't, sorry
It looks like beamer.cls does this itself: ,----[ from beamer.cls ] | % | % Ensure that \pdfoutput is defined. Might be removed at some point. | % | \ifx\pdfoutput\@undefined \newcount\pdfoutput \fi | \ifx\pdfoutput\relax \newcount\pdfoutput \fi `---- > > In any case, either the document class or some package loads > > hyperref and recent versions of it are incompatible with > > preview.sty. So even if we can get rid of the \pdfoutput problem, > > you won't have much joy with this combination. > > my debian has texlive 2009, so newest releases of hyperref shouldn't > cast too dark a shadow on my texing... I think the incompatibility already exists in this release. I'm using the same version of TeX Live and when I load hyperref in circ.tex (the preview-latex showcase), preview-latex complains that it found no previews. At least when it is run on the document. Running it at point oddly seems to work. -- Ralf _______________________________________________ bug-auctex mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-auctex
