From: "Eckhart Guthöhrlein" <eckhart.guthoehrlein@cebitec.uni-bielefeld.de>
Subject: Re: problem getting started with metafun -- runaway defininition...
Date: Thu, 24 Apr 2003 09:25:31 +0200 [thread overview]
Message-ID: <20030424072531.GA11745@cebitec.uni-bielefeld.de> (raw)
In-Reply-To: <5.2.0.9.0.20030423231428.00af3650@mail.tinorb.com>
On Wed, Apr 23, 2003 at 11:23:37PM -0700, Mark A. Lilly wrote:
> i'm trying to get started with metafun, but when i run the command to
> create my metafun.mem
> texexec --make --alone en metafun
> (from the same directory as metafun.mp resides) i get the following error:
You can run this in any directory, more important: put the
resulting metafun.mem in a place where files of that type will
be found. In your case, this should be $TEXMF/web2c.
Hope that helps.
--
Eckhart
next prev parent reply other threads:[~2003-04-24 7:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-02 6:04 hyphenation Zeljko Vrba
2003-04-08 11:26 ` hyphenation Hans Hagen
2003-04-24 6:23 ` problem getting started with metafun -- runaway defininition Mark A. Lilly
2003-04-24 7:25 ` Eckhart Guthöhrlein [this message]
2003-04-24 16:19 ` Mark A. Lilly
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=20030424072531.GA11745@cebitec.uni-bielefeld.de \
--to=eckhart.guthoehrlein@cebitec.uni-bielefeld.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).