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