From: Patrick Gundlach <pg@levana.de>
Subject: Re: Integrating Metapost
Date: Fri, 31 Oct 2003 11:55:39 +0100 [thread overview]
Message-ID: <m27k2l4qxg.fsf@levana.de> (raw)
In-Reply-To: <20031030234059.GA2605@cs.uu.nl> (Andres Loeh's message of "Fri, 31 Oct 2003 00:40:59 +0100")
Andres Loeh <andres@cs.uu.nl> writes:
Hello Andres,
> 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?
That would be good. Just as an example, one can do this in LaTeX:
\NeedsTeXFormat{LaTeX2e}[1995/12/01]
(there are a few related commands)
so you can make sure to have LaTeX2e newer than the given date.
But I don't know how to get the metafun format number. One can't pass
mpost variables back to TeX?
Patrick
--
You are your own rainbow!
prev parent reply other threads:[~2003-10-31 10:55 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
2003-10-31 10:55 ` Patrick Gundlach [this message]
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=m27k2l4qxg.fsf@levana.de \
--to=pg@levana.de \
--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).