[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: documentation about '-d' in AM_YFLAGS is suboptimal

From: Stefano Lattarini
Subject: Re: documentation about '-d' in AM_YFLAGS is suboptimal
Date: Wed, 12 Jan 2011 23:57:55 +0100
User-agent: KMail/1.13.3 (Linux/2.6.30-2-686; KDE/4.4.4; i686; ; )

On Wednesday 12 January 2011, Ralf Wildenhues wrote:
> OK with nits addressed.
> Thanks!
> Ralf
> [CUT]
> > From a report by ???????? ????????????????????.
> My email client renders this as a bunch of question marks only.  Please
> ensure that both the git log entry and the ChangeLog entry are properly
> encoded in UTF-8.
They should be (they both looks ok in vim with :set enc=utf-8).

> > --- a/doc/automake.texi
> > +++ b/doc/automake.texi
> > @@ -6078,7 +6078,12 @@ intended for the @file{} author.
> >  @code{AM_YFLAGS} is usually used to pass the @option{-d} option to
> >  @command{yacc}.  Automake knows what this means and will automatically
> >  adjust its rules to update and distribute the header file built by
> > address@hidden -d}.  What Automake cannot guess, though, is where this
> > address@hidden address@hidden note that @command{automake} recognizes
> > address@hidden in @code{AM_YFLAGS} only if it is not clustered with other
> > +options; for example, it won't be recognized if @code{AM_YFLAGS} is
> > address@hidden, but it will be if @code{AM_YFLAGS} is @samp{-d -t} or
> > address@hidden -d}.}.
> Generally, @footnote's should be used sparingly, as they disrupt the
> flow of reading and don't render well in the info output.  I guess it's
> acceptable here though.
> Please use @option for denoting the options here.
OK.  Sorry for the noise, but for some stupid reason I thought that using
@option with more (whitespace-separated) arguments was inappropriate.  Go

Merged into maint and yacc-work, and merged both into master.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]