From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: Denis Maier via ntg-context <ntg-context@ntg.nl>
Cc: Hans Hagen <j.hagen@freedom.nl>
Subject: Re: [NTG-context] Can ConTeXt write its pdf to a different directory?
Date: Sat, 27 May 2023 12:09:04 +0200 [thread overview]
Message-ID: <c846257e-0f22-d7fb-cd08-8213a62ff483@freedom.nl> (raw)
In-Reply-To: <8feec2e4d53b41b0898f66565c42ae2a@unibe.ch>
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
___________________________________________________________________________________
next prev parent reply other threads:[~2023-05-27 10:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-27 1:52 peter.hopcroft--- via ntg-context
2023-05-27 3:53 ` Max Chernoff via ntg-context
2023-05-27 9:44 ` peter.hopcroft--- via ntg-context
2023-05-27 9:51 ` Denis Maier via ntg-context
2023-05-27 10:09 ` Hans Hagen via ntg-context [this message]
2023-08-07 1:58 ` [NTG-context] " Jethro Djan
2023-08-07 6:54 ` Hans Hagen
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=c846257e-0f22-d7fb-cd08-8213a62ff483@freedom.nl \
--to=ntg-context@ntg.nl \
--cc=j.hagen@freedom.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).