Re: problem with texi2dvi from texinfo 6.1

[Vincent Belaïche]

Hello Kurt,

It seems that some \ref is missing before the reference. Well I have
added it, and the only problem which I can see is that the ~ is handled
like a normal tilde.

But this is because texi2dvi uses this command:

Running pdflatex '\catcode126=12 \def\normaltilde{~}\catcode126=13 
\let~\normaltilde ' '\input' './test1.tex'

(ie ~ is changed into a normal tilde).

I think that the intention of this catcode change was to allow ~ in file
names, but maybe that should be made only for the input file
name. I.e. the command line should be instead like this:

pdflatex '\begingroup\catcode126=12\def\temp{' './test1.tex' 
'}\expandafter\endgroup\expandafter\input\expandafter{\temp}'

   Vincent.


Le 23/02/2016 08:14, Kurt Hornik a écrit :
>>>>>> Vincent Belaïche writes:
>
>> Dear Kurt,
>> Is the issue that texi2dvi does not make enough runs?
>
> Yes.
>
>> Could you send also a minimal example of Rd2.tex, I could then make a
>> trial on my machine to see if I can reproduce the issue ....
>
> Gavin had also asked for a smaller example (the one I had circulated was
> from production use).  
>
> So pls try the following:
>
>
>
>
> For me:
>
> $ texi2dvi test1.tex 
> This is pdfTeX, Version 3.14159265-2.6-1.40.16 (TeX Live 2015/Debian) 
> (preloaded format=latex)
>  restricted \write18 enabled.
> entering extended mode
> LaTeX2e <2016/02/01>
> Babel <3.9n> and hyphenation patterns for 79 languages loaded.
> (./test1.tex (/usr/share/texlive/texmf-dist/tex/latex/base/article.cls
> Document Class: article 2014/09/29 v1.4h Standard LaTeX document class
> (/usr/share/texlive/texmf-dist/tex/latex/base/size10.clo))
> (/usr/share/texlive/texmf-dist/tex/latex/hyperref/hyperref.sty
> (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/hobsub-hyperref.sty
> (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/hobsub-generic.sty))
> (/usr/share/texlive/texmf-dist/tex/latex/graphics/keyval.sty)
> (/usr/share/texlive/texmf-dist/tex/generic/ifxetex/ifxetex.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/oberdiek/auxhook.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/oberdiek/kvoptions.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/hyperref/pd1enc.def)
> (/usr/share/texlive/texmf-dist/tex/latex/latexconfig/hyperref.cfg)
> (/usr/share/texlive/texmf-dist/tex/latex/url/url.sty))
>
> Package hyperref Message: Driver (default): hdvips.
>
> (/usr/share/texlive/texmf-dist/tex/latex/hyperref/hdvips.def
> (/usr/share/texlive/texmf-dist/tex/latex/hyperref/pdfmark.def
> (/usr/share/texlive/texmf-dist/tex/latex/oberdiek/rerunfilecheck.sty)))
> No file test1.aux.
> (/usr/share/texlive/texmf-dist/tex/latex/hyperref/nameref.sty
> (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/gettitlestring.sty))
>
> Package hyperref Warning: Rerun to get /PageLabels entry.
>
> [1] [2] (/home/Hornik/tmp/ZZZ/test1.aux)
>
> Package rerunfilecheck Warning: File `test1.out' has changed.
> (rerunfilecheck)                Rerun to get outlines right
> (rerunfilecheck)                or use package `bookmark'.
>
>
> LaTeX Warning: Label(s) may have changed. Rerun to get cross-references right.
>
>  )
> Output written on test1.dvi (2 pages, 2800 bytes).
> Transcript written on test1.log.
>
> and
>
> $ echo $?
> 1
>
> Best
> -k
>
>
>>    Vincent.
>
>> Le 22/02/2016 22:19, Gavin Smith a écrit :
>>> The log files you sent help a bit. They contain lines like:
>>>
>>> Package hyperref Warning: Rerun to get /PageLabels entry.
>>>
>>> This explains why no "New xref files" messages are being printed by
>>> texi2dvi: the function xref_files_changed in texi2dvi sees that text
>>> in the log files and doesn't look in the log files. I don't have those
>>> lines in my log files (maybe due to different versions of packages),
>>> so what happens for me is different.
>>>
>>> I still don't know where exactly texi2dvi is quitting in your case,
>>> alas. Perhaps the output from
>>>
>>> sh -x ./texi2dvi --verbose Rd2.tex >Rd2.trace
>>>
>>> could help? I've attached what I got.
>>>
>>> Also deleting chunks from the file to get a smaller file that gives
>>> the same error can only help. (It would make the log files shorter and
>>> possibly easier to spot what's wrong.)
>>>
>>> NB I don't know if the problem is on my end or yours but I have awful
>>> trouble reading emails with long logs in the body of the email: could
>>> you try sending any long logs or output as attachments instead? That's
>>> if you weren't doing that already and my mail reader (GMail web
>>> interface) is displaying them inline).
>