ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Nikolai Weibull <context-list@pcppopper.org>
Subject: Re: Re: btex ... etex in .mp
Date: Fri, 27 Aug 2004 18:48:19 +0200	[thread overview]
Message-ID: <20040827164819.GC2604@puritan.pcp.ath.cx> (raw)
In-Reply-To: <20040827153658.6d1fce52@glenlivet.elvenkind.com>

* Taco Hoekwater <taco@elvenkind.com> [Aug 27, 2004 15:40]:
> Don't know. Metapost seems to be complaining about something
> that is part of extra_endfig, but neither trees.mp nor mp-text.mp
> do anything with that, so it may be completely unrelated ?

Actually, it was boxes.mp's fault.  I was "input"ing boxes from two
places, and it was not multiple-inclusion-protected, so line 122 of
metapost/base/boxes.mp was being executed twice, adding
clearboxesclearboxes instead of only clearboxes.  The line is buggy
though, as it should read 

	extra_endfig := extra_endfig & "clearboxes;";

My error report should have been

	>> clearboxesclearboxes
	! Isolated expression.
	:
	:

which I didn't realize until now.

Who should one contact about fixing that?

Anyway, the real problem was that texexec doesn't run with --mptex when
it actually needs to.  If there are textext() stuff or other generated
btex ... etex stuff, but no btex ... etex in the picture itself, the
extra run for the labels is not performed.  This needs fixing and should
probably not be impossible to fix, but I guess it's yet another one of
my "pushing the limits of ConTeXt/MetaPost"-problems.  I cannot quite
figure out how texexec determines whether to run an extra run of the
files, but it won't.  I can provide an example of this off-list (as
there are quite a few files necessary for even a small example) if
anyone is interested.

The temporary solution is thus to include at least one btex ... etex
sequence in the graphic:
	label(textext(""), origin);

which of course is crap, but it's the best I could come up with.
	nikolai

--
::: name: Nikolai Weibull    :: aliases: pcp / lone-star / aka :::
::: born: Chicago, IL USA    :: loc atm: Gothenburg, Sweden    :::
::: page: www.pcppopper.org  :: fun atm: gf,lps,ruby,lisp,war3 :::
main(){printf(&linux["\021%six\012\0"],(linux)["have"]+"fun"-97);}

  reply	other threads:[~2004-08-27 16:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-26 20:07 Nikolai Weibull
2004-08-27  7:32 ` Taco Hoekwater
2004-08-27 10:32   ` Nikolai Weibull
2004-08-27 13:36     ` Taco Hoekwater
2004-08-27 16:48       ` Nikolai Weibull [this message]
2004-08-27 18:05         ` Taco Hoekwater

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=20040827164819.GC2604@puritan.pcp.ath.cx \
    --to=context-list@pcppopper.org \
    --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).