[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: AC_PATH_PROGS_FEATURE_CHECK [was: Bug in gnulib-tools prevents bison
From: |
Noah Misch |
Subject: |
Re: AC_PATH_PROGS_FEATURE_CHECK [was: Bug in gnulib-tools prevents bison from bootstrapping] |
Date: |
Wed, 5 Sep 2007 15:29:10 -0700 |
User-agent: |
Mutt/1.5.9i |
On Wed, Sep 05, 2007 at 01:45:49PM -0700, Eric Blake-1 wrote:
> > > address@hidden AC_CHECK_PROG (@var{variable}, @var{prog-to-check-for},
> > @var{value-if-found}, @ovar{value-if-not-found}, @ovar{path},
> > @ovar{reject})
> > > address@hidden AC_CHECK_PROG (@var{variable}, @var{prog-to-check-for}, @
> > > + @var{value-if-found}, @ovar{value-if-not-found}, @
> > > + @dvar{path, $PATH}, @ovar{reject})
> >
> > Why the @\n? We don't do that elsewhere in the manual.
>
> The texinfo manual documents that inside @def*, @\n
> serves as a line-continuation marker and can be used to
> make the .texi source file fit 80-column editing; it
> has no effect on the final rendering in either info or dvi.
> I'm not particularly fond of long lines when they can be
> avoided, so I plan to ultimately convert the entire
> manual in that manner, as a matter of style (I already
> did it for M4's .texinfo source file). But in the
> meantime, I agree with your complaint that it should be
> an independent patch.
That does sound worthwhile. Thanks for clarifying.