> >Did this ever work, and if so, which version of texinfo.tex and
> >texi2dvi?
Forget this - sorry for the noise - this was introduced recently
by Debian packaging.
Can be closed on the texinfo side.
Norbert
PREINING, Nor
Hi Gavin,
no idea, guess so. I'll try on texinfo 4.8 in stable. I just was informed of
the report and it seems that it was working before.
I'll investigate, and hope that the maintainer of the package will comment, too.
Thanks
Norbert
On 21 February 2016 19:18:39 GMT+09:00, Gavin Smith
wro
On 21 February 2016 at 09:50, Norbert Preining wrote:
> HI Gavin,
>
>> The problem is that @setfilename is missing from the file, and
>> texi2dvi looks for that line to add the extra line. @setfilename was
>> required before, so this isn't a regression (I hope).
>
> Ahh, I see. The original did ha
HI Gavin,
> The problem is that @setfilename is missing from the file, and
> texi2dvi looks for that line to add the extra line. @setfilename was
> required before, so this isn't a regression (I hope).
Ahh, I see. The original did have a line like this:
@setfilename @value{cmd1}.info
so i
On 21 February 2016 at 06:19, Norbert Preining wrote:
> Hi Gavin, hi all
>
> (please keep Cc)
>
> I am sorry for all the bug reports, but here is the next one that
> surfaced when building the documentation for gcc.
>
> In short, it seems that definitions given on the command line
> --comm
Hi Gavin, hi all
(please keep Cc)
I am sorry for all the bug reports, but here is the next one that
surfaced when building the documentation for gcc.
In short, it seems that definitions given on the command line
--command='@set foobar value'
are not properly expanded in the aux files.
H
