ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma-42P/b7yZOt0@public.gmane.org>
To: Taco Hoekwater <taco-KIERECuABvX/D1n+0JDH9g@public.gmane.org>
Cc: mailing list for ConTeXt users
	<ntg-context-wvrSQK3plZs@public.gmane.org>,
	dev-luatex-wvrSQK3plZs@public.gmane.org
Subject: Re: new/missing feature in luamplib
Date: Tue, 07 Aug 2012 11:00:36 +0200	[thread overview]
Message-ID: <5020D934.2090402@wxs.nl> (raw)
In-Reply-To: <86A1AFB8-7483-4B6A-9A52-758DECEF6B96-KIERECuABvX/D1n+0JDH9g@public.gmane.org>

On 7-8-2012 10:33, Taco Hoekwater wrote:
> Hi,
>
> On Aug 7, 2012, at 10:12 AM, Hans Hagen wrote:
>
>> 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).
>
> I was under the impression that this was all that the proposed patch does. Luamplib
> did not allow any (tex nor lua) escapes within the block, if I understand correctly.

ok, so it's not a luatex/mplib issue but something for the maintainer of 
that package as deciding what characters need what catcode is a package 
issue (probably obeying \ { } is enough then)

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
-----------------------------------------------------------------

      parent reply	other threads:[~2012-08-07  9:00 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 ` [Dev-luatex] " Hans Hagen
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 [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=5020D934.2090402@wxs.nl \
    --to=pragma-42p/b7yzot0@public.gmane.org \
    --cc=dev-luatex-wvrSQK3plZs@public.gmane.org \
    --cc=ntg-context-wvrSQK3plZs@public.gmane.org \
    --cc=taco-KIERECuABvX/D1n+0JDH9g@public.gmane.org \
    /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).