From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Wolfgang Schuster <wolfgang.schuster@gmail.com>
Subject: Re: Ctx ... Lua
Date: Wed, 22 Aug 2012 15:03:54 +0200 [thread overview]
Message-ID: <5034D8BA.4000001@wxs.nl> (raw)
In-Reply-To: <1DB4EA15-3D6E-44D5-A696-BB096BEDC8A0@gmail.com>
On 22-8-2012 13:26, Wolfgang Schuster wrote:
>
> Am 22.08.2012 um 13:15 schrieb Procházka Lukáš <LPr@pontex.cz>:
>
>> Hello,
>>
>> sometimes in this mail discussion I'm encountering a Ctx/Lua command which has been unknown for me or I would use other (known) commands to do the job.
>>
>> So - would it be possible to explain
>>
>> - what's the difference/advantage btw \directlua and \ctxlua
>
> No difference, just another name, there are even more synonyms.
The \ctxlua variant is somewhat more future proof. In the past
\directlua had a mandate extra argument. Also, the \ctxlua macro
can use a dedicated message namespace if needed and future versions
might have more tracing.
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
___________________________________________________________________________________
prev parent reply other threads:[~2012-08-22 13:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-22 11:15 Procházka Lukáš
2012-08-22 11:26 ` Wolfgang Schuster
2012-08-22 13:03 ` 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=5034D8BA.4000001@wxs.nl \
--to=pragma@wxs.nl \
--cc=ntg-context@ntg.nl \
--cc=wolfgang.schuster@gmail.com \
/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).