From: "Kevin D. Robbins" <robbins.kevin.d@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: How to load a lua file into a named lua instance
Date: Fri, 20 Nov 2009 17:12:45 -0700 [thread overview]
Message-ID: <f5d0b64b0911201612j71cc7b9l4b838d80b67b7e9@mail.gmail.com> (raw)
In-Reply-To: <4B0718F1.5070705@wxs.nl>
[-- Attachment #1.1: Type: text/plain, Size: 2113 bytes --]
Hi Hans,
I started reading at \registerctxluafile in luat-cod.mkiv, but it wasn't
quite what I was looking for. But, I then stumbled on \definenamedlua in
luat-ini.mkiv. There, I learned of the function 'protect' in luat-ini.lua.
So, adding the line
protect("moduledata")
at the top of t-module.lua and then loading this file with 'dofile
(global.kpse.find_file ("t-module.lua", "tex"))' loads all my definitions
into the "moduledata" environment, so that I can directly address these
definitions in other TeX files within \modulecode{} or \startmodulecode ...
\stopmodulecode.
Kevin
On Fri, Nov 20, 2009 at 3:32 PM, Hans Hagen <pragma@wxs.nl> wrote:
> Kevin D. Robbins wrote:
>
>> Hi all,
>>
>> I have a module with lots of lua code, and I'd like to move most of the
>> lua code to a separate file, say t-module.lua. I have written all of the lua
>> code using \modulecode and \startmodulecode ... \stopmodulecode. But, when I
>> move the lua code to t-module.lua and load it with dofile, it seems to load
>> in the global instance instead of the third party module instance. Is there
>> any method to load an external lua file in a named instance?
>>
>
> \registerctxluafile{t-module}{}
>
>
> -----------------------------------------------------------------
> Hans Hagen | PRAGMA ADE
> Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
> tel: 038 477 53 69 | fax: 038 477 53 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
>
> ___________________________________________________________________________________
>
[-- Attachment #1.2: Type: text/html, Size: 3209 bytes --]
[-- Attachment #2: Type: text/plain, Size: 486 bytes --]
___________________________________________________________________________________
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:[~2009-11-21 0:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-20 22:15 Kevin D. Robbins
2009-11-20 22:32 ` Hans Hagen
2009-11-21 0:12 ` Kevin D. Robbins [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=f5d0b64b0911201612j71cc7b9l4b838d80b67b7e9@mail.gmail.com \
--to=robbins.kevin.d@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).