Re: CVS Texinfo fails to build the Autoconf manual (from git)

[Patrice Dumas]

On Tue, Jul 17, 2012 at 10:46:58AM -0600, Eric Blake wrote:
> 
> What does this mean to the end user?  Autoconf needs to have a macro
> whose expansion does not end with the current line, and where the manual
> can be compiled with both old and new tools (that is, I do not want to
> force autoconf development to upgrade to the latest texinfo just to
> compile the manual).  If you subtly change semantics of the approach
> autoconf is currently using, then you also need to document a construct
> that will work for both old and new tools

I may be missing something, but simply dropping the @c should be
correct?  I tested info output (from makeinfo in C) and dvi output, 
and it seemed to be ok with and without the @c.  The new 
implementation will work only without the @c.

But, why was the @c added in the first place?  Is it important for
something now or was it important for some older versions of texinfo.tex
or makeinfo?




PS: there is in fact another change in behaviour that seems more 
problematic to me, the protection of the line by the @ adds a space within 
the @samp, this looks wrong and I will work on that as soon as
possible.

-- 
Pat