From: Pablo Rodriguez via ntg-context <ntg-context@ntg.nl>
To: ConTeXt users <ntg-context@ntg.nl>
Cc: Pablo Rodriguez <oinos@gmx.es>
Subject: [NTG-context] output filename with SHA256
Date: Fri, 23 Feb 2024 14:32:48 +0100 [thread overview]
Message-ID: <269aab33-7bea-dc17-04f5-0b89342a425d@gmx.es> (raw)
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 = utilities.sha2.hash256(io.loaddata(pdf_file_name))
local c_r = environment.currentrun
t[c_r] = sha_pdf
local exists_pdf = ("%s_%s-%s.pdf"):format(c_r-1, tex.jobname, t[c_r-1])
if io.exists(exists_pdf) then os.remove(exists_pdf) end
os.rename(pdf_file_name, ("%s_%s-%s.pdf"):format(c_r, tex.jobname,
sha_pdf))
end
)
\stopluacode
\stoptext
In short, it adds its SHA256 to the final filename.
Since renames the PDF document in each run, I would like to remove the
output from the previous run.
The table seems not to store the value from a previous run.
I see now that I am creating it again with each run.
Is there any way to check if compilation needs any other 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
___________________________________________________________________________________
next reply other threads:[~2024-02-23 13:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-23 13:32 Pablo Rodriguez via ntg-context [this message]
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
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=269aab33-7bea-dc17-04f5-0b89342a425d@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).