From: Hans van der Meer via ntg-context <ntg-context@ntg.nl>
To: NTG ConTeXt <ntg-context@ntg.nl>
Cc: Hans van der Meer <havdmeer@ziggo.nl>
Subject: Re: modules not found
Date: Wed, 8 Sep 2021 12:53:14 +0200 [thread overview]
Message-ID: <FC66452E-D019-41D0-A6BF-EF63FD2EB94D@ziggo.nl> (raw)
In-Reply-To: <50634DEB-8910-4C40-B522-2F22B65CFA8F@ziggo.nl>
[-- Attachment #1.1: Type: text/plain, Size: 1929 bytes --]
Further investigation seems to indicate that the module files are not found when initiating the context run from another directory. Though previously this was no problem.
I have moved the whole ConTeXt machinery from $HOME to another volume. Could that cause the problem? Allthough I set their location in the .bashrc.
# The current version of the ConTeXt luametatex in use:
CONTEXTLMTX=/Volumes/REALM/TeX/context
export CONTEXTLMTX
PATH=$CONTEXTLMTX/tex/texmf-osx-64/bin:$PATH ; export PATH
dr. Hans van der Meer
> On 8 Sep 2021, at 12:46, Hans van der Meer via ntg-context <ntg-context@ntg.nl> wrote:
>
> Here is something I do not understand about \usemodule.
>
> My modules are in two places because I wanted development and production separated:
> (1) Volume/TeX/texmf/modules/
> (2) Volume/TeX/texmf/modules-new/
>
> Unexpected and suddenly loading files from the first directory does not occur any longer: modules > 'hvdm-tak' is not found
> But modules from modules-new load without a hitch: modules > 'hvdm-load' is loaded
>
> I have discard the caches and rebuilt them to no avail. Then trying mtxrun --locate filename does not show any location not even from the files that are loaded, just an empty line.
> What happens inside \usemodule to cause this? I confess being baffled. And how to convince ConTeXt to find all my modules?
>
> dr. Hans van der Meer
>
>
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________
[-- Attachment #1.2: Type: text/html, Size: 5447 bytes --]
[-- Attachment #2: Type: text/plain, Size: 493 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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2021-09-08 10:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-08 10:46 Hans van der Meer via ntg-context
2021-09-08 10:53 ` Hans van der Meer via ntg-context [this message]
2021-09-08 11:21 ` Hans Hagen via ntg-context
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=FC66452E-D019-41D0-A6BF-EF63FD2EB94D@ziggo.nl \
--to=ntg-context@ntg.nl \
--cc=havdmeer@ziggo.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).