From: Piet van Oostrum <piet@cs.uu.nl>
Subject: Re: File variables in tex-site.el
Date: 02 May 2003 12:44:32 +0200 [thread overview]
Message-ID: <wzllxp4ohb.fsf@nono.cs.uu.nl> (raw)
In-Reply-To: b8svpk$fta$1@online.de
>>>>> "Ulrich Dirr" <ud@art-satz.de> (UD) wrote:
UD> Piet van Oostrum wrote:
>> Actually the View command itself determines what kind of file was
>> produced and can be parameterized to do the proper thing to open the
>> file.
UD> Could you please give me some concrete hints ('... can be
UD> parameterized')?
(defcustom TeX-output-view-style
'(("^dvi$" ("^a5$" "^landscape$") "xdvi \"%d\" -paper a5r -s 4")
("^dvi$" "^a5$" "xdvi \"%d\" -paper a5")
("^dvi$" ("^landscape$" "^pstricks$\\|^psfrag$")
"dvips -t landscape -f \"%d\" | gv")
("^dvi$" "^landscape$" "xdvi \"%d\" -paper a4r -s 4")
("^dvi$" "^pstricks$\\|^psfrag$" "dvips -f \"%d\" | gv")
("^dvi$" "." "xdvi \"%d\"")
("^pdf$" "^landscape$" "xpdf -papertype a4r \"%o\"")
("^pdf$" "." "xpdf \"%o\"")
("^html?$" "." "netscape \"%o\""))
"List of output file extensions and view options.
So this tells that if you generated a .dvi file it views with xdvi, but if
you generated a .pdf file, it views with xpdf. And then as you can see it
is also parameterized with options and packages.
If you use LaTeX PDF rather than LaTeX it knows that the output file was
.pdf rather than .dvi.
Please note that this is still not fixed in stone, i.e. we might come up
with a more flexible and easier to use system if someone has a bright
idea. For example the options and packages now easily lead to a
combinatorial explosion. So an easier system to build up the commands from
parts might be preferable.
--
Piet van Oostrum <piet@cs.uu.nl>
URL: http://www.cs.uu.nl/~piet [PGP]
Private email: P.van.Oostrum@hccnet.nl
next prev parent reply other threads:[~2003-05-02 10:44 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
2003-05-01 15:11 ` Piet van Oostrum
2003-05-02 5:30 ` Ulrich Dirr
2003-05-02 10:44 ` Piet van Oostrum [this message]
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=wzllxp4ohb.fsf@nono.cs.uu.nl \
--to=piet@cs.uu.nl \
/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).