From: Hans Hagen <pragma@wxs.nl>
Cc: ntg-context@ntg.nl
Subject: Re[2]: The usual install problem.
Date: Tue, 26 Feb 2002 12:02:30 +0100 [thread overview]
Message-ID: <5.1.0.14.1.20020226120126.038a85a8@server-1> (raw)
In-Reply-To: <767164424.20020225223650@bigfoot.com>
At 10:36 PM 2/25/2002 +0100, Giuseppe Bilotta wrote:
>Monday, February 25, 2002 Hans Hagen wrote:
>
>HH> texexec --make --alone
>
>By the way, Hans, when I
>
>texexec --make metafun
>
>the metafun.mem file is put together with the (pdfe)TeX formats,
>and not together with the other Metapost .mem files. (Using MiKTeX
>2.1). Shouldn't this be fixed somehow?
what does --alone do?
btw, you can set the assiciated env var ($TEXFORMATS or alike) to indicate
the place or edit texexec.ini
Hans
-------------------------------------------------------------------------
Hans Hagen | PRAGMA ADE | pragma@wxs.nl
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
fall-back web server:
www.pragma-pod.nl
-------------------------------------------------------------------------
next prev parent reply other threads:[~2002-02-26 11:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-23 0:39 John Culleton
2002-02-21 8:36 ` David Antos
2002-02-21 9:15 ` Taco Hoekwater
2002-02-21 15:20 ` W. Egger
2002-02-25 13:51 ` Hans Hagen
2002-02-25 19:42 ` Frans Goddijn
2002-02-25 20:02 ` Frans Goddijn
2002-02-25 21:36 ` Re[2]: " Giuseppe Bilotta
2002-02-26 11:02 ` Hans Hagen [this message]
2002-02-26 21:05 ` Re[3]: " Giuseppe Bilotta
2002-02-27 18:44 ` Hans Hagen
2002-02-28 10:53 ` Re[4]: " Giuseppe Bilotta
2002-02-28 11:55 ` Hans Hagen
2002-03-01 13:18 ` Re[5]: " Giuseppe Bilotta
2002-03-02 13:41 ` Giuseppe Bilotta
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=5.1.0.14.1.20020226120126.038a85a8@server-1 \
--to=pragma@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).