From: Hans Hagen <pragma@wxs.nl>
Cc: ConTeXt mailing list <ntg-context@ntg.nl>
Subject: Re: problem with texexec and inline metapost
Date: Wed, 04 Jul 2001 08:47:05 +0200 [thread overview]
Message-ID: <3.0.6.32.20010704084705.00fd56a0@server-1> (raw)
In-Reply-To: <5.1.0.14.0.20010703192446.00a94340@public.uni-hamburg.de>
At 08:01 PM 7/3/01 +0200, Eckhart Guthöhrlein wrote:
>When running texexec over my input file containing a metapost graphic
>(first time, no mpgraph files exist), metapost is called after the first
>run, but then tex is not called again. Therefore, I have to call texexec
>twice to actually get the graphics in my dvi file. Accordingly, changes to
>the mp code become effective only after the second call to texexec (when
>creating pdf. - the dvi driver of course finds the updated file after the
>first run). I thought texexec would do this job for me, so perhaps there is
>a switch I didn't see yet?
>When I enable \write18 and \runMPgraphicstrue, creating graphics during
>runtime works fine. But I would prefer to have \write18 disabled.
>I tried 'texexec --mptex xyz', but then texexec just quits after its
>version message, doing nothing else. ?
>I'm using the latest version of context/texexec together with miktex 2.1.
>Maybe I should just take a break, but I don't see what I have left to try.
What latest? The ones i uploaded the last few days *do* an extra pass with
external mp graphics {based on checksum calculation] but only with the
undocumented --automprun, so
texexec --automprun yourfile.tex
Hans
-------------------------------------------------------------------------
Hans Hagen | PRAGMA ADE | pragma@wxs.nl
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
next prev parent reply other threads:[~2001-07-04 6:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-03 18:01 Eckhart Guthöhrlein
2001-07-04 6:47 ` Hans Hagen [this message]
2001-07-04 7:30 ` Eckhart Guthöhrlein
2001-07-14 10:02 ` Eckhart Guthöhrlein
2001-07-14 10:35 ` Taco Hoekwater
2001-07-14 10:38 ` Eckhart Guthöhrlein
2001-07-14 10:57 ` Taco Hoekwater
2001-07-16 7:33 ` Hans Hagen
2001-07-14 16:27 Eckhart Guthöhrlein
2001-07-16 7:36 ` Hans Hagen
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=3.0.6.32.20010704084705.00fd56a0@server-1 \
--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).