Bug#815369: texi2pdf output filename bug?

2016-05-01 Thread Gavin Smith
On 1 May 2016 at 12:14, Gavin Smith wrote: > I haven't researched why --tidy makes a difference. I plan to stop > this error by making @value non-expandable when writing to auxiliary > files. This would have the effect that the value used would be the > value at the time when t

Bug#815369: texi2pdf output filename bug?

2016-05-01 Thread Gavin Smith
On 30 April 2016 at 22:57, Guo Yixuan wrote: > The mwe.texi file by Norbert: > > $ cat mwe.texi > \input texinfo @c -*-texinfo-*- > @setfilename min2.info > > What ever > @anchor{@value{cmd1} doc}@anchor{0} > Here we go > @bye > > ./mwe.aux:1: TeX capacity exceeded, sorry [input stack size=18

Bug#815205: another texinfo.tex bug in \scanmacro

2016-04-12 Thread Gavin Smith
On 12 April 2016 at 09:05, Norbert Preining wrote: > Here is a minimal example extracted from the sbcl sources that shows > the effect: > \input texinfo @c -*-texinfo-*- > > @iftex > @macro cl{name} > {@smallertt@phantom{concurrency:}@llap{cl:}}\name\ > @end macro > @end iftex > > Some text > >

Bug#815205: another texinfo.tex bug in \scanmacro

2016-04-11 Thread Gavin Smith
On 17 March 2016 at 07:25, Gavin Smith wrote: > I've checked and using \gdef instead of \def works, because the > definition took place within a TeX group: I've come across the following message: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815205#95: == The patch ment

Bug#815205: another texinfo.tex bug in \scanmacro

2016-03-19 Thread Gavin Smith
On 16 March 2016 at 10:01, Norbert Preining wrote: > > I reduced the problem to the following minimal not-working > example: > > > \input texinfo @c -*-texinfo-*- > > @iftex > @tex > \newif\ifdash > \long\def\dashp#1{\expandafter\setnext#1-\dashphelper} > \long\def\setnext#1-{\fu

Bug#815205: another texinfo.tex bug in \scanmacro

2016-03-19 Thread Gavin Smith
On 17 March 2016 at 01:31, Norbert Preining wrote: > > Ok, I tried your suggestion, but that again breaks: I've checked and using \gdef instead of \def works, because the definition took place within a TeX group: \input texinfo @c -*-texinfo-*- @iftex @tex \gdef\aaa#1{Hello #1} @end tex @end

Bug#815734: regression: ESS cannot be compiled

2016-03-05 Thread Gavin Smith
On 4 March 2016 at 21:28, Gavin Smith wrote: > On 4 March 2016 at 04:01, Norbert Preining wrote: >> The output is: >> ./bla.texi:9: Argument of @gobblespaces has an extra }. > > I got the same. I think it's easy enough to fix. The only possible > problem is that thi

Bug#815734: regression: ESS cannot be compiled

2016-03-04 Thread Gavin Smith
> > I have reduced the problematic case to the following minimal example: Thank you for taking the time to do this, Norbert. > From these two facts I'd declare that the new texinfo.tex that > you have in Debian is broken. > (Yes, that is a strong statement; but still breaking something > tha

Bug#815734: regression: ESS cannot be compiled

2016-03-04 Thread Gavin Smith
On 4 March 2016 at 04:01, Norbert Preining wrote: > The output is: > ./bla.texi:9: Argument of @gobblespaces has an extra }. I got the same. I think it's easy enough to fix. The only possible problem is that this error comes about due to an attempt to remove whitespace from the start of a macro a

Bug#815369: [BUG] command line definitions not expanded

2016-02-21 Thread Gavin Smith
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

Bug#815369: [BUG] command line definitions not expanded

2016-02-21 Thread Gavin Smith
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