From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
luigi scarso <luigi.scarso@gmail.com>
Subject: Re: Can't use MetaFun with mplib anymore
Date: Thu, 14 Mar 2019 10:52:03 +0100 [thread overview]
Message-ID: <315c66c6-0b5d-5444-06a4-48af492a09b8@xs4all.nl> (raw)
In-Reply-To: <CAG5iGsA_eF_AQN-n5P-0ReRt6i_JYvxDszVgXR5xOVy9zgVU3w@mail.gmail.com>
On 3/14/2019 8:51 AM, luigi scarso wrote:
>
>
> On Thu, Mar 14, 2019 at 5:56 AM Henri Menke <henrimenke@gmail.com
> <mailto:henrimenke@gmail.com>> wrote:
>
>
> Dear list,
>
> Something has changed in MetaFun and it can no longer be used in
> plain LuaTeX,
> with neither of
>
> luatex test.tex
> mtxrun --script plain test.tex
>
> This is the error:
>
> >> LUATEXFUNCTIONALITY
> >> "mp.print(LUATEXFUNCTIONALITY)"
> ! Equation cannot be performed (numeric=string).
>
> MWE is below, as always.
>
> Cheers, Henri
>
> ---
>
> \directlua{
> local mpkpse = kpse.new(arg[0], "mpost")
>
> local function finder(name, mode, ftype)
> if mode == "w" then
> return name
> else
> return mpkpse:find_file(name,ftype)
> end
> end
>
> local mpx = mplib.new {
> find_file = finder
> }
> local ret = mpx:execute[[
> boolean mplib ; mplib := true ;
> input metafun.mp <http://metafun.mp> ;
> ]]
>
> print(ret.log)
> }
> \bye
>
>
> in mp-mlib.mpiv it seems that we should have
> string LUATEXFUNCTIONALITY ; LUATEXFUNCTIONALITY :=
> runscript("mp.print(LUATEXFUNCTIONALITY)") ;
> instead of
> numeric LUATEXFUNCTIONALITY ; LUATEXFUNCTIONALITY :=
> runscript("mp.print(LUATEXFUNCTIONALITY)") ;
> Now I have
> tex/texmf-context/metapost/context/base/mpiv$ grep -r LUATEXFUNCTIONALITY
> mp-mlib.mpiv:%numeric LUATEXFUNCTIONALITY ; LUATEXFUNCTIONALITY :=
> runscript("mp.print(LUATEXFUNCTIONALITY)") ;
> mp-mlib.mpiv:string LUATEXFUNCTIONALITY ; LUATEXFUNCTIONALITY :=
> runscript("mp.print(LUATEXFUNCTIONALITY)") ;
>
> and your example looks ok.
as currently the variable is isn't used we can also comment it
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | 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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2019-03-14 9:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-14 4:56 Henri Menke
2019-03-14 7:49 ` Hans Hagen
2019-03-14 9:00 ` Henri Menke
2019-03-14 9:55 ` Hans Hagen
2019-03-14 7:51 ` luigi scarso
2019-03-14 9:52 ` Hans Hagen [this message]
2019-03-14 10:00 ` luigi scarso
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=315c66c6-0b5d-5444-06a4-48af492a09b8@xs4all.nl \
--to=j.hagen@xs4all.nl \
--cc=luigi.scarso@gmail.com \
--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).