Re: [bug #43122] texi2dvi does not compile enough times to get toc

[Gavin Smith]

On 30 August 2015 at 22:56, Karl Berry <address@hidden> wrote:
>     Possible problem: a *.fls file meets the *.??s glob pattern for sorted
>     index files. Probably not a problem.
>
> I have used, and still use, an "fl" index in actual documents.  So it
> seems like it is in fact a conflict, unfortunately.  I doubt there is
> any portable way to specify the recorder file name.  Sigh.  -k
>

I tried with a fl index and indeed it broke.

My first idea was to rename the recorder file from *.fls, e.g. to
*.flz. This didn't work though, I think because the final run of TeX
has *.fls open for writing, stopping it being opened for reading.

I realised that there are two sets of auxiliary files, the old and the
new, so we could read from the old while writing to the new (i.e.
overwriting the *.fls file).

I've attached what I have so far. I make the saved files take priority
by taking . away from the beginning of the TEXINPUTS environment
variable. I reordered the execution so we could rename the *.fls log
file before it's overwritten by texindex.

Also the change of the catcode of ~ doesn't affect the test that's
been added, so I leave that alone.

I was hoping to stop texinfo.tex being read from the current
directory, but that seems not to work. (Even "tex info.texi" uses
texinfo.tex in the current directory instead of that which has been
installed.) Also the -I flags don't override texinfo.tex in the
current directory. This has caused me problems before. But on further
thought, it does make sense for "\input texinfo" in a TeX (Texinfo)
file to look for a "texinfo" file in the same directory.

I'm not too confident what I have here is right - there are quite a
few combinations, like pwd = directory containing file or not, whether
--tidy is used, whether index files already existed, whether index
files already existed in a *.t2d subdirectory after a --tidy run.
There are several ways to fail, for example no index at all, and
harder to spot, out-of-date indices, or texi2dvi running TeX too many
times. (I make that 48 tests required, which I'm sure I haven't done.)
Everyone please test with your favourite Texinfo (and/or LaTeX)
documents in creative ways and report what breaks.

texi2dvi
Description: Binary data

texi2dvi.diff3
Description: Binary data