Hans Hagen
On 16-4-2012 19:28, Aditya Mahajan wrote:
But this overwrites the default value of TEXMFHOME. If the mtxrun --generate step were not needed, one could do the same with TEXMFPROJECT tree.
One can indeed use texmfhome which is checked at runtime (but a large one will take time of course esp on a network share).
Here I always use texmf-project.
Of course one can also use \usepath (or context --path=... which does the same).
Hans
By trial and eror I found out that context --path=... tries to run the scripts and programs within that directory which leads to abort if e.g. the calling user has no write permission there. On the other hand, inserting a \usepath[...] just after the \start... command functions as exspected. Thus, I'd propose to provide an additional option --usepath=... what does exactly that, which avoids editing the main.tex file. Helge