unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: David Kastrup <dak@gnu.org>
Subject: Re: File variables in tex-site.el
Date: 30 Apr 2003 16:59:09 +0200	[thread overview]
Message-ID: <x54r4gxc8y.fsf@lola.goethe.zz> (raw)
In-Reply-To: b8o55e$lm8$1@online.de

"Ulrich Dirr" <ud@art-satz.de> writes:

> I'm wondering what all the file variables mean (%t, %f, %s, etc.).
> I would like to customize the list shown below. Where can I find an
> explanation what variables exist and what's their meaning?
> 
> ;; The fpTeX commands.
> (setq TeX-command-list
>   (list (list "TeX" "tex \\nonstopmode\\input %t" 'TeX-run-TeX nil t)
>  (list "LaTeX" "%l \\nonstopmode\\input{%t}" 'TeX-run-LaTeX nil t)
>  (list "LaTeX PDF" "pdflatex \\nonstopmode\\input{%t}" 'TeX-run-LaTeX
> nil t)
>  (list "eLaTeX PDF" "pdfelatex \\nonstopmode\\input{%t}" 'TeX-run-LaTeX
> nil t)
>  (list "View" "%v" 'TeX-run-command t nil)
>  (list "View PS" "gsview32 %f" 'TeX-run-command t nil)
>  (list "View PDF" "start %s.pdf" 'TeX-run-command t nil)
>  (list "Print" "dvips %d" 'TeX-run-command t nil)
>  (list "File" "dvips %d -o %f " 'TeX-run-command t nil)
>  (list "BibTeX" "bibtex %s" 'TeX-run-BibTeX nil nil)
>  (list "Index" "makeindex %s" 'TeX-run-command nil t)
>  (list "Check" "lacheck %s" 'TeX-run-compile nil t)
>  (list "Spell" "<ignored>" 'TeX-run-ispell-on-document nil nil)
>  (list "Makeinfo" "makeinfo %t" 'TeX-run-compile nil t)
>  (list "AmSTeX" "amstex \\nonstopmode\\input{%t}" 'TeX-run-TeX nil t)
>  (list "Other" "" 'TeX-run-command t t)))

Oh shit.  _That's_ the reason why your stuff does not work
intuitively with PDFLaTeX now.  Please take a look at the settings of
this variable in tex.el, change fptex.el accordingly and submit a
patch.  I am afraid that fptex.el has fallen behind times.  Perhaps
one should let the code in fptex.el rather just modify those settings
in tex.el that are relevant.  We need an fptex.el maintainer,
obviously.  I don't think that any of the current developers of
AUCTeX actually uses Windows.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum

  parent reply	other threads:[~2003-04-30 14:59 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-30  9:31 File variables in tex-site.el Ulrich Dirr
2003-04-30 14:34 ` Kai Großjohann
2003-04-30 14:59 ` David Kastrup [this message]
2003-05-01  8:09   ` Ulrich Dirr
2003-05-01  9:26     ` David Kastrup
2003-05-01 15:11     ` Piet van Oostrum
2003-05-02  5:30       ` Ulrich Dirr
2003-05-02 10:44         ` Piet van Oostrum
2003-05-03  7:04           ` Ulrich Dirr
2003-05-03  9:01             ` David Kastrup
2003-05-01 22:47     ` Stefan Monnier
2003-05-01 10:00 ` Dr. F.C.Caner
2003-05-02 13:07   ` Matthias Rempe
2003-05-05  8:36     ` Dr. F.C.Caner
2003-05-05 22:30       ` Matthias Rempe
2003-05-05 23:01       ` Jesper Harder
2003-05-06  5:41         ` Dr. F.C.Caner
2003-05-07 11:28           ` Dr. F.C.Caner
2003-05-07 16:45             ` Matthias Rempe
2003-05-08  6:00               ` Dr. F.C.Caner

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=x54r4gxc8y.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).