ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Matthijs Kooijman <matthijs@stdin.nl>
To: Mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: vardef with @# not working within context
Date: Mon, 21 Sep 2009 13:56:02 +0200	[thread overview]
Message-ID: <20090921115602.GT8930@katherina.student.utwente.nl> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1254 bytes --]

Hi all,

I've been fiddling around with metaobj a bit, but defining my own objects
failed. After some debugging, I've reduced this to a metapost / context MkIV
issue (so no metaobj specifics anymore).

What happens, is that vardefs that use @# as a placeholder in their name only
work when they are defined in an external .mp file. When I define them inside
context (\startMPcode or \startMPinclusions), I get funny errors (mostly
"Isolated expression", which seems to mean that the macro is not defined).

I suspect this is because the way context extracts metapost code. Is this a
fundamental problem, or could it be fixed?

The following context file will easily reproduce the problem:

\starttext
\startMPcode
    vardef foo = draw (0mm,0mm)--(10mm,10mm); enddef;
    foo;

    vardef xy@# = (@#,@#) enddef ;
    draw xy0mm -- xy10mm; 
\stopMPcode
\stoptext

Running this file gives the following (first) error:
  mplib | mp terminal: >> xy0mm
  ! Improper `addto'.

To illustrate that this is specific to the use of @#, I've included the foo
vardef which does work properly. When I move the vardef xy.. line to a
separate file, say foo.mp, and replace it with "input foo;", the errors
disappear.

Gr.

Matthijs

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

[-- Attachment #2: Type: text/plain, Size: 487 bytes --]

___________________________________________________________________________________
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://tex.aanhet.net
archive  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

             reply	other threads:[~2009-09-21 11:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-21 11:56 Matthijs Kooijman [this message]
2009-09-21 12:20 ` Aditya Mahajan
2009-09-21 13:42   ` Hans Hagen
2009-09-21 15:38     ` Aditya Mahajan
2009-09-21 17:42       ` Hans Hagen
2009-09-21 18:04         ` Aditya Mahajan
2009-09-21 18:30           ` Hans Hagen
2009-09-21 18:34             ` Aditya Mahajan
2009-09-22  8:50     ` Matthijs Kooijman
2009-09-22  9:56       ` 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=20090921115602.GT8930@katherina.student.utwente.nl \
    --to=matthijs@stdin.nl \
    --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).