From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: ntg-context@ntg.nl
Cc: Hans Hagen <j.hagen@xs4all.nl>
Subject: Re: Compiling a large metapost document
Date: Thu, 2 Jun 2022 12:15:34 +0200 [thread overview]
Message-ID: <c2a1dade-7de0-dac8-0c4a-f13843a59eb2@xs4all.nl> (raw)
In-Reply-To: <f0b9787c-428b-836f-605b-2d10eeff05b3@uni-bonn.de>
On 6/1/2022 8:34 PM, Thomas A. Schmitz via ntg-context wrote:
>
>
> 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?
due to a mail server crash i lost todays and last nights mail sop here s
a partial reply
(Just put that large mp blob in a file and call that one instead of
passing through tex's tokenizer:
\startMPpage
input test.mp ;
\stopMPpage
then in order to save runtime do
draw image (
draw (220.852, 127.175) ;
draw (226.248, 128.606) ;
draw (221.840, 129.541) ;
draw (280.733, 100.927) ;
draw (276.968, 83.053) ;
draw (251.644, 83.879) ;
) withpen pencircle scaled 0.16875 withcolor (0.976, 0.702, 0.204) ;
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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-02 10:15 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
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 [this message]
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=c2a1dade-7de0-dac8-0c4a-f13843a59eb2@xs4all.nl \
--to=ntg-context@ntg.nl \
--cc=j.hagen@xs4all.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).