From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19651 invoked from network); 28 Mar 1998 04:31:10 -0000 Received: from math.gatech.edu (list@130.207.146.50) by ns1.primenet.com.au with SMTP; 28 Mar 1998 04:31:10 -0000 Received: (from list@localhost) by math.gatech.edu (8.8.5/8.8.5) id XAA18007; Fri, 27 Mar 1998 23:28:20 -0500 (EST) Resent-Date: Fri, 27 Mar 1998 23:28:20 -0500 (EST) Message-Id: <199803280428.XAA20390@cypress.math.gatech.edu> To: zsh-workers@math.gatech.edu Subject: Re: default command function In-Reply-To: Your message of "Thu, 26 Mar 1998 11:07:25 GMT." <199803261107.LAA32378@diamond.tao.co.uk> Date: Fri, 27 Mar 1998 23:28:16 -0500 From: Richard Coleman Resent-Message-ID: <"JpdBl.0.IP4.Zn77r"@math> Resent-From: zsh-workers@math.gatech.edu X-Mailing-List: archive/latest/3821 X-Loop: zsh-workers@math.gatech.edu Precedence: list Resent-Sender: zsh-workers-request@math.gatech.edu > Perhaps the command search order (builtin, function, external command, > ...) could go into a shell parameter, making `builtin' and `command' > just special cases of this more general facility. (I think this > sort of feature was first suggested to me by Richard, and I have > recently implemented it, in a very general form, in a shell I wrote > for a non-Unix OS.) When I was maintainer, I spent a couple weeks working on this idea, and eventually threw all the code away. It just got too hackish. If you could make this work, it would be great. As part of this, I wanted to merge the command search code with the where/whence/type builtin. There are several different places where zsh goes searching for a command. -- Richard Coleman coleman@math.gatech.edu