From: splite@purdue.edu
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] first capital letter in function names at man pages, why?
Date: Fri, 21 May 2004 09:44:26 -0500 [thread overview]
Message-ID: <20040521144426.GA2329@sigint.cs.purdue.edu> (raw)
In-Reply-To: <69e03455a280e06d01209386e5a557ea@plan9.escet.urjc.es>
On Fri, May 21, 2004 at 04:27:14PM +0200, Fco.J.Ballesteros wrote:
> BTW, from what has been said, I think that using the function name
> as-is (no caps) in the manual page would suffice to keep all of us happy.
> Am I right? Or someone already discarded this fix?
You are indeed right. man pages are reference works, not the Canterbury
Tales. If their usefulness as references would be impaired by slavish
adherence to formal English syntax then stuff the rules.
next prev parent reply other threads:[~2004-05-21 14:44 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-20 14:59 [9fans] first capital letter in function names at man pages ¿why? Alberto Cortes
2004-05-20 15:22 ` Rob Pike
2004-05-20 15:53 ` [9fans] first capital letter in function names at man pages, why? Alberto Cortes
2004-05-20 16:44 ` Russ Cox
2004-05-20 17:20 ` Alberto Cortes
2004-05-20 17:31 ` rog
2004-05-20 17:43 ` Alberto Cortes
2004-05-20 17:50 ` Fco.J.Ballesteros
2004-05-21 17:20 ` Joel Salomon
2004-05-21 17:46 ` boyd, rounin
2004-05-21 18:11 ` Jason Gurtz
2004-05-21 18:21 ` boyd, rounin
2004-05-20 17:53 ` rog
2004-05-20 17:54 ` Alberto Cortes
2004-05-21 10:28 ` Gorka Guardiola Múzquiz
2004-05-21 10:29 ` Dave Lukes
2004-05-21 10:57 ` Alberto Cortes
2004-05-21 11:04 ` Gorka Guardiola Múzquiz
2004-05-21 12:23 ` Alberto Cortes
2004-05-21 12:30 ` Gorka Guardiola Múzquiz
2004-05-21 12:48 ` Alberto Cortes
2004-05-21 14:25 ` Fco.J.Ballesteros
2004-05-21 14:34 ` Alberto Cortes
2004-05-21 14:27 ` Fco.J.Ballesteros
2004-05-21 14:44 ` splite [this message]
2004-05-21 15:24 ` boyd, rounin
2004-05-21 15:29 ` Fco. J. Ballesteros
2004-05-21 16:23 ` Alberto Cortes
2004-05-21 14:50 ` boyd, rounin
2004-05-21 15:57 ` boyd, rounin
2004-05-24 2:10 ` Micah Stetson
2004-05-24 2:38 ` Greg Pavelcak
2004-05-24 3:47 ` Eric KD5UWL
2004-05-24 15:46 ` boyd, rounin
2004-05-24 22:33 ` Micah Stetson
2004-05-21 14:22 ` boyd, rounin
2004-05-20 20:43 ` vdharani
2004-05-20 18:18 ` boyd, rounin
2004-05-20 18:07 ` boyd, rounin
2004-05-20 18:20 ` rog
2004-05-20 23:34 ` Brantley Coile
2004-05-20 17:02 ` Rob Pike
2004-05-21 9:01 ` [9fans] first capital letter i Douglas A. Gwyn
2004-05-21 15:34 ` Rob Pike
2004-05-20 16:57 ` [9fans] first capital letter infunction names at man pages ¿why? matt lawless
2004-05-20 17:58 ` boyd, rounin
2004-05-20 18:09 ` Russ Cox
2004-05-20 18:42 [9fans] first capital letter in function names at man pages, why? rog
2004-05-20 19:21 ` Scott Schwartz
2004-05-20 20:07 ` boyd, rounin
2004-05-21 14:05 ` rog
2004-05-21 15:12 ` boyd, rounin
2004-05-21 16:25 ` rog
2004-05-21 0:36 dmr
2004-05-21 0:50 ` George Michaelson
2004-05-21 0:59 ` Rob Pike
2004-05-21 2:13 ` boyd, rounin
2004-05-21 5:33 ` Taj Khattra
2004-05-21 15:35 ` Anastasopoulos S
2004-05-21 16:02 ` boyd, rounin
2004-05-22 0:57 ` ron minnich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040521144426.GA2329@sigint.cs.purdue.edu \
--to=splite@purdue.edu \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).