From: Hans Hagen <pragma@wxs.nl>
To: "Keith J. Schultz" <keithjschultz@web.de>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>, dev-luatex@ntg.nl
Subject: Re: [Dev-luatex] new/missing feature in luamplib
Date: Tue, 07 Aug 2012 10:12:44 +0200 [thread overview]
Message-ID: <5020CDFC.50208@wxs.nl> (raw)
In-Reply-To: <30B8277D-B6D7-4920-A050-F51B9DA459E6@web.de>
On 7-8-2012 09:29, Keith J. Schultz wrote:
> Hi Manuel, Everybody,
>
> I am just getting into LuaLaTeX.
>
> I needed to do some work with MetaPost.
>
> While working I came across a kudo. That is once inside the mblibcode
> environment one can not call Lua. THIS I consider a missing feature and
> a VERY important one.
Some (simple) support for lua calls is on the (long term) agenda but not
before the current mplib extensions project is done (i.e. the decimal
calculation plugins).
Calling lua in itself is not so much an issue; after all one can just do
a \directlua inside a blob of mp passed to mplib (I do that all the
time). For an lua 'primitive' in mplib (which then probably would just
be called just 'lua') we first need to figure out:
1 - how to access mp internals (and that relates to the mentioned
decimal extensions, as we might need to get and set)
2 - if and how we can share the state with the (main) tex lua instance
3 - how we want to print back to mp (like tex.[s]print)
It's one of those feature we have discussed (maybe too) long ago, but
because it has to be more than just (3) it never ended up first on the
todo list (first finishing the main lib).
The problem with these things is that it has to be mostly 'right from
the start' in order not to conflict too much with long term usage).
Anyhow, if you play with such things, best have something
lua "mp.print(123)"
Given mp's somewhat different parsing and expansion compared to tex
there are also some conceptual issues involved. It also relates to input
buffers (and file reading) and io is somewhat messy in mp and on the
agenda for cleaning up.
(Luigi Scarso has done this with metafont, so that might be a starting
point for experimenting.)
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
___________________________________________________________________________________
next parent reply other threads:[~2012-08-07 8:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <30B8277D-B6D7-4920-A050-F51B9DA459E6@web.de>
2012-08-07 8:12 ` Hans Hagen [this message]
2012-08-07 8:33 ` Taco Hoekwater
[not found] ` <86A1AFB8-7483-4B6A-9A52-758DECEF6B96-KIERECuABvX/D1n+0JDH9g@public.gmane.org>
2012-08-07 9:00 ` 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=5020CDFC.50208@wxs.nl \
--to=pragma@wxs.nl \
--cc=dev-luatex@ntg.nl \
--cc=keithjschultz@web.de \
--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).