Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!ucsd!usc!samsung!uunet!bu-cs!bucsb!bucsf!jbw
From: jbw@bucsf.bu.edu (Joe Wells)
Newsgroups: gnu.bash.bug
Subject: Re: Request for enhancement
Message-ID: <JBW.89Nov14224054@bucsf.bu.edu>
Date: 15 Nov 89 03:40:54 GMT
References: <891@cwjcc.CWRU.Edu> <8911142325.AA01114@aurel.cns.caltech.edu.>
Distribution: gnu
Organization: Boston University Computer Science Department
Lines: 15
In-reply-to: bfox@AUREL.CNS.CALTECH.EDU's message of 14 Nov 89 23:25:28 GMT

In article <8911142325.AA01114@aurel.cns.caltech.edu.> bfox@AUREL.CNS.CALTECH.EDU (Brian Fox) writes:

   Bash will have a "command" builtin in 1.05.  "command" is useful for
   builtins or disk commands.  It means to ignore aliases and functions
   when searching for the command.

How about a "command" builtin that only executes programs in your path,
since "builtin" already exists for running builtin commands.

Thus, "builtin command foo" would always run program "foo".

-- 
Joe Wells <jbw@bucsf.bu.edu>
jbw%bucsf.bu.edu@bu-it.bu.edu
...!harvard!bu-cs!bucsf!jbw