Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!wuarchive!uunet!shelby!agate!usenet.ins.cwru.edu!odin!chet
From: chet@odin.INS.CWRU.Edu (Chet Ramey)
Newsgroups: comp.unix.shell
Subject: Re: Dot in PATH?
Message-ID: <1991Feb7.191136.20649@usenet.ins.cwru.edu>
Date: 7 Feb 91 19:11:36 GMT
References: <1991Feb6.084135.11456@wpi.WPI.EDU> <1991Feb6.154106.7067@usenet.ins.cwru.edu> <2905@charon.cwi.nl>
Sender: news@usenet.ins.cwru.edu
Reply-To: chet@po.CWRU.Edu
Distribution: comp
Organization: Case Western Reserve Univ. Cleveland, Ohio, (USA)
Lines: 22
Nntp-Posting-Host: odin.ins.cwru.edu

In article <2905@charon.cwi.nl> dik@cwi.nl (Dik T. Winter) writes:
>In article <1991Feb6.154106.7067@usenet.ins.cwru.edu> chet@po.CWRU.Edu writes:
> > odin$ which foo
> > bash: which: command not found
> > odin$ foo
> > this is ./foo
> > 
>It is very tempting to give some nasty comment here.

Go for it.  I have thick skin.

Note that `which' is not a shell function or builtin, nor is it an
executable in `.' or `/usr/bin'.  It is an executable in a private
bin directory.

Chet
-- 
Chet Ramey				``There's just no surf in
Network Services Group			  Cleveland, U.S.A. ...''
Case Western Reserve University
chet@ins.CWRU.Edu		My opinions are just those, and mine alone.