From: Pablo Rodriguez via ntg-context <ntg-context@ntg.nl>
To: ntg-context@ntg.nl
Cc: Pablo Rodriguez <oinos@gmx.es>
Subject: [NTG-context] Re: output filename with SHA256
Date: Tue, 27 Feb 2024 11:08:23 +0100 [thread overview]
Message-ID: <5e672140-0866-6277-e90d-6802fa5ae782@gmx.es> (raw)
In-Reply-To: <32E9F0AB-980E-4871-8718-36E344FA0774@scorecrow.com>
On 2/23/24 23:58, Bruce Horrocks wrote:
>> On 23 Feb 2024, at 13:32, Pablo Rodriguez via ntg-context <ntg-context@ntg.nl> wrote:
>> [...]
>> Is there any way to check if compilation needs any other run?
>> [...]
> Rather than use the wrapup() hook can why not rename the file using
> a second job on the command line?
>
> So your compile command might look like:
>
> $ context jobname.tex add_sha.tex
Hi Bruce,
this totally makes sense to me.
But (shame on me!) this is the first time I will type context followed
by two files.
This is also the first time when I see that invoking ConTeXt with more
than a file makes sense to me.
Many thanks for your help,
Pablo
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2024-02-27 10:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-23 13:32 [NTG-context] " Pablo Rodriguez via ntg-context
2024-02-23 15:01 ` [NTG-context] " mf
2024-02-28 11:24 ` Pablo Rodriguez via ntg-context
2024-02-23 22:58 ` Bruce Horrocks
2024-02-27 10:08 ` Pablo Rodriguez via ntg-context [this message]
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=5e672140-0866-6277-e90d-6802fa5ae782@gmx.es \
--to=ntg-context@ntg.nl \
--cc=oinos@gmx.es \
/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).