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