Date: Fri, 12 Nov 1999 09:43:07 -0500 From: Greg Lehey <grog@mojave.sitaranetworks.com> To: Sheldon Hearn <sheldonh@uunet.co.za>, Nik Clayton <nik@freebsd.org> Cc: Bruce Evans <bde@zeta.org.au>, obrien@NUXI.com, cvs-committers@freebsd.org, cvs-all@freebsd.org Subject: Re: cvs commit: src/contrib/grep/doc grep.1 Message-ID: <19991112094307.28720@mojave.sitaranetworks.com> In-Reply-To: <6216.942392728@axl.noc.iafrica.com>; from Sheldon Hearn on Fri, Nov 12, 1999 at 09:45:28AM %2B0200 References: <19991111235932.A62263@catkin.nothing-going-on.org> <6216.942392728@axl.noc.iafrica.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Friday, 12 November 1999 at 9:45:28 +0200, Sheldon Hearn wrote:
>
> On Thu, 11 Nov 1999 23:59:32 GMT, Nik Clayton wrote:
>
>> I concur with Greg. "The cat(1) command..." or "The cat(1) utility"
>> (or even "The /etc/rc.conf file...") all read as being stilted and
>> redundant.
>
> By the way, I thought about the argument that the use of mixed case
> forces the reader to verify the case of the actual command. Since we
> always use the correct case in the synopsis, I'm not even sure that
> there's anything wrong with using mixed case in the manpages.
Sure there is. It conflicts. If you always spell it the correct way,
there's no room for confusion. That applies to the page title, BTW:
the current mdoc(7) man page states:
.Dt DOCUMENT_TITLE [section] [volume] Title, in upper case.
I disagree with this upper case provision for the same reason.
There's really no good reason for it, especially if it only occurs
there.
Greg
--
Finger grog@lemis.com for PGP public key
See complete headers for address and phone numbers
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19991112094307.28720>