Re: [patch #4610] Consolidated documentation patch

[Benno Schulenberg]

Charles Levert wrote:
> +7th Edition -s-1UNIX-s0

\s  (Although I don't like to see "Unix" in allcaps.)

> +to report byte offsets as if the file were \s-1UNIX\s0-style
> text file,

Missing an "a" after "were".

> -Copyright @copyright{} 2000, 2001 Free Software Foundation, Inc.
> +Copyright @copyright{} 1998--2005 Free Software Foundation, Inc.

If I'm not mistaken, the years listed here should be the ones in 
which _modified versions of this texi document were _released.

> +* GNU Options::          GNU extensions, grouped by categories.

Better "in categories" or "by category".

On second thought, I don't see the point of separating the POSIX 
options from the GNU extensions, and it kind of invalidates the 
categorisation.  If it really should be mentioned which options are 
POSIX, then it's easy to sum them up in some final paragrah.

So the categorisation I would do differently: put --help and -V in 
the Other Options, as these are so generic, they really shouldn't 
come first.

First would be Matching control: -e, -f, -i, -v, -w, -x.
Second, Output Control: -c --color, -L, -l, -m, -o, -q, -s.
Third, Output Line Prefix Control, with the addition of -n.
Fourth, Context Line Control.
Fifth, File and Directory Selection.
Sixth, Other Options: --help, --line-buffered, --mmap, -V, -U, -z.

> +The long option names are a @sc{gnu} extension in themselves,
> +but these options as such are from @sc{posix} specifications.

Better without "in themselves".

> +Each group may contain several matching lines
> +when they are close enough to each other
> +that two otherwise adjacent but divided groups connect
> +and can just merge into a single contiguous one.

"Each group may contain several matching lines
when these lines are separated by less than 2*NUM context lines."

> +regardless of the order in which these options may have been
> specified. 

Better simply "were specified".

> address@hidden --With-filename

No cap.

Benno