On 2002.11.03, Scott Goodwin <[EMAIL PROTECTED]> wrote: > > If you mean that all the ns_sock* commands are to be documented under > one ns_sock.n man page, I have to disagree. It breaks the unix standard > of one command per man page. I wouldn't know to look in ns_sock.n for > ns_sockopen; the user should not need to know what file a command is > defined in so they can look up the command. And when I want to see how > ns_sockopen works, I don't want ns_socklisten and the others on the same > page. I'd rather have the other related commands be in the "See Also" > section. > > I believe strongly that we should have one man page per API call, and > not one man page per file name.
Right. The traditional use of man pages is to type in: $ man <command> Such as "man accept" or "man ls" ... and have the accompanying or related call names in the "SEE ALSO" section. I agree with Scott here. -- Dossy -- Dossy Shiobara mail: [EMAIL PROTECTED] Panoptic Computer Network web: http://www.panoptic.com/ "He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on." (p. 70)
