Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!shelby!agate!ucbvax!tut.cis.ohio-state.edu!AUREL.CALTECH.EDU!bfox
From: bfox@AUREL.CALTECH.EDU (Brian Fox)
Newsgroups: gnu.bash.bug
Subject: Bug/Feature in globbing
Message-ID: <8907121829.AA02468@aurel.caltech.edu>
Date: 12 Jul 89 18:29:28 GMT
References: <WWC.89Jul12082231@boole.ece.wisc.edu>
Sender: daemon@tut.cis.ohio-state.edu
Reply-To: bfox@aurel.caltech.edu
Distribution: gnu
Organization: GNUs Not Usenet
Lines: 25


   Date: 12 Jul 89 13:22:31 GMT
   From: cica!ctrsol!sdsu!polyslo!indri!engr!wwc@cis.ohio-state.edu  (William W. Carlson)
   Organization: University of Wisconsin-Madison
   Sender: bug-bash-request@prep.ai.mit.edu


   I really like bash a great deal, but one "feature" I find quite
   annoying.  Whenever globbing fails (i.e. no match), it leaves the
   unglobbed string as is.  (i.e. if I type "ls foo* bar*" and there is a
   file in the current directory called foo.c but none starting with
   "bar", ls gets passed "ls foo.c bar*" and of course says "bar* not
   found."  This feature is particularly disturbing in aliases.
   Do people think this is a "bug" or a "feature"?  If it is a bug, I'd
   really like it fixed.  If it is a feature, I'd like for there to be
   some way (perhaps set -no_bogus_globbing) to disable it.

   Bill Carlson
   wwc@engr.wisc.edu

Well, this was a design decision.  I think that it is the best of
possible alternatives.  Would you like to present an alternative that
you feel is better?

Brian