From: David Kastrup <dak@gnu.org>
Subject: Re: File variables in tex-site.el
Date: 01 May 2003 11:26:49 +0200 [thread overview]
Message-ID: <x5llxrrp9i.fsf@lola.goethe.zz> (raw)
In-Reply-To: b8qko3$hsr$1@online.de
"Ulrich Dirr" <ud@art-satz.de> writes:
> David Kastrup wrote:
> > "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
> >
> > 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.
>
> I looked at tex.el and changed, e.g.,
> (list "eLaTeX PDF" "pdfelatex \"\\nonstopmode\\input{%t}\""
> 'TeX-run-TeX nil t)
> accordingly. But I still don't understand what's the difference in
> behavior (ok, now I'll save some keystrokes). I still have to type C-c
> C-c after successfully compiling to view the file; getting 'Command:
> (default View)'; changing it to 'View PDF'; RET; etc.
The main difference was to the View command: it views PDF per default
if you used PDFLaTeX for producing PDF.
> And of course it would be a nice feature if Emacs could close
> any PDF document in Acrobat(Reader) before compiling (because Acrobat
> blocks the file) and changing to Acrobat if all above was successfully
> done.
I think that is not possible with Acrobat Reader.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2003-05-01 9:26 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
2003-05-01 8:09 ` Ulrich Dirr
2003-05-01 9:26 ` David Kastrup [this message]
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=x5llxrrp9i.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).