From: Hans Hagen <pragma@wxs.nl>
Subject: Re: Re: Installation problem
Date: Tue, 22 Jun 2004 12:35:53 +0200 [thread overview]
Message-ID: <40D80B89.4020403@wxs.nl> (raw)
In-Reply-To: <m23c4nnba8.fsf@levana.de>
Patrick Gundlach wrote:
> <>here is my solution:
>
> in texexec.ini change
>
> set TeXFormatFlag to &
>
> into:
> set TeXFormatFlag to
>
> (empty)
>
>
> and run texexec like:
>
> texexec --tex=pdfetex file.tex
>
>
> this is because texexec checks
>
> if ( $TeXFormatFlag eq "" ) {
> if ($TeXProgram =~ /(etex|pdfetex)/) {
> $TeXFormatFlag = "-efmt=" ; # >=2004 -fmt=
> } elsif ($TeXProgram =~ /(eomega)/) {
> $TeXFormatFlag = "-eoft=" ; # >=2004 obsolete
> } elsif ($TeXProgram =~ /(aleph)/) {
> $TeXFormatFlag = "-fmt=" ;
> } else {
> $TeXFormatFlag = "-fmt=" ;
> }
> }
indeed, the texexec.rme file is changed accordingly; i needed that
change because & is giving to much problems in nested calls; also, next
year there will be changes again because from now on web2c formats will
be fmt, like
web2c/pdfetex/cont-en.fmt
instead of
web2c/cont-en.efmt
(currently both -efmt and -fmt are handled by the latest pdfetex) ; i
didn't check miktex yet
> <>and $TeXProgram is not set to $TeXExecutable (why the two different
> vars?)
dunno, must have a look
Hans
next prev parent reply other threads:[~2004-06-22 10:35 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-21 8:28 Matt Gushee
2004-06-21 8:45 ` Patrick Gundlach
2004-06-21 9:22 ` Matt Gushee
2004-06-21 9:29 ` Patrick Gundlach
2004-06-21 10:06 ` Matt Gushee
2004-06-21 14:57 ` Patrick Gundlach
2004-06-21 15:11 ` Hans Hagen
2004-06-21 20:51 ` Patrick Gundlach
2004-06-22 8:32 ` Hans Hagen
2004-06-22 8:51 ` Patrick Gundlach
2004-06-22 9:11 ` Hans Hagen
2004-06-22 10:21 ` Patrick Gundlach
2004-06-22 10:35 ` Hans Hagen [this message]
2004-06-21 15:34 ` Matt Gushee
2004-06-25 8:32 ` Patrick Gundlach
2004-06-21 8:46 ` Thomas A. Schmitz
2004-06-21 9:05 ` Hans Hagen
2004-10-16 5:43 Installation Problem David Arnold
2004-10-16 9:55 ` Patrick Gundlach
2004-10-16 17:06 ` David Arnold
2004-10-17 20:06 ` h h extern
2004-10-16 15:46 ` Problem Larry Stamm
2004-10-16 19:08 ` David Arnold
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=40D80B89.4020403@wxs.nl \
--to=pragma@wxs.nl \
--cc=ntg-context@ntg.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 NNTP newsgroup(s).