autoconf-patches
[Top][All Lists]
Advanced

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

Re: documentation punctuation fixes


From: Akim Demaille
Subject: Re: documentation punctuation fixes
Date: 17 Apr 2001 15:05:41 +0200
User-agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.1 (Cuyahoga Valley)

> 2001-04-13  Steven G. Johnson  <address@hidden>
>         * doc/autoconf.texi: Fixes for punctuation and grammar..  Replace
>         "..." with "@dots{}" except when "..." is in literal code.
>  @example
> -... && my_foos="$my_foos fooo"
> -... && my_foos="$my_foos foooo"
> address@hidden && my_foos="$my_foos fooo"
> address@hidden && my_foos="$my_foos foooo"

Does it come out properly?


>  @example
> -... && AC_CONFIG_FOOS(fooo)
> -... && AC_CONFIG_FOOS(foooo)
> address@hidden && AC_CONFIG_FOOS(fooo)
> address@hidden && AC_CONFIG_FOOS(foooo)
>  @end example

Likewise

>  But when things go wrong, you'll thank the Autoconf team for
> address@hidden
> address@hidden@dots{}

Please, change this into ``you'll be happy that autoheader exists'' or
something like that.  I was a bit too angry when I wrote that.


> +since not all shells properly understand @samp{"address@hidden"foo"@dots{} 
> `"}.
> +Worse yet, not all shells understand @samp{"address@hidden"foo\"@dots{} `"} 
> the same

Why are the quotes escaped?  Do you really mean to move to @dots?  I'm
not sure what you mean by `except when "..." is in literal code'.


>  @noindent
> -...but beware of the @address@hidden bug from Solaris (see above).  For 
> safety,
> address@hidden beware of the @address@hidden bug from Solaris (see above).  
> For safety,

Do we need to keep this {}?  Can we write address@hidden but'?  This is really
ugly :(


> -shell is known to not support the @sc{posix.2} syntax @samp{[!...]}
> +shell is known to not support the @sc{posix.2} syntax @address@hidden
>  (when in interactive mode, @command{zsh} is confused by the
> address@hidden syntax and looks for an event in its history because of
> address@hidden@dots{}]} syntax and looks for an event in its history because 
> of
>  @samp{!}).  Many shells do not support the alternative syntax
> address@hidden (Solaris, Digital Unix, etc.).
> address@hidden@dots{}]} (Solaris, Digital Unix, etc.).

Likewise.

>  @c FIXME: Grmph, yet another quoting myth: quotation has *never*
>  @c prevented `expansion' of $1.  Unless it refers to the expansion
> address@hidden of the value of $1?  Anyway, we need a rewrite here...
> address@hidden of the value of $1?  Anyway, we need a rewrite address@hidden

:) :) :)

>  @example
>  @group
> -if ...; then
> +if @dots{}; then
>    AC_REQUIRE([SOME_CHECK])
>  fi
> -...
> address@hidden
>  SOME_CHECK
>  @end group
>  @end example

?

>  Synopsis:
>  @example
> -./config.status @var{option}... address@hidden@dots{}]
> +./config.status @address@hidden address@hidden@dots{}]
>  @end example

?

>  @maindex CHECKING
> -Same as @samp{AC_MSG_NOTICE([checking @var{feature-description}...]}.
> +Same as @samp{AC_MSG_NOTICE([checking @address@hidden

?



reply via email to

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