Hi,
On Wed, Jun 29, 2005 at 10:05:08AM -0400, Derek Price wrote:
> It depends who you listen to. I generally go by the Fourth edition of
> Strunk & White's, "The Elements of Style", which says, yes, there should
> always be a comma before the "and" or "or" in a list longer than two
> elements. Strunk & White is a widely accepted and oft quoted reference
> on English grammar and punctuation and has been around since 1957.
thank you for explanation. I'm not a native speaker, and my intuition came
from my native language. (We don't write the comme before "and" or "or" in
Czech.) I don't want to go against the tradition.
> >Another observing: "... the arguments of XYZ commands be separated ...
> >command."
> >I feel a bit uneasy about the repeating of the word "command".
>
> I don't in this context, but I like your rewording. Briefer is usually
> better if you can encapsulate the same information. :)
OK, I'm committig it; patch attached.
Thanks,
Stepan
Index: doc/autoconf.texi
===================================================================
RCS file: /cvsroot/autoconf/autoconf/doc/autoconf.texi,v
retrieving revision 1.922
diff -u -r1.922 autoconf.texi
--- doc/autoconf.texi 30 Jun 2005 12:29:19 -0000 1.922
+++ doc/autoconf.texi 30 Jun 2005 12:41:41 -0000
@@ -12282,9 +12282,9 @@
foo
@end example
-Also note that Posix requires that the arguments of the @samp{b}, @samp{t},
[EMAIL PROTECTED], and @samp{w} commands be separated by exactly one space from
their
-command. On the other hand, no white space is allowed between @samp{:} and the
+Also note that Posix requires that the @samp{b}, @samp{t}, @samp{r}, and
[EMAIL PROTECTED] commands be followed by exactly one space before their
argument.
+On the other hand, no white space is allowed between @samp{:} and the
subsequent label name.
@item @command{sed} (@samp{t})
