From: Hans Hagen <pragma@wxs.nl>
Cc: ntg-context@ntg.nl
Subject: Re: metafun tryout
Date: Fri, 28 Jun 2002 09:11:50 +0200 [thread overview]
Message-ID: <5.1.0.14.1.20020628090627.031be3e0@server-1> (raw)
In-Reply-To: <20020627142428.A13408@cs.cmu.edu>
At 02:24 PM 6/27/2002 -0400, David Petrou wrote:
>but when i run the texexec command what you suggested (texexec --make
>--alone en metafun), i get:
>
>----------------------------------------------------------------------
>! TeX capacity exceeded, sorry [pool size=221441].
>\docopyvalue ... \@EA \@EA \csname #1#3\endcsname
> \@EA {\csname
> #2#3\endcsna...
>
>\next1 #1,->\docopyparameter {#1}
> \doprocesscommaitem
><argument> ...ergrondraster ,\c!achtergrondkleur ,
> \c!uitlijnen ,\c!onder
> ,\c...
>
>\doprocesscommalist ...aitem \gobbleoneargument #1
> ,]\relax \global
> \advance ...
>
>\copylocalframed ...c!boven ,\c!strut ,\c!plaats ]
> \copyparameters
> [#1\c!acht...
>
>\dododefinieerplaatsblok ...localframed [\??fl #1]
> \stelplaatsblokin [#1]
> [\c...
>...
>l.1826
>----------------------------------------------------------------------
This is weird, and it looks like something is wrong with your system setup;
>so what i did instead was first run `texexec --make en nl' like the
>instructions suggest, and then run `texexec --make --alone metafun'.
ok (btw, a next tetex can generate metafun formats as well but i still have
to patch texexec for that)
you can try
texconfig -e
or so, and uncomment the metafun line of it's there
>after moving the metafun.mem file, things work fine, except it takes
>REALLY long to process a simple one-line file.
ok, then indeed something's wrong with your system, did you run
mktexlsr
(generate file database)
>the docs say that things can take a long time if i made a mistake
>doing installation. but i really tried hard to follow the
>instructions to the letter. i'm appending below what a run looks
>like. (i actually ran it twice in case there were caching effects.)
when the file database is generated (ls-r files) tex programs become much
faster in file lookup (now the slow down comes from locating font files and so)
>also we're still left with the mystery of why i had to run `texexec
>--make --alone metafun' from the directory that holds metafun.mp.
has to do with the fact that until recently, tex installations did not
generate metapost formats at the user's site
>another (smallish) mystery: the docs say to modify a file called
>`cont-sys.tex' to set certain defaults, etc. but this file doesn't
>exist. there are other files with different extensions. perhaps a
>doc typo?
search for cont-sys.rme
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
-------------------------------------------------------------------------
information: http://www.pragma-ade.com/roadmap.pdf
documentation: http://www.pragma-ade.com/showcase.pdf
-------------------------------------------------------------------------
next prev parent reply other threads:[~2002-06-28 7:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-24 11:57 Kris Hermans
2002-06-24 16:12 ` Hans Hagen
2002-06-24 18:07 ` Kris Hermans
2002-06-24 19:36 ` David Petrou
2002-06-24 21:16 ` Mr. Lei Wang
2002-06-25 6:15 ` Kris Hermans
2002-06-25 15:40 ` Hans Hagen
2002-06-25 15:50 ` Hans Hagen
2002-06-26 21:04 ` David Petrou
2002-06-27 16:48 ` Hans Hagen
2002-06-27 18:24 ` David Petrou
2002-06-28 7:11 ` Hans Hagen [this message]
2002-07-01 3:22 ` David Petrou
2002-07-01 12:21 ` Hans Hagen
2002-07-08 18:39 ` David Petrou
2002-07-08 20:26 ` Henning Hraban Ramm
2002-07-08 21:16 ` David Petrou
2002-07-09 8:03 ` Siep
2002-07-10 21:48 ` David Petrou
2002-07-10 21:46 ` David Petrou
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.20020628090627.031be3e0@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).