Date: Mon, 10 Feb 1997 05:56:32 -0700 (MST) From: Alan Lundin <aflundi@lundin.abq.nm.us> To: freebsd-current@freefall.freebsd.org Subject: Re: 3.0-970124-SNAP: man page search order 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)
next in thread | previous in thread | raw e-mail | index | archive | help
> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199702101256.FAA28352>