On 21 August 2015 at 14:52, Vincent Belaïche <[email protected]> wrote:
> So yes the .toc and the other output files are there, and that does not
> suffice for texi2dvi to trigger one more run. As I said the problem is
> that MikTeX pdftex does not traces the \openout into the log file.
To tell whether it's been turned off by Texinfo, you could try
$ cat openout.dvi
\newwrite \ourwrite
\openout \ourwrite dum.dum
\end
$ pdftex openout.dvi
This is pdfeTeX, Version 3.141592-1.21a-2.2 (Web2C 7.5.4)
entering extended mode
(./openout.dvi [1{/usr/share/texmf-var/fonts/map/pdftex/updmap/pdftex.map}] )</
usr/share/texmf/fonts/type1/bluesky/cm/cmr10.pfb>
Output written on openout.pdf (1 page, 3181 bytes).
Transcript written on openout.log.
$ cat openout.log
This is pdfeTeX, Version 3.141592-1.21a-2.2 (Web2C 7.5.4)
(format=pdftex 2010.5.17) 21 AUG 2015 15:32
entering extended mode
**openout.dvi
(./openout.dvi
\ourwrite=\write0
[1
\openout0 = `dum.dum'.
{/usr/share/texmf-var/fonts/map/pdftex/updmap/pdftex.map}] )</usr/share/texmf/f
onts/type1/bluesky/cm/cmr10.pfb>
Output written on openout.pdf (1 page, 3181 bytes).
$
As you see the output of the \openout line is on by default here.
