From: Aditya Mahajan <adityam@umich.edu>
Subject: some commands still use texexec without texmfstart
Date: Tue, 28 Feb 2006 17:54:50 -0500 (EST) [thread overview]
Message-ID: <Pine.WNT.4.63.0602281747330.904@nqvgln> (raw)
Hi,
I use a standalone context distribution in parallel with miktex. The
way miktex is configured, it provides a texexec.exe file in its bin
directory. Context provides a texexec.bat file in its bin directory.
Normally, texexec is supposed to be run using texmfstart which picks
texexec.rb from the script directory and everything works fine. There
are however some macros that call texexec without texmfstart. As a
result the miktex texexec (texexec.exe) is called over context's
texexec.bat. I am listing the files that call raw texexec. Shouldn't
all of these be called using texmfstart?
1. core-fig.tex has a line
\executesystemcommand{texmfstart texexec.pl --batch --pdf #1 #3}}
Notice the texexec.pl
2. page-app.tex has a line
\executesystemcommand{texexec \bufferprefix\@@texapp.tex --once
--batch}
No texmfstart
3. supp-mps.tex has a definition
\def\executeMPTEX#1%
{texexec ....
}
No texmfstart
Some support scripts also use texexec without texmfstart
1. mptopdf.pl has a line
$mpbin = 'texexec --mptex $PassOn' }
2. texfont.pl has
if ($show) { system ("texexec --once --silent $texfile") }
3. texsync uses
system("texexec --make --alone #{str}")
4. ctxtools.rb uses
one = "texexec --make --alone --all #{interface}"
two = "texexec --batch --silent --interface=#{interface} x-set-01"
5. pdftrimwhite uses
$result = `texexec --batch --once --purge $resultfile` }
6. makempy.pl uses
$tex{context} = "texexec --batch --once --interface=en --pdf" ;
--
Aditya Mahajan, EECS Systems, University of Michigan
http://www.eecs.umich.edu/~adityam || Ph: 7342624008
reply other threads:[~2006-02-28 22:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=Pine.WNT.4.63.0602281747330.904@nqvgln \
--to=adityam@umich.edu \
--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).