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: [OS X TeX] Default rule thickness
Date: Thu, 14 Aug 2008 12:50:50 +0200	[thread overview]
Message-ID: <48A40E0A.3000304@wxs.nl> (raw)
In-Reply-To: <38CF58CB-A115-45C8-995D-6059CC1E9D56@mpq.mpg.de>

Oliver Buerschaper wrote:
>>> What's the correct way of piping this to MetaFun? Putting
>>>
>>> DefaultRuleThickness := \defaultrulethickness;
>>>
>>> into each "\startuseMPgraphic{}" block works, but how can I define
>>> this globally? Moving it into "\startMPinclusions" creates a scope
>>> problem … see also the other thread about BodyFontSize etc.
>> \def\defaultrulethickness{\the\fontdimen8\textfont\plusthree}
>>
>> \startMPinitializations
>>   DefaultRuleThickness := \defaultrulethickness;
>> \stopMPinitializations
> 
> This works like a charm!
> 
> Now I'm a bit confused though as to which definitions need this  
> "MPinitializations" block and which ones can/should go to  
> "MPinclusions". For example, a subsequent

inclusions happen once, initializations for each graphic

-----------------------------------------------------------------
                                           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:[~2008-08-14 10:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <689AE27A-F050-46B4-95E0-5A8CAF3E66A8@mpq.mpg.de>
     [not found] ` <BE3EF24C-3A0D-4F83-BCEA-AA988AC3942B@me.com>
2008-08-06 10:59   ` Wolfgang Schuster
2008-08-08  8:12     ` Oliver Buerschaper
2008-08-09  8:12       ` Taco Hoekwater
2008-08-13 16:35         ` Oliver Buerschaper
2008-08-13 17:06           ` Taco Hoekwater
2008-08-13 18:57             ` Oliver Buerschaper
2008-08-13 21:24               ` Hans Hagen
2008-08-14  8:51                 ` Oliver Buerschaper
2008-08-14 10:50                   ` Hans Hagen [this message]

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=48A40E0A.3000304@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).