bug-texinfo
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: texi2dvi changes


From: Vincent Belaïche
Subject: Re: texi2dvi changes
Date: Fri, 25 Sep 2015 11:20:54 +0200


Le 25/09/2015 10:42, Gavin Smith a écrit :
> On 24 September 2015 at 21:54, Vincent Belaïche
> <address@hidden> wrote:
>>> I pointed out that the log files were being grep'd a lot to get the
>>> list of generated files. This won't happen as much now.
>>>
>>

[...]

>
> IIRC this change was part of avoiding an infinite loop happening due
> to the fls file being created as a recorder file, saved, and then
> overwritten as a sorted index file, and then differing from that which
> had been saved, indicating that another TeX run was required. Now only
> the files that are directly produced are compared, not the sorted
> index files. I wasn't sure if this was right for BibTeX (in case, for
> example, TeX produces a file A, which is then processed to create file
> B, which then in turn is processed to create a file C: then even if
> file A hasn't changed, if file B has we still need another run of the
> tools), but it appears to work. It's possible I could have done it in
> a simpler way, but I don't know.

For BibTeX you need both the .aux file and the .bib file(s), for
instance if you have essai.tex that needs essai-bib.bib, then you will
run ``bibtex "essai"'', that will look into essai.aux, get there the
\bibdata{essai-bib}, then look into essai-bib.bib.

Note that this is for the original bibtex, I don't know whether this is
the same with biblatex & biber which more & more people are using.

>
> It occurred to me why we don't simply check that the dvi or pdf file
> hasn't changed, and forget about the other files.

They you can't know what the next step if (bibtex, makeglossaries,
biber, makeindex, texindex, ...)...

> It's probably because those files are considered to be too big to back
> up and compare, and only comparing the auxiliary files is more
> efficient.
>

Well that may be true, latexmk makes an md5sum of the files to check for
change, that is probably faster if you account for this that the
bottleneck is disk access, not computation.


[...]

>
> Thanks for testing, good to hear it appears to be working.

Thanks to you Gavin,

   Vincent.

---
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel 
antivirus Avast.
http://www.avast.com




reply via email to

[Prev in Thread] Current Thread [Next in Thread]