> > Looks like it could be used, with only a modest amount of wrapper
> > scripting, to really identify *all* the files used in a given LaTeX run
Thomas Esser <[EMAIL PROTECTED]> writes:
> I'd use KPATHSEA_DEBUG=4 for that.
OK, that is a good suggestion to compare. I did a first test just now.
Setting TEXMFLOG seems somewhat easier, because then I don't have to do
any extra work to separate the kdebug:fopen lines from any other output
that may be going to stderr. But in a first test it seems that using
KPATHSEA_DEBUG=4 captures a couple of additional bits of information
that TEXMFLOG does not: The filename of the TeX executable; the filename
of the texmf.cnf file; and the filename of the \jobname.aux file. (I
don't know why the last one is not recorded in the TEXMFLOG file,
perhaps I made some mistake.)
(Investigating further ...)
Aha, very interesting. It seems that files read by TeX are not recorded
in TEXMFLOG if they are found in the current directory. I wonder if this
is intended behavior (probably not??), I will have to look into it some
more ...
