From: Taco Hoekwater <taco@elvenkind.com>
Subject: Re: Metafun - Metapost capacity exceeded
Date: Wed, 05 Apr 2006 10:40:54 +0200 [thread overview]
Message-ID: <44338296.1020500@elvenkind.com> (raw)
In-Reply-To: <443376FC.2050806@wxs.nl>
Hans Hagen wrote:
> Thomas Engel wrote:
>
>>Hello Hans,
>>
>>
>>this is the message I got after running texexec pro_mcc_a3.tex.
>>As you can see I have increased the memory size for mp.
>>I have attached the two tex-files.
>>Maybe there is a mistake in the mp-code. A pdf-file will be produced,
>>but if you check the output you will see, that one cubicle is missing!
>>
>
> i run out of tex memory (8 meg) while converting the big last one
Oh yeah, it needs 14.5 MB of memory or so for the conversion.
Taco
next prev parent reply other threads:[~2006-04-05 8:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-04 17:17 Thomas Engel
2006-04-05 6:27 ` Taco Hoekwater
2006-04-05 7:51 ` Hans Hagen
2006-04-05 8:40 ` Taco Hoekwater [this message]
2006-04-05 8:12 ` Hans Hagen
-- strict thread matches above, loose matches on Subject: below --
2006-04-03 17:03 Thomas Engel
2006-04-03 22:29 ` Hans Hagen
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=44338296.1020500@elvenkind.com \
--to=taco@elvenkind.com \
--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).