From: Stanislav Sokolenko <stanislav@sokolenko.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Finding lua file for module using \registerctxluafile
Date: Wed, 18 Jul 2018 14:07:27 -0300 [thread overview]
Message-ID: <e99c8b2e-1199-ff28-86ee-5322bbe4f0c1@sokolenko.net> (raw)
Dear list,
I've recently written a small module p-mymod.tex which uses lua code in
p-mymod.lua. In order to load this lua code, I use
\registerctxluafile{p-mymod}{1.001} (copying the example of
m-database.mkiv). However, it seems like the search path for lua files
isn't the same as for context module files.
When a context file that uses p-mymod through \usemodule[mymod] is
placed in a subdirectory, it finds p-mymod, but not the lua portion:
p-mymod.tex
p-mymod.lua
subdir/test.tex
Placing the lua file inside the subdirectory resolves this problem:
p-mymod.tex
subdir/p-mymod.lua
subdir/test.tex
What is the suggested method to change the lua search path? Ideally, I'd
like to avoid placing the files in
$TEXMF/tex/context/third/<modulename>/<files> as this module is quite
intimately tied to the specific project and it doesn't make much sense
to separate the files too much.
Thanks,
Stan
___________________________________________________________________________________
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 reply other threads:[~2018-07-18 17:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-18 17:07 Stanislav Sokolenko [this message]
2018-07-18 20:25 ` Hans Hagen
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=e99c8b2e-1199-ff28-86ee-5322bbe4f0c1@sokolenko.net \
--to=stanislav@sokolenko.net \
--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).