From: Bruce Horrocks via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Bruce Horrocks <ntg@scorecrow.com>
Subject: Re: Compiling a large metapost document
Date: Wed, 1 Jun 2022 23:26:53 +0100 [thread overview]
Message-ID: <FC56FF2D-28B8-4E39-9A2C-DB32FFA8DE4C@scorecrow.com> (raw)
In-Reply-To: <CAGraPNfwty+FaNYi8Rc9iFv-3DP31a+R8-STxeusE3LWYu_S0Q@mail.gmail.com>
> On 1 Jun 2022, at 22:30, Stefan Nedeljkovic via ntg-context <ntg-context@ntg.nl> wrote:
>
> Dear Thomas,
>
> I'm sorry for all the shortcomings of my question. I'll try to be more concrete. If you won't download my file, could you at least give me a hint on how to configure LMTX?
>
> I Tried editing the file context/tex/texmf/web2c/texmfcnf.lua, and running context --generate, context --make, but the error persists. I'm new to context and I don't know how to configure this file. Running --usage reveals in the log that the category "token" is exceeded. I tried the aforementioned editing of the conf file, but the log stays the same.
For the benefit of others, the error is:
tex memory > bumping category 'token' failed, details: all=80000000 | ini=495183 | max=10000000 | mem=10000000 | min=1000000 | ptr=10002079 | set=10000000 | stp=250000 | top=10000000
I can't see where max token memory is defined to try and increase it. The only reference seems to be in ~/tex/texmf-context/tex/context/base/mkxl/luat-cod.lmt but uncommenting and increasing had no obvious effect.
—
Bruce Horrocks
Hampshire, UK
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2022-06-01 22:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-01 14:48 Stefan Nedeljkovic via ntg-context
2022-06-01 16:43 ` Stefan Nedeljkovic via ntg-context
2022-06-01 17:24 ` Bruce Horrocks via ntg-context
2022-06-01 17:35 ` Stefan Nedeljkovic via ntg-context
2022-06-01 18:34 ` Thomas A. Schmitz via ntg-context
2022-06-01 20:15 ` Stefan Nedeljkovic via ntg-context
2022-06-01 20:16 ` Stefan Nedeljkovic via ntg-context
2022-06-01 20:25 ` Thomas A. Schmitz via ntg-context
2022-06-01 21:30 ` Stefan Nedeljkovic via ntg-context
2022-06-01 22:26 ` Bruce Horrocks via ntg-context [this message]
2022-06-02 7:18 ` Thomas A. Schmitz via ntg-context
2022-06-02 8:51 ` Stefan Nedeljkovic via ntg-context
2022-06-02 10:15 ` Hans Hagen via ntg-context
2022-06-02 10:36 ` Stefan Nedeljkovic via ntg-context
2022-06-01 23:45 ` Max Chernoff via ntg-context
2022-06-02 2:00 ` Stefan Nedeljkovic via ntg-context
2022-06-02 2:22 ` Max Chernoff via ntg-context
2022-06-02 2:41 ` Stefan Nedeljkovic via ntg-context
2022-06-02 3:21 ` Stefan Nedeljkovic via ntg-context
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=FC56FF2D-28B8-4E39-9A2C-DB32FFA8DE4C@scorecrow.com \
--to=ntg-context@ntg.nl \
--cc=ntg@scorecrow.com \
/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).