From: "Adam Lindsay" <atl@comp.lancs.ac.uk>
Subject: m-graph and the definition of \@@expanded
Date: Sun, 9 Feb 2003 17:19:23 +0000 [thread overview]
Message-ID: <20030209171923.7635@mail.comp.lancs.ac.uk> (raw)
Hi ConTeXters...
I was wondering if the metapost/fun module "m-graph" was still working
for everyone. I worked with it a lot last October/November, but haven't
had the need to revisit it recently.
For those interested, does:
texexec --pdf --mode=demo m-graph.tex
....work correctly?
(m-graph is from tex/context/base/m-graph.tex, and the data files it
expects are in doc/metapost/base/*.d)
Am I the only one having problems, or were the syst-* macros changed
after 31 October 2002 so as to conflict with something deep inside
graph.mp? I get the same problem with both the latest ConTeXt as well as
one from ~5 December.
It *might* something else I'm trying to debug, but I get the following
when trying to \usemodule[graph]:
! Illegal parameter number in definition of \@@expanded.
<to be read again>
(
<argument> ...fi ; input graph ; vardef Gsetr_@##(
suffix $)(expr l, h) =
Gcl...
\expanded ...\long \xdef \@@expanded {\noexpand #1
}\@@expanded
\theMPinclusions ...A {\the \MPinitializations ;}}
\writeMPgraphic {}
\startwritingMPgraphic ...untime}\theMPinclusions
\else
\openMPgraphicfile {...
\startMPgraphic ...hic {#1}\startwritingMPgraphic
\writeMPgraphic
{#1}\stopw...
...
l.9 \stopMPpage
Sorry to bother the list with something so specialist,
adam
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Adam Lindsay +44(0)1524 594 537
atl@comp.lancs.ac.uk
http://www.comp.lancs.ac.uk/computing/users/atl/
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
next reply other threads:[~2003-02-09 17:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-09 17:19 Adam Lindsay [this message]
2003-02-09 19:13 ` Hans Hagen
2003-02-09 23:54 ` Adam Lindsay
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=20030209171923.7635@mail.comp.lancs.ac.uk \
--to=atl@comp.lancs.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).