From: Andres Loeh <andres@cs.uu.nl>
Subject: Re: Integrating Metapost
Date: Fri, 31 Oct 2003 00:40:59 +0100 [thread overview]
Message-ID: <20031030234059.GA2605@cs.uu.nl> (raw)
In-Reply-To: <6.0.0.22.2.20031030184401.01dc9788@server-1>
> >>>>> local_multi_par_area
> >>>>> false
> >
> >! Equation cannot be performed (numeric=boolean).
>
> looks like an old version of metafun with a new version of context; make
> sure that the metafun macros are in metapost/context/base (and not in one
> of the parent directories) and regenerate the format (texexec --make
> --alone metafun)
This seems to be a very common problem. Isn't it possible
to integrate a check into the metafun code so that a more
helpful error message is produced in case of a format
version mismatch?
Groeten,
Andres
--
Andres Loeh, Universiteit Utrecht
mailto:andres@cs.uu.nl mailto:mail@andres-loeh.de
http://www.andres-loeh.de
next prev parent reply other threads:[~2003-10-30 23:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-30 7:44 Lutz Haseloff
2003-10-30 12:54 ` Nigel King
2003-10-30 15:30 ` Patrick Gundlach
2003-10-30 17:45 ` Hans Hagen
2003-10-30 23:40 ` Andres Loeh [this message]
2003-10-31 10:55 ` Patrick Gundlach
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=20031030234059.GA2605@cs.uu.nl \
--to=andres@cs.uu.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).