ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Thomas A. Schmitz via ntg-context" <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: "Thomas A. Schmitz" <thomas.schmitz@uni-bonn.de>
Subject: Re: Compiling a large metapost document
Date: Wed, 1 Jun 2022 22:25:01 +0200	[thread overview]
Message-ID: <c9feb9f2-618d-0b19-e7eb-00d44d057f95@uni-bonn.de> (raw)
In-Reply-To: <CAGraPNe-WhLK3jo-oBdDk2NsP-Tzz2VtBidwX1vSHwd4Ja-DaA@mail.gmail.com>


On 6/1/22 22:15, Stefan Nedeljkovic via ntg-context wrote:
> The problem *is* the file size. There is not a minimal example, 
> because everything works when there is less drawdot commands. There is 
> 125000+ drawdot commands in the file.
> The run ends with the message:
> If you really absolutely need more capacity, you can ask a wizard to 
> enlarge me.
> mtx-context     | fatal error: return code: 1
> 
> I really don't know how to "enlarge" LMTX, so my question is not about 
> debugging the file, but rather compiling it. The current version of the 
> file should produce no syntax etc. errors. I accidentally uploaded the 
> wrong file twice, now it should be fixed, and you should get the same 
> message in the console as me.

Excuse me: you want me to download a huge file, from an unknown author, 
that may or may not contain all sorts of things. You want me to compile 
this file on my computer. To obtain an error message that you could have 
mentioned in your first message. Why? Why don't you search the list 
archives with the key words "enlarge capacity"? I still don't understand 
what you expect us to do.

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
___________________________________________________________________________________

  parent reply	other threads:[~2022-06-01 20:25 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 [this message]
2022-06-01 21:30             ` Stefan Nedeljkovic via ntg-context
2022-06-01 22:26               ` Bruce Horrocks via ntg-context
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=c9feb9f2-618d-0b19-e7eb-00d44d057f95@uni-bonn.de \
    --to=ntg-context@ntg.nl \
    --cc=thomas.schmitz@uni-bonn.de \
    /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).