From: Hans Hagen <pragma@wxs.nl>
Cc: ntg-context@ntg.nl
Subject: Re: Metapost
Date: Sun, 10 Nov 2002 22:02:11 +0100 [thread overview]
Message-ID: <5.1.0.14.1.20021110215431.0231c480@remote-1> (raw)
In-Reply-To: <000501c287f8$59655ed0$010a0a0a@michal>
At 02:57 PM 11/9/2002 +0100, you wrote:
>I have tried to repeat the example in the file "Creating metapost examples"
>(mmakempy.pdf) and I receive result as below and empty place in my document.
>Can anyone give me a hint?
>
>This is MetaPost, Version 0.641 (Web2c 7.3.7x) (mem=metafun 2002.10.31) 31
>OCT 2002 22:25
>**&metafun mpgraph
>(mpgraph.mp
>{randomseed:=3603}
> (d:/TeXLive/texmf/metapost/base/graph.mp
>(d:/TeXLive/texmf/metapost/base/format.mp
>(d:/TeXLive/texmf/metapost/base/string.mp)
>(d:/TeXLive/texmf/metapost/base/texnum.mp
> >> d:/TeXLive/texmf/metapost/base/texnum.mp
> >> texnum.mpx
>! Unable to make mpx file.
>l.14 init_numbers(btex
> $-$etex, btex$1$etex, btex${\times}10$etex,
>The two files given above are one of your source files
>and an auxiliary file I need to read to find out what your
>btex..etex blocks mean. If you don't know why I had trouble,
>try running it manually through MPto -tex, TeX, and DVItoMP.
you have a name clash with a system file (somewhere else in your tex path);
this can be solved by making sure that in case of context, tex searches on
the local path first (can be done in texmf.cnf); i'm a bit puzzled, because
context should make a fake file on the current path). Another option is to
protect your temp job files with (in cont-sys.tex):
\protectbufferstrue
or more obscure, you can change the name of the temp files,
\def\MPgraphicfile{\bufferprefix mp\ifMPrun run\else graph\fi}
say mp -> mps , but first try the buffers
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
-------------------------------------------------------------------------
information: http://www.pragma-ade.com/roadmap.pdf
documentation: http://www.pragma-ade.com/showcase.pdf
-------------------------------------------------------------------------
next prev parent reply other threads:[~2002-11-10 21:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-09 13:57 Metapost Michał Morawski
2002-11-10 21:02 ` Hans Hagen [this message]
2002-11-10 23:43 ` Metapost Adam Lindsay
2002-11-10 21:10 ` Metapost K.H. Wesseling
-- strict thread matches above, loose matches on Subject: below --
2010-02-17 21:18 metapost Martin 'golodhrim' Scholz
2010-02-17 21:31 ` metapost Hans Hagen
2010-02-17 21:34 ` metapost Mojca Miklavec
2010-02-17 21:37 ` metapost Mojca Miklavec
2001-09-08 17:48 Metapost Joop Susan
2001-09-10 9:25 ` Metapost Hans Hagen
1999-08-23 5:08 Metapost David Arnold
1999-08-23 8:31 ` Metapost 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=5.1.0.14.1.20021110215431.0231c480@remote-1 \
--to=pragma@wxs.nl \
--cc=ntg-context@ntg.nl \
--cc=ntg-context@ref.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).