ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
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: Wed, 28 Feb 2024 12:24:44 +0100	[thread overview]
Message-ID: <9483e6b9-fb5c-86dd-c8cc-8cf43dea651c@gmx.es> (raw)
In-Reply-To: <811502b7-32d4-4131-843e-c9e653aa3c8a@fastwebnet.it>

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 os.rename only on when
the condition takes place.

It would be as to write:

  if x or environment.currentrun >= environment.maxnofruns then
    os.rename(pdf_file, ("%s-%s.pdf"):format(tex.jobname, sha_pdf))
  end

"x" would be the condition where the .tua/.tuc files are identical.

Do you know where that condition is written in the code, so ConTeXt
doesn’t perform another run?

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
___________________________________________________________________________________

  reply	other threads:[~2024-02-28 11:32 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 [this message]
2024-02-23 22:58 ` Bruce Horrocks
2024-02-27 10:08   ` Pablo Rodriguez via ntg-context

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=9483e6b9-fb5c-86dd-c8cc-8cf43dea651c@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).