ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Eckhart Guthöhrlein" <eckhart_guthoehrlein@public.uni-hamburg.de>
Subject: Re: --automprun does not work
Date: Sat, 14 Jul 2001 11:55:35 +0200	[thread overview]
Message-ID: <5.1.0.14.0.20010714114927.00a9fc48@public.uni-hamburg.de> (raw)
In-Reply-To: <5.1.0.14.0.20010712163807.00a94a60@public.uni-hamburg.de>

At 16:49 12.07.2001 +0200, I wrote:
>Forgot this one. With \write18 enabled, everything works fine now, but not 
>without... \runMPgraphicsfalse (or at least not ..true) in cont-sys.tex is 
>necessary, otherwise texexec assumes on-the-fly generation and does not 
>call mp afterwards.
>The problem is: With
>texexec --automprun --pdf test
>mp is called after the tex runs, but no picture is produced (and possibly 
>that's why no final tex run follows). This is the entire log file mpgraph.log:
>
>This is MetaPost, Version 0.641 (MiKTeX 2.1) (preloaded mem=metafun 
>2001.7.12)  12 JUL 2001 16:42
>**mpgraph
>(mpgraph.mp )
>
>However, compiling mpgraph.mp from the command line via
>mp mpgraph
>works fine!
>
>I can't explain why mp is terminated prematurely when called by texexec. 
>Even more strange, Hans might remember having told me about the --autmprun 
>switch. Everything worked properly on my machine, perhaps one of the 
>latest updates causes problems (but I can't tell which one, if so, for I 
>didn't use mp since then)?

I have to make some additions to this. In principle, everything works well, 
so no problem with texexec due to updates. But there are problems with more 
complex MP code, possibly with metaobj. My test file:

\startreusableMPgraphic{nometaobj}
    draw unitsquare scaled 1cm;
\stopreusableMPgraphic

\startreusableMPgraphic{justinput}
    input metaobj;
    draw unitsquare scaled 1cm;
\stopreusableMPgraphic

\startreusableMPgraphic{metaobj}
    input metaobj;
    newBox.testbox(btex Where is it? etex);
    testbox.c=origin;
    drawObj(testbox);
\stopreusableMPgraphic

\starttext
    \reuseMPgraphic{...}
\stoptext

witth {...}={nometaobj} as well as {...}={justinput}, everything works 
fine. But with {...}={metaobj}, I get the nearly empty log above. Compiling 
via mp mpgraph works. So, this might be some interference with metaobj, or 
perhaps a general problem with complex MP code (but I can't imagine this 
looking at the available examples...)
And as I wrote before, with runtime mp via \write18, all three test 
graphics work.

Eckhart


  reply	other threads:[~2001-07-14  9:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-12 14:49 Eckhart Guthöhrlein
2001-07-14  9:55 ` Eckhart Guthöhrlein [this message]
2001-07-16  7:54   ` Hans Hagen
2001-07-16 13:26     ` Eckhart Guthöhrlein
     [not found] <Your message of "Mon, 16 Jul 2001 15:26:20 +0200." <5.1.0.14.0.20010716151808.00a8e1a8@public.uni-hamburg.de>
2001-07-16 14:08 ` Patrick Gundlach
2001-07-17 10:02   ` Eckhart Guthöhrlein

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=5.1.0.14.0.20010714114927.00a9fc48@public.uni-hamburg.de \
    --to=eckhart_guthoehrlein@public.uni-hamburg.de \
    /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).