ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: vardef with @# not working within context
Date: Mon, 21 Sep 2009 15:42:45 +0200	[thread overview]
Message-ID: <4AB782D5.6090609@wxs.nl> (raw)
In-Reply-To: <alpine.LNX.2.00.0909210813230.16670@ybpnyubfg.ybpnyqbznva>

Aditya Mahajan wrote:
> On Mon, 21 Sep 2009, Matthijs Kooijman wrote:
> 
>> 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?
> 
> You need to escape # inside any \startMPwhatever...\stopMPwhatever. This 
> has to do with the fact that TeX processes the contents before they are 
> passed to metapost, and TeX does not like isolated #. Try replacing
> # with \# or \string#

it's more that tex likes to duplicate the # internally

> Hans, does it make sense to parse all MP environments (ironically except 
> \startMPenvironment, but that is almost redundant in MKIV) with a 
> separate catcode regime where # has catcode other. After all, it is 
> highly unlikely that anyone will define a TeX maco inside \startMPcode 
> or \startMPinclusions.

how about adding

let @## = @# ;

to mp-tool.mp (you need to remake the context format in mkiv or the 
metafun format in mkii)

seems to work

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
      tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
                                              | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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 13:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-21 11:56 Matthijs Kooijman
2009-09-21 12:20 ` Aditya Mahajan
2009-09-21 13:42   ` Hans Hagen [this message]
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=4AB782D5.6090609@wxs.nl \
    --to=pragma@wxs.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).