From: Pierre Goossens <pierre.goossens@wxs.nl>
Cc: ntg-context@ntg.nl
Subject: Re: Metapost samples
Date: Mon, 20 Nov 2000 23:43:21 +0100 [thread overview]
Message-ID: <3.0.6.32.20001120234321.007bbaf0@pop.wxs.nl> (raw)
In-Reply-To: <20001120113430.D2775@cs.ucc.ie>
At 11:34 20-11-00 +0000, you wrote:
>David Arnold (darnold@northcoast.com) wrote:
>
>: Here's a nice round of simple graphics in Metapost that I used on my calc
>: review sheet for an upcoming exam.
>
>[snip]
>
>I tried to run it through mpost on my machine but
>that didn't work. Am I right to assume that it
>requires some ConTeXt built-ins? If so, can they
>be isolated from the ConTeXt distribution?
>
>Regards,
>
>
>Marc
>
Hello Marc,
Because that was also the case with me (the not-working part) I made
separate files for every figure in the original pretest.mp file.
It turns out that the figures 1, 2, 7, 9 and 10 suffer the same symptoms.
This is what my MikTeX logging has to say about it:
-----------------
This is MetaPost, Version 0.641 (MiKTeX 1.20e) (preloaded mem=plain
2000.9.9) 20 NOV 2000 23:15
**mp1
(mp1.mp (C:\texmf\metapost\context\mp-tool.mp)
>> anglebetween
! Improper `addto'.
<to be read again>
withpen
draw->...PR0)else:doublepath(EXPR0)withpen
.currentpen.fi._op_
<to be read again>
(
l.31 draw anglebetween(
(0,0)--(3u,0),(0,0)--(0,4u),"");
? h
This expression should have specified a known path.
So I'll not change anything just now.
? x
-----------------
The 'known path' part returns in all said figures. I haven't looked into
this further as I am still ploughing through the metafun-p.pdf . A very
readable manual by the way.
Succes,
Pierre
next prev parent reply other threads:[~2000-11-20 22:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-17 18:22 David Arnold
2000-11-19 21:55 ` Hans Hagen
2000-11-20 11:34 ` Marc van Dongen
2000-11-20 12:30 ` Hans Hagen
2000-11-20 22:43 ` Pierre Goossens [this message]
2000-11-21 8:44 ` 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.20001120234321.007bbaf0@pop.wxs.nl \
--to=pierre.goossens@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).