I have to disagree with you. Good English expression is not mutually
exclusive with good coding. I think some IT people love the arcane because
it's a kind of latter day freemasonry... secret acronyms instead of
handshakes. Here is a simple example of how it SHOULD be done. Clear and
precise followed by docs on the switches, as required.
********************************
[david@data david]$ man ftp
FTP(1) System Reference Manual
FTP(1)
NAME
ftp - Internet file transfer program
SYNOPSIS
ftp [-pinegvd] [host]
pftp [-inegvd] [host]
DESCRIPTION
Ftp is the user interface to the Internet standard File Transfer
Protocol. The program allows a user to transfer files to and from a
remote network site.
********************************
BTW... if you think this is not relevant to linux, you've been an expert
for too long ;-) Try being part time, and having to figure things out.
Surely linux isn't just for the professional?
On Sat, 23 Mar 2002, Jeff Waugh wrote:
> man pages are for *reference*, not for detailed documentation. You should
> be able to find detailed documentation in -doc packages, or in
> /usr/share/doc.
>
> man pages are meant for, "hmm, what's that switch?" rather than, "hmm, what
> the bollocks is this?"
--
SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/
More Info: http://lists.slug.org.au/listinfo/slug
