From owner-freebsd-current Fri Mar 3 12: 5: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from wopr.caltech.edu (wopr.caltech.edu [131.215.240.222]) by hub.freebsd.org (Postfix) with ESMTP id 4A83837B64E for ; Fri, 3 Mar 2000 12:05:05 -0800 (PST) (envelope-from mph@wopr.caltech.edu) Received: (from mph@localhost) by wopr.caltech.edu (8.9.3/8.9.1) id MAA56921; Fri, 3 Mar 2000 12:04:42 -0800 (PST) (envelope-from mph) Date: Fri, 3 Mar 2000 12:04:41 -0800 From: Matthew Hunt To: Garance A Drosihn Cc: Laurence Berland , Chuck Robey , Alfred Perlstein , Dan Papasian , current@FreeBSD.ORG Subject: Re: which(1), rewritten in C? Message-ID: <20000303120441.A56070@wopr.caltech.edu> References: <38BF334F.2F10D4B0@confusion.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from drosih@rpi.edu on Fri, Mar 03, 2000 at 11:13:23AM -0500 Approved: graham.spanier Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Mar 03, 2000 at 11:13:23AM -0500, Garance A Drosihn wrote: > If you do a 'type -a which' or 'help which' in bash, you'll find that > 'which' is not a built-in function in bash either. Sh/bash people > would be more likely to use 'type blah' or 'type -a blah' instead > of 'which blah'. For what little it's worth, I'm a bash user and always use "which". Probably because half the time, it's in backquotes: $ less `which which` and the "type" builtin is too verbose, saying "which is hashed (/usr/bin/which)." (It seems "type -p which" will do what I want, but it's easier to type "which which", especially since that is my habit already.) As I have a slow machine by modern standards, I'm all for a faster which(1) as well. -- Matthew Hunt * Stay close to the Vorlon. http://www.pobox.com/~mph/ * To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message