From owner-freebsd-current  Mon Feb 10 05:16:50 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id FAA01759
          for current-outgoing; Mon, 10 Feb 1997 05:16:50 -0800 (PST)
Received: from lundin.abq.nm.us. (lundin.abq.nm.us [198.59.115.228])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA01754
          for <freebsd-current@freefall.freebsd.org>; Mon, 10 Feb 1997 05:16:44 -0800 (PST)
Received: (from aflundi@localhost) by lundin.abq.nm.us. (8.7.5/8.7.3) id FAA28352 for freebsd-current@freefall.freebsd.org; Mon, 10 Feb 1997 05:56:32 -0700 (MST)
Date: Mon, 10 Feb 1997 05:56:32 -0700 (MST)
From: Alan Lundin <aflundi@lundin.abq.nm.us>
Message-Id: <199702101256.FAA28352@lundin.abq.nm.us.>
In-Reply-To: Nate Williams <nate@mt.sri.com>
       "Re: 3.0-970124-SNAP: man page search order" (Feb  9,  2:40pm)
X-Mailer: Mail User's Shell (7.2.5 10/14/92)
To: freebsd-current@freefall.freebsd.org
Subject: Re: 3.0-970124-SNAP: man page search order
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>   static char *std_sections[] = 
>     {
>        "1", "n", "l", "6", "8", "2", "3", "4", "5", "7", "9", "p", "o", NULL
>     };

Is there something sacred about one letter section
names?  It seems to me that if we create a "p"
section for perl, then when we decide that python
ought to also be included, we're out of name space.
I guess I'd like to see complex systems like tcl
or perl have there own spelled out name:

  static char *std_sections[] = 
    {
       "1", "n", "l", "6", "8", "2", "3", "4", "5", "7", "9",
       "perl", "tcl", "o", NULL
    };

and perhaps all the *.1's, *.3's, *.5's could be
mixed together under the spelled out section.  This
way you'd get the man page by saying

    $ man tcl set
    $ man perl socket

Seems fairly natural to me.  At least it beats

    $ MANPATH=/usr/local/lib/tcl man incr

that I do now on my Sun systems.  :-)

--alan