From: "Thomas A. Schmitz" <thomas.schmitz@uni-bonn.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
Hans Hagen <j.hagen@xs4all.nl>
Subject: Re: TeX capacity exceeded
Date: Wed, 19 May 2021 18:49:49 +0200 [thread overview]
Message-ID: <6a4939bd-50ca-ef87-ca2a-1b517c4ff2e0@uni-bonn.de> (raw)
In-Reply-To: <2b0fcbc0-a854-5b88-ff0b-d48fb7679d9e@xs4all.nl>
On 19.05.21 18:34, Hans Hagen wrote:
>>
> Can you check the latest upload? You should be able to go way higher.
Yes, with 2021.05.19 18:22, the file compiles again in lmtx! I'm also
trying your suggestions for improving the Lua code and rethinking my
tables for analyzing the vocabulary. Thank you for the quick fix! And I
hope there won't be any problem for other users - I'm aware that memory
on computers can differ vastly. I sometimes run ConTeXt on my raspberry
pi 3, which has just 1 G of RAM, whereas my newish iMac at home has 40
G. So it's difficult to find the sweet spot that will satisfy everybody...
All best
Thomas
___________________________________________________________________________________
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:[~2021-05-19 16:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-17 21:43 Thomas A. Schmitz
2021-05-18 13:35 ` Hans Hagen
2021-05-18 16:44 ` Hans Hagen
2021-05-19 16:34 ` Hans Hagen
2021-05-19 16:49 ` Thomas A. Schmitz [this message]
2021-05-19 17:22 ` Hans Hagen
-- strict thread matches above, loose matches on Subject: below --
2022-03-17 22:43 Tex " jbf via ntg-context
2008-06-03 7:10 TeX " M.guravage
2008-06-03 9:11 ` Taco Hoekwater
2004-07-10 17:01 jimarin
2004-07-12 7:17 ` Willi Egger
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=6a4939bd-50ca-ef87-ca2a-1b517c4ff2e0@uni-bonn.de \
--to=thomas.schmitz@uni-bonn.de \
--cc=j.hagen@xs4all.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).