[NTG-context] Re: output filename with SHA256

2024-02-28 Thread Pablo Rodriguez via ntg-context
On 2/23/24 16:01, mf wrote: > [...] > A new run is started unless: > [...] > - the tuc file is identical to the one of the previous run Hi Massi, many thanks for your reply. If ConTeXt relies on that condition to stop compilation, then it would be great to know how it is performed to invoke

[NTG-context] Re: output filename with SHA256

2024-02-27 Thread Pablo Rodriguez via ntg-context
On 2/23/24 23:58, Bruce Horrocks wrote: >> On 23 Feb 2024, at 13:32, Pablo Rodriguez via ntg-context >> 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

[NTG-context] Re: output filename with SHA256

2024-02-23 Thread Bruce Horrocks
> On 23 Feb 2024, at 13:32, Pablo Rodriguez via ntg-context > wrote: > > Dear list, > > I have the following sample file: > > \starttext > whatever > > \startluacode > luatex.wrapup( > function() >local t = {} >local pdf_file_name = tex.jobname..".pdf" >local sha_pdf =

[NTG-context] Re: output filename with SHA256

2024-02-23 Thread mf
Il 23/02/24 14:32, Pablo Rodriguez via ntg-context ha scritto: Dear list, I have the following sample file: \starttext whatever \startluacode luatex.wrapup( function() local t = {} local pdf_file_name = tex.jobname..".pdf" local sha_pdf =