On 5/27/2023 11:51 AM, Denis Maier via ntg-context wrote:
> I usually use a makefile for this.
> There I have build rule that first cds into the target directory, then calls context from there.
That is indeed the solution (also because the --path option will then
fetch from the source). The more lua hackery the more danger of
interference. The problem here is that a rename won't work in all
scenarios (different drives on windows for instance, or from local disk
to network drive).

Anyway, one can also give

   --runpath=sometargetpath

which i actually use to run for instance manuals, but there it is driven
in the file itself:

   % language=us runpath=texruns:manuals/musings

in combination with

   TEXRUNS=c:\data\temporary\texruns

so that I don't overwrite a stable manual in the source path. Over the
decades that context evolved there have been plenty such tricks added.

I could probably add a move option to the job ticket mechanism but that
has not changed in ages so ... workflows demands are too different.

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
        tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : https://contextgarden.net
___________________________________________________________________________________