Hi, is there some mechanism (directive?) that gives me a list of files that were involved in making a PDF? Preferably only those outside of the texmf trees, but I could filter that myself. (With "latexmk -recorder somelatexfile" I get the file list as a .fls file.) My goal is to commit all used images to my git repo, while I often have a big collection of images that I didn’t use in the end and don’t need in the repo. Hraban
On 7/20/2024 9:31 AM, Henning Hraban Ramm wrote:
Hi,
is there some mechanism (directive?) that gives me a list of files that were involved in making a PDF? Preferably only those outside of the texmf trees, but I could filter that myself.
(With "latexmk -recorder somelatexfile" I get the file list as a .fls file.)
My goal is to commit all used images to my git repo, while I often have a big collection of images that I didn’t use in the end and don’t need in the repo. subconscious you know the answer:
look at the log file files are tagged with "start used files" of course you can also try \enabledirectives[system.dumpfiles=lua] and stare at the resulting job log file (jlg) (the default is xml but i noticed some empty entries in there ... a very old feature so i need to travel back in time now) if files are missing let me know 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 -----------------------------------------------------------------
Am 20.07.24 um 10:04 schrieb Hans Hagen:
subconscious you know the answer:
look at the log file
Not only sub*; I forgot to mention I’d like to avoid parsing that.
of course you can also try
\enabledirectives[system.dumpfiles=lua]
and stare at the resulting job log file (jlg)
Thank you! Now my downsampling bites me: { ["filename"]="…/img/m_k_i_v_Fenster_jpg_2ec2682ee73b38bbc98c6d1432bf1bcb.lowres.jpg", ["foundname"]="…/img/m_k_i_v_Fenster_jpg_2ec2682ee73b38bbc98c6d1432bf1bcb.lowres.jpg", ["fullname"]="…/img/m_k_i_v_Fenster_jpg_2ec2682ee73b38bbc98c6d1432bf1bcb.lowres.jpg", ["usedmethod"]="direct", }, I can disable it: { ["filename"]="…/img/Fenster.jpg", ["foundname"]="…/img/Fenster.jpg", ["fullname"]="…/img/Fenster.jpg", ["usedmethod"]="direct", }, But images lack the "filetype" entry that other file types have, it would have been useful. But checking the file extension is good enough for my task. Hraban
Hans provided me with a patch that allows \enabledirectives[system.dumpfiles=json] It will be in the next update, I guess. I’m using it with the new tool "addtogit.py" in https://codeberg.org/fiee/context-tools to add all files that are necessary for a ConTeXt job to the current git repository. Of course I could have parsed the log file. Hraban
participants (2)
-
Hans Hagen -
Henning Hraban Ramm