From: mf <massifr@fastwebnet.it>
To: ntg-context@ntg.nl
Subject: Re: Using Lua files in project structure
Date: Sun, 5 Apr 2020 15:39:55 +0200 [thread overview]
Message-ID: <3b1cf50e-8ed8-d04f-8936-5a9678a8bfd1@fastwebnet.it> (raw)
In-Reply-To: <CAKyqqab2MJD7DKOpHR-Z_-7J-p68o82nX8UBQ78OE3oyvam8jQ@mail.gmail.com>
Il 05/04/20 15:00, Jairo A. del Rio ha scritto:
> I'm writing a project in ConTeXt MKIV and I want to load some (pure) Lua
> libraries and bindings (defining \ctxlua and the like). For instance, I
> have the file foo.lua with some macros and I want to use them in my
> project. Something like this:
>
> \startproject project
> %\component foo.lua %This does not work
> %\environment foo.lua %This does not work
> %\input foo.lua %This does not work
> %\directlua{dofile("foo.lua")} %This does not work even when the project
\directlua{require("foo")}
or
\startluacode
require("foo")
\stopluacode
> file and foo.lua are in the same folder.
> \stopproject
>
> What should I do? Thank you in advance.
Best wishes,
Massi
___________________________________________________________________________________
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2020-04-05 13:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-05 13:00 Jairo A. del Rio
2020-04-05 13:10 ` Thomas A. Schmitz
2020-04-05 13:39 ` mf [this message]
2020-04-05 14:28 ` Wolfgang Schuster
2020-04-05 15:49 ` Jairo A. del Rio
2020-04-05 16:05 ` Wolfgang Schuster
[not found] ` <CAKyqqabbbkDX38CjPk+AGmJ+GqpEKKbq9S0deddhVuM_UnLKnQ@mail.gmail.com>
2020-04-06 13:59 ` Fwd: " Jairo A. del Rio
2020-04-06 16:11 ` Aditya Mahajan
2020-04-06 16:38 ` Jairo A. del Rio
2020-04-06 16:34 ` Wolfgang Schuster
2020-04-05 16:19 ` Aditya Mahajan
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=3b1cf50e-8ed8-d04f-8936-5a9678a8bfd1@fastwebnet.it \
--to=massifr@fastwebnet.it \
--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).