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

[Gavin Smith]

> Now here is the funny story, I have made a correction of texi2dvi
> (attached to this email), and it converts all pathes from MSys to MSW
> for both input file and TeX envvar, everything seemed ok but compilation
> of dummy.texi was still failed. So I read the error message a little bit
> more carefully (one should always read carefully error message to know
> what the error is, rather than guess it) and I realized that the file
> that TeX could not find with `{dummy_inc.texi}', not `dummy_inc.texi'
> (ie erroneously embraced in curly brackets). I could have entered
> `dummy_inc.texi' instead of `../../../dummy_inc.texi' and it would have
> also worked, because both pathes are in TEXINPUTS. That was just an
> error syntax in dummy.texi as I had written
>
>    @include{dummy_inc.texi}
>
> instead of
>
>    @include dummy_inc.texi

So there's no problem then?


> But that is not all : indeed MikTeX engines are Msys applications, they
> understand both path formats, so :
>
> - the latest (rev 6609) texi2dvi on the repo works fine on dummy.texi
>   once the @include syntax error is fixed, and
> - my latest patch (attached to this email) works also fine

Can you send  the patch instead of the whole file so I can see what you changed?


> - my patch is useless for MikTeX 2.9, however I cannot say if this is
>   the case for other MSW TeX distributions (or earlier MikTeX), can we
>   rely on this that the engines are Msys application ? And even if that
>   is the case, what will happen if the tex engines are launched from
>   another bash implementation (if any ? what djgpp is ?). I don't think
>   we need to handle cygwin case, I don't know cygwin but what I had
>   heard is that it is a complete Linux environment with its own TeX
>   distribution, ie it is more similar to a linux virtual machine,
>   completely different to what Msys is: a lightweight MSW native *nixy
>   port with tricks to handle *nixy path format, that is why you can
>   launch native MSW application from Msys provided that

If we don't know if there's a problem or not, let's not worry about it
until someone reports a problem on one of those systems.