ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Sanjoy Mahajan <sanjoy@mrao.cam.ac.uk>
Subject: trouble with \startMPinclusions[+]
Date: Fri, 22 Sep 2006 23:15:14 -0400	[thread overview]
Message-ID: <E1GQxz0-0007rJ-UB@approximate.corpus.cam.ac.uk> (raw)

The small test file below uses \startMPinclusions[+], but it produces
"TeX capacity exceeded" from what looks like an endless loop.  The error
msgs are below the file.  This is with context 2006.08.08 21:51, and the
live ConTeXt (2006.09.17) gives the same error.

[I was trying to test whether I could replicate my standalong metapost
programming style within metafun. I often have:

u := 1cm;
% a couple figures using this u:=1cm unit size;
beginfig(1)
fill ...
endfig;
etc.
% now a few figures with a different unit size
u := 1.5cm;
beginfig(10)
fill ...
endfig;
...

So I wanted to see whether I could use \startMPinclusions[+] midway
through the source file, in between several
\start(stop)reusableMPgraphic blocks, to change u between figures.  But
the error msgs intervened.  Anyway, here's the file.  The
currentcolor(def) in the error msgs makes me wonder whether it's related
to the new code to make there be a fixed current color before each
figure?]

=================== cut here =================
\starttext

\startreusableMPgraphic{a}
fill fullcircle scaled 1cm;
\stopreusableMPgraphic

\placefigure[force,none]{}{\reuseMPgraphic{a}}

hello

% instead, just \startMPinclusions works (i.e. without the [+])
\startMPinclusions[+]
\stopMPinclusions

\startreusableMPgraphic{b}
fill fullcircle scaled 1cm;
\stopreusableMPgraphic

\placefigure[force,none]{}{\reuseMPgraphic{b}}

hello2

\stoptext
=================== cut here =================

And a piece of the log:

floatblocks     : order disturbed
floatblocks     : 1 placed
color           : currentcolor (def) is not defined 
! TeX capacity exceeded, sorry [input stack size=1500].
\theMPinclusions ->\theMPinclusions 
                                    \writeMPgraphic {
}
\theMPinclusions ->\theMPinclusions 
                                    \writeMPgraphic {
}
\theMPinclusions ->\theMPinclusions 
                                    \writeMPgraphic {
}
\theMPinclusions ->\theMPinclusions 
                                    \writeMPgraphic {
}
\theMPinclusions ->\theMPinclusions 
                                    \writeMPgraphic {
}
\theMPinclusions ->\theMPinclusions 
                                    \writeMPgraphic {
}
...
l.19 ...cefigure[force,none]{}{\reuseMPgraphic{b}}
                                                  
If you really absolutely need more capacity,
you can ask a wizard to enlarge me.

             reply	other threads:[~2006-09-23  3:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-23  3:15 Sanjoy Mahajan [this message]
2006-09-24 19:30 ` Hans Hagen

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=E1GQxz0-0007rJ-UB@approximate.corpus.cam.ac.uk \
    --to=sanjoy@mrao.cam.ac.uk \
    --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).