David Kastrup <[email protected]> writes: >> In what cases would AUCTeX automatically determine that it should >> compile to PDF instead of DVI and vice versa? > > Looking in latex.el shows something like > > (TeX-add-style-hook "pdftex" 'TeX-PDF-mode-on) > (TeX-add-style-hook "pdftricks" 'TeX-PDF-mode-on) > (TeX-add-style-hook "pst-pdf" 'TeX-PDF-mode-on) > (TeX-add-style-hook "dvips" 'TeX-PDF-mode-off) > ;; This is now done in style/pstricks.el because it prevents other > ;; pstricks style files from being loaded. > ;; (TeX-add-style-hook "pstricks" 'TeX-PDF-mode-off) > (TeX-add-style-hook "psfrag" 'TeX-PDF-mode-off) > (TeX-add-style-hook "dvipdf" 'TeX-PDF-mode-off) > (TeX-add-style-hook "dvipdfm" 'TeX-PDF-mode-off) > ;; (TeX-add-style-hook "DVIoutput" 'TeX-PDF-mode-off) > ;; > ;; Well, DVIoutput indicates that we want to run PDFTeX and expect to > ;; get DVI output. Ugh. > (TeX-add-style-hook "ifpdf" (lambda () > (TeX-PDF-mode-on) > (TeX-PDF-mode-off))) > ;; ifpdf indicates that we cater for either. So calling both > ;; functions will make sure that the default will get used unless the > ;; user overrode it.
Ah, yes, of course that makes sense. But probably the average user like Michel or me doesn't use any of those packages. Thanks, Tassilo _______________________________________________ bug-auctex mailing list [email protected] https://lists.gnu.org/mailman/listinfo/bug-auctex
