From: Hans Hagen <pragma@wxs.nl>
Subject: running mp
Date: Wed, 23 Jan 2002 09:26:37 +0100 [thread overview]
Message-ID: <5.1.0.14.1.20020123091314.032dd560@server-1> (raw)
In-Reply-To: <200201221853.TAA25814@smail.let.uu.nl>
[forwarded mail; can you use an address that is known to the list?]
From: Daniel Joyce <daniel.a.joyce@worldnet.att.net>
> Only MetaPost commands that do not contain embedded btex etex
> commands
>seem to work.
>
> If it has btex etex in it, it never generates a mpgraph.1 file.
>
> Also, even though I have it set up so that texexec should call
> Mpost, it
>never does. I have to do...
>
> texexec --pdf foo.tex
> texexec --mptex mpgraph.mp
> texexec --mptex mprun.mp
> texexec --pdf foo.tex
>
> If I look in the log, it shows the command chaining that should
> mean that
>it's doing it all by itself, but I still have to run it manually, it has no
>effect.
>
> Also, if the MP command has a btex etex pair in it, when running
> texexec
>--mptex, it doesn't say it's creating mpgraph.1, it says it's creating a
>dvi file, but no dvi file is to be found when it completes.
I'm a bit puzzled and it's hard to identify the problem from a distance.
The btex/etex part of mp is rather fuzzy and since the mpto tools work on
temp files, it's hard to trace where things go wrong. In texexec, I try to
prevent some problems (like breaking too long lines, identifying btex and
alike), but i still rely on the filtering of the tools (maybe i should let
texexec take care of that too).
Now, when you embed mp code in your tex doc, context itself will try to
identify btex/textext/... constructs and when running 'realtime' it will
run either mp without or with tex processing. If you use the write18
method, you can force tex runs with
\forceMPTEXgraphictrue
but normally this is not needed.
If you enable write 18, as well as set the switches in cont-sys.tex (see
cont-sys.rme for what is needed), the realtime options whould work. If this
works ok, then the --automp option should also work (forces non real time
and identifies how to run).
[here, when i make graphics, i always use the real time options, but i run
manuals with --automp; the whole metafun manual runs without problems and
it's my big test case, since it has about every nasty call you can imagine.]
If you still have problems, send me the smallest problematic file possible.
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
-------------------------------------------------------------------------
fall-back web server:
www.pragma-pod.nl
-------------------------------------------------------------------------
parent reply other threads:[~2002-01-23 8:26 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <200201221853.TAA25814@smail.let.uu.nl>]
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.1.20020123091314.032dd560@server-1 \
--to=pragma@wxs.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).