From owner-freebsd-current Sun Feb 9 10:32:37 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id KAA28421 for current-outgoing; Sun, 9 Feb 1997 10:32:37 -0800 (PST) Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id KAA28411 for ; Sun, 9 Feb 1997 10:32:31 -0800 (PST) Received: by halloran-eldar.lcs.mit.edu; (5.65v3.2/1.1.8.2/19Aug95-0530PM) id AA06685; Sun, 9 Feb 1997 13:32:20 -0500 Date: Sun, 9 Feb 1997 13:32:20 -0500 From: Garrett Wollman Message-Id: <9702091832.AA06685@halloran-eldar.lcs.mit.edu> To: Robert N Watson Cc: freebsd-current@freefall.FreeBSD.org Subject: 3.0-970124-SNAP: man page search order In-Reply-To: <8mzBYNO00YVp0P4FIt@andrew.cmu.edu> References: <8mzBYNO00YVp0P4FIt@andrew.cmu.edu> Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk < said: > 2. The real thing is this. The man page search order finds all of the c > programming calls after the TCL ones, so "man bind" returns TCL's bind, > not the syscall bind. This is inconvenient if one is a C programmer not > a TCL programmer. I assume I can fix this with /etc/manpath.config, but > this doesn't seem like the right default setting? I would as soon all the Tcl crap were squirreled away in another directory where I don't have to look at it, ever. If I want to know how a Tcl command works, I read The Book, not look at a badly-formatted man page. If there were one Tcl man page that explained all the basics, like the perl4 man page, then it might actually be useful. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, ANA, or NSA| - Susan Aglukark and Chad Irschick