Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!shelby!apple!gem.mps.ohio-state.edu!tut.cis.ohio-state.edu!AUREL.CNS.CALTECH.EDU!bfox From: bfox@AUREL.CNS.CALTECH.EDU (Brian Fox) Newsgroups: gnu.bash.bug Subject: Request for enhancement Message-ID: <8911151705.AA03733@aurel.cns.caltech.edu.> Date: 15 Nov 89 17:05:07 GMT References: Sender: daemon@tut.cis.ohio-state.edu Reply-To: bfox@aurel.cns.caltech.edu Distribution: gnu Organization: GNUs Not Usenet Lines: 26 Date: 15 Nov 89 03:40:54 GMT From: bucsb!bucsf!jbw@cs.bu.edu (Joe Wells) Organization: Boston University Computer Science Department References: <891@cwjcc.CWRU.Edu>, <8911142325.AA01114@aurel.cns.caltech.edu.> Sender: bug-bash-request@prep.ai.mit.edu 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". For the most part, shell scripts do not care if the command that they are executing is a builtin or on disk, they only care that it isn't a functin or alias. 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. Brian