[NTG-context] What is preloaded by “mtxrun --script”?

16 Feb 2011

      Hi all,

I noticed that although mtxrun preloads some of the context libs
that doesn’t cover everything available during an ordinary mkiv
run.  What would be the canonical way to load additional libs
like “luat-ini” &c. on demand? “environment.loadluafile()”? Can
this be configured globally? Is it wise to mess with “own.libs”
in mtxrun?

Example: This snippet checks the global env for some tables.
“mtxrun --script” doesn’t find any while some of them are there
when processed as cld.

···8<····························································

-- http://www.ntg.nl/pipermail/ntg-context/2010/054982.html
local testme = {
    "userdata", "thirddata", "moduledata", "documentdata", "parametersets",
    --"document"
}

for _,item in next, testme do
    local i = _G[item]
    if i then
        print(item, table.serialize(i))
    else
        print(item, "Nope!")
    end
end

-- Comprehensive:
--for _,k in next,table.sortedkeys(_G) do
    --print(k,_G[k])
--end

···8<····························································

(My issue is that I’m testing the lua internals of module code
without having to startup the whole big typesetting environment.
Would be much easier if everything normally accessible from
inside an mkiv session was there as well.)

Thanks for any insights, Philipp

[NTG-context] What is preloaded by “mtxrun --script”?

Philipp Gesang