On Mon, 16 Apr 2012, Hans Hagen wrote:
On 16-4-2012 15:00, Helge Blischke wrote:
Hans Hagen
writes: On 15-4-2012 23:57, Helge Blischke wrote:
I try to process a ConTeXt project residing in a directory different from the current directory (where context is called), imagine e.g. a NFS mounted directory on a different host.
I tried to point context to the project directory by specifying it by the command line option --path=absolute_path_to_the_directory but that did not work.
mtxrun --path=... --script context ...
But what to do if the directory specified by the --path= option is not writeable for the user executing mtxrun?
then put all the project files in <texroot>/texmf-project/tex/context/user, run mtxrun --generate, and run on a directory where the used can mess around
Is there a tree, other than TEXMFHOME, which is scanned at runtime? (so that mtxrun --generate is not needed). For example, one can do the following: TEXMFHOME=path-to-project-files context filename But this overwrites the default value of TEXMFHOME. If the mtxrun --generate step were not needed, one could do the same with TEXMFPROJECT tree. Aditya