From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/4923 Path: main.gmane.org!not-for-mail From: Eckhart =?iso-8859-1?Q?Guth=F6hrlein?= Newsgroups: gmane.comp.tex.context Subject: problem with texexec and inline metapost Date: Tue, 03 Jul 2001 20:01:31 +0200 Sender: owner-ntg-context@let.uu.nl Message-ID: <5.1.0.14.0.20010703192446.00a94340@public.uni-hamburg.de> NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Trace: main.gmane.org 1035395555 29866 80.91.224.250 (23 Oct 2002 17:52:35 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Wed, 23 Oct 2002 17:52:35 +0000 (UTC) Original-To: ConTeXt mailing list Xref: main.gmane.org gmane.comp.tex.context:4923 X-Report-Spam: http://spam.gmane.org/gmane.comp.tex.context:4923 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. Eckhart