ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Denis B. Roegel" <Denis.Roegel@loria.fr>
Cc: roegel@lorraine.loria.fr (Denis B. Roegel)
Subject: problem with vardefs
Date: Thu, 7 Dec 2000 15:41:11 +0100 (MET)	[thread overview]
Message-ID: <200012071441.PAA07685@bar.loria.fr> (raw)

How am I supposed to write a vardef with `@#' in context?
For instance, the following

\startuseMPgraphic{annot}
  vardef annot@#(suffix n)% noeud
    (expr l)% étiquette
    (expr a)% angle
    =
    label@#(l,n.c+(cosd a,sind a)*labdist);
  enddef;
\stopuseMPgraphic

produces the error:

! Illegal parameter number in definition of \MP:annot.
<to be read again> 
                   (
<argument>  vardef annot@##(
                            suffix n)(expr l)(expr a)= label@##(l,n.c+(cosd ...

\dostartuseMPgraphic ...leuseMPgraphic {#1}{#2}{#3
                                                  }}
l.54 \stopuseMPgraphic

Thanks,

Denis


             reply	other threads:[~2000-12-07 14:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-07 14:41 Denis B. Roegel [this message]
2000-12-07 15:12 ` 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=200012071441.PAA07685@bar.loria.fr \
    --to=denis.roegel@loria.fr \
    --cc=roegel@lorraine.loria.fr \
    /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).