[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[AUCTeX-devel] Re: XeTeX

From: Ralf Angeli
Subject: [AUCTeX-devel] Re: XeTeX
Date: Tue, 06 Jun 2006 23:24:29 +0200

* David Kastrup (2006-06-06) writes:

> Peter Dyballa <address@hidden> writes:
>> On Mac OS X. Some day I'll have a MacBook (Pro) with a Merom
>> processor enabling me to run more than one OS at the same time.

That sounds like a threat.

> In that case, you should take a look at how Omega support is
> implemented.

Which I don't really like because it is rather unflexible.  I'd prefer
a solution where it is not necessary to have a whole set of variables
for a new engine but where this could be handled by a list of
processors which could e.g. include information about executables and
command line switches used at various occasions in AUCTeX.  Processor,
viewer etc. could be chosen by looking at activated modes, values of
variables or document properties.  A few months ago I played a bit
with the idea and wrote this:

(defcustom TeX-processor-alist ()
  '((tex . "tex")
    (pdftex . "pdftex")
    (latex . "latex")
    (pdflatex . "pdflatex")
    (omega . "omega")
    (lambda . "lambda")
    (xetex . "xetex")
    (xelatex . "xelatex")))

(defun TeX-processor ()
  "Return the macro processor as a string."
  (assq (cond ((and plain-TeX-mode TeX-omega-mode)
               (if (or TeX-PDF-mode TeX-DVI-via-PDFTeX) pdftex tex))
              ((and LaTeX-mode TeX-Omega-mode)
               (if (or TeX-PDF-mode TeX-DVI-via-PDFTeX) pdflatex latex)))

(defun TeX-set-processor (processor)
  (setq TeX-processor processor)
  (cond ((memq processor '(xetex xelatex))
         (TeX-PDF-mode 1))
        ((memq processor '(lambda omega))
         (TeX-PDF-mode 0))))

(defcustom TeX-expand-list
    ("%(processor)" TeX-processor)

But I never really went further down this road and thought it through.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]