Opened 19 years ago
Closed 19 years ago
#1545 closed defect (fixed)
Section 6.48.1 nitpick
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | lowest | Milestone: | |
| Component: | Book | Version: | TESTING |
| Severity: | trivial | Keywords: | |
| Cc: |
Description
Noted in the installation instructions:
"The meaning of the configure options:"
Should "configure" be encapsulated in <command> tags?
Change History (9)
comment:1 by , 19 years ago
comment:2 by , 19 years ago
Agreed on the first point - I wouldn't bother marking up the ./configure as a command as we don't do it anywhere else.
As for the singular/plural form of 'option', I'd prefer it matched the number of options being passed to ./configure but I'm certainly not going to hold a release up because of it. If you're in the area anyway and spot it doesn't tally up, feel free to change it, otherwise I wouldn't bother.
comment:3 by , 19 years ago
The problem is that it currently doesn't match the options passed to configure (expept possibly by accident). What it does match is the number of options *explained* below it (we don't duplicate explanations so the number explained rarely, if ever, matches the number actually passed).
Shall I change it according to the number of args passed to configure instead of the number of args explained (which seems more proper IMO).
comment:4 by , 19 years ago
Well, the way I read it is that the singular/plural form in "The meaning of the configure options:" relates to the number of items in the list that follows. I can see why folks would think it relates to the number of options passed to configure though. I now think it'd be easier all round if we just stick with the plural form, "options", regardless of how many options are passed to configure and/or explained in the list that follows the wording.
comment:5 by , 19 years ago
| Owner: | changed from to |
|---|
comment:6 by , 19 years ago
I've changed all of them to plural (not committed, yet). One more thing to note, though, is that gcc and binutils pass2, as well as chapter6/glibc, say
"The meaning of the *new* configure options"
Matt, please advise as to whether or not new should stay.
comment:9 by , 19 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Fixed in testing (r6075). Closing bug.
It isn't anywhere else in the book. That same sentence is used in 20 different places according to a quick grep I did. At least in perl's case if we go with command tags we would have to s/configure/configure.gnu/.
Also, I noticed that option is sometimes singular and sometimes plural. As a general heading to a list, couldn't it always be plural?
I'll defer to someone else's judgment on these points.