ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Peter Rolf <indiego@gmx.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: passvariable(); path problem
Date: Fri, 04 Oct 2013 16:47:34 +0200	[thread overview]
Message-ID: <524ED506.9070906@gmx.net> (raw)
In-Reply-To: <524ECD78.2070001@wxs.nl>

Am 04.10.2013 16:15, schrieb Hans Hagen:
> On 10/4/2013 2:52 PM, Peter Rolf wrote:
>> Hi,
>>
>> I played around with the new passvariable() option and ran into errors
>> when passing a path. Used the latest beta (01.10.2013). Can someone
>> confirm this?
> 
> in mp-mlib.mpiv:
> 
> vardef mfun_path_to_string(expr p) =
>     mfun_point_to_string(p,1) for i=2 upto length(p) : & " " &
> mfun_point_to_string(p,i) endfor
> enddef ;
> 
> vardef mfun_boolean_to_string(expr b) =
>     if b : "true" else : "false" fi
> enddef ;
> 
> (i forgot to rename the argument when outlining the code)
> 
> fwiw: in your case you still get an (empty) graphic, use
> \startMPcalculation ... when you don't want that
>

Many thanks! Good to know, but in this case I just need the path.


> Hans
> 
> -----------------------------------------------------------------
>                                           Hans Hagen | PRAGMA ADE
>               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
>     tel: 038 477 53 69 | voip: 087 875 68 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  : http://foundry.supelec.fr/projects/contextrev/
> wiki     : http://contextgarden.net
> ___________________________________________________________________________________
> 
> 

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


  reply	other threads:[~2013-10-04 14:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-04 12:52 Peter Rolf
2013-10-04 14:15 ` Hans Hagen
2013-10-04 14:47   ` Peter Rolf [this message]
2013-10-04 14:59     ` Peter Rolf
2013-10-05 15:52   ` Peter Rolf
2013-10-05 22:37     ` Hans Hagen
2013-10-06 13:05       ` Peter Rolf
2013-10-06 15:06         ` Hans Hagen
2013-10-07  8:48           ` Peter Rolf
2013-10-07  9:47             ` luigi scarso
2013-10-07 10:03               ` Hans Hagen
2013-10-07 11:02               ` Peter Rolf

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=524ED506.9070906@gmx.net \
    --to=indiego@gmx.net \
    --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).