🚀 go-pugleaf

In article <8911142325.AA01114@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.

In article <JBW.89Nov14224054@bucsf.bu.edu> (Joe Wells) writes:
   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".

In article <8911151705.AA03733@aurel.cns.caltech.edu.> (Brian Fox) writes:
   If you want to use disk commands, you can disable all of the shell
   builtins that you don't want to use with the "enable -n" command.

Unfortunately, this is hard when the name of the executable file is not
known beforehand, but is instead taken from the input or the environment. 

After thinking about this, I realized that a more useful command would be
one like "type -path foo", except that it would return the full pathname
of the executable file named "foo" that would be executed, *if there were
no builtins, aliases, or functions named "foo"*, and would return nothing
if there were no such executable file in the user's path.  This is
a cross between the current semantics of "type -path foo" and "type -all
-path foo".

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