From owner-freebsd-current Sun Feb 9 13:41:01 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA11086 for current-outgoing; Sun, 9 Feb 1997 13:41:01 -0800 (PST) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA11081 for ; Sun, 9 Feb 1997 13:40:57 -0800 (PST) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id OAA06585; Sun, 9 Feb 1997 14:40:49 -0700 (MST) Date: Sun, 9 Feb 1997 14:40:49 -0700 (MST) Message-Id: <199702092140.OAA06585@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Cc: freebsd-current@freefall.freebsd.org Subject: Re: 3.0-970124-SNAP: man page search order In-Reply-To: References: <9632.855479839@critter.dk.tfs.com> 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 > }; > > (It can be overridden by a MANSEC variable, btw.) > > Now comes the difficult part: what's the best order? > > static char *std_sections[] = > { > "1", "8", "2", "3", "n", "4", "5", "6", "7", "9", "l", NULL > }; This works for me. But, it leans toward programmer/admin types, which some may disagree with. My gut feeling is 'commit that puppy'. :) Nate