From: Henri Menke <henrimenke@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Can't use MetaFun with mplib anymore
Date: Thu, 14 Mar 2019 22:00:04 +1300 [thread overview]
Message-ID: <bddc6034-285e-6725-b3b2-1e9a30558728@gmail.com> (raw)
In-Reply-To: <67c452df-4efb-ad7d-db6a-b9ab78eab126@xs4all.nl>
On 3/14/19 8:49 PM, Hans Hagen wrote:
> On 3/14/2019 5:56 AM, Henri Menke 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).
>
> hm, that can be
>
> mp.print(LUATEXFUNCTIONALITY or 0)
>
> but ... i'm surprised you can use metafun in plain at all ... i never
> test that and to be honest am not too motivated to support mpiv code in
> generic either .. better use
Until TeX Live 2018, MetaFun worked in plain (at least the subset I'm
using). It would be a shame if the support would end. I also think
that there are quite a number of users. The number of posts on TeX
Stack Exchange mentioning luamplib with metafun is not negligible.
https://tex.stackexchange.com/search?q=mplibsetformat
I (and probably a lot of other people) would really appreciate if you
could apply Luigi's fix, so we can continue do enjoy MetaFun, even
outside ConTeXt.
Cheers, Henri
>
> \startMPpage
> \stopMPpage
>
> with context and then include the pdf
>
> Hans
>
>> 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 ;
>> ]]
>>
>> print(ret.log)
>> }
>> \bye
>>
>> ___________________________________________________________________________________
>>
>> 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
>> ___________________________________________________________________________________
>>
>>
>
>
___________________________________________________________________________________
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:00 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 [this message]
2019-03-14 9:55 ` Hans Hagen
2019-03-14 7:51 ` luigi scarso
2019-03-14 9:52 ` Hans Hagen
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=bddc6034-285e-6725-b3b2-1e9a30558728@gmail.com \
--to=henrimenke@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).