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 20:34:05 +0200 [thread overview]
Message-ID: <f0b9787c-428b-836f-605b-2d10eeff05b3@uni-bonn.de> (raw)
In-Reply-To: <CAGraPNfFUQb+UV25OnyBytuu6n5uQ+9aRyJgid_OWn5FKk6xWw@mail.gmail.com>
On 6/1/22 19:35, Stefan Nedeljkovic via ntg-context wrote:
> Sorry, i just updated the file, should now compile, but fail due to
> resources. Are the configuration options to context that would enable
> this file to be compiled?
The question still stands: what do you expect us to do? Hunt for a
problem through a huge file? What have you done to identify this
problem? Is there a minimal example?
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:[~2022-06-01 18:34 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 [this message]
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
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=f0b9787c-428b-836f-605b-2d10eeff05b3@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).