From: Zeljko Vrba <mordor@fly.srk.fer.hr>
Cc: ntg-context@ntg.nl
Subject: Re: Why does metapost refuse to run a perfectly legal file?
Date: Thu, 14 Sep 2000 09:57:01 +0200 [thread overview]
Message-ID: <20000914095701.A26256@fly.srk.fer.hr> (raw)
In-Reply-To: <39C07BB3.6AF74C2F@pobox.com>; from berend@pobox.com on Thu, Sep 14, 2000 at 09:18:11AM +0200
On Thu, Sep 14, 2000 at 09:18:11AM +0200, Berend de Boer wrote:
> Hello All,
>
> For no apparent reason metapost often refuses to run a file (perhaps
> this is related to my previous question??). When context generates the
> mpgraph.mp and metapost is run its log file is:
>
> This is MetaPost, Version 0.641 (Web2C 7.3.1) (mem=metafun 2000.9.14)
> 14 SEP 2000 07:21
> **&metafun mpgraph
> (mpgraph.mp)
> ! Emergency stop.
> <*> &metafun mpgraph
>
> *** (job aborted, no legal end found)
>
>
> However, if I manually say metapost &metafun mpgraph everything is fine.
>
You have to put end at the end of file, like this:
end
next prev parent reply other threads:[~2000-09-14 7:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-14 7:18 Berend de Boer
2000-09-14 7:57 ` Zeljko Vrba [this message]
2000-09-14 8:42 ` 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=20000914095701.A26256@fly.srk.fer.hr \
--to=mordor@fly.srk.fer.hr \
--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).