Bug/Feature in globbing

Article View: gnu.bash.bug

Article #301

#301

From: William W. Carlson
Date: Wed, 12 Jul 1989 13:22

13 lines
1014 bytes

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

Technical Details

Message-ID: <WWC.89Jul12082231@boole.ece.wisc.edu>

Path: arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!usc!polyslo!indri!engr!wwc

Show Full Headers

Complete Article Headers

Path: arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!usc!polyslo!indri!engr!wwc
From: wwc@boole.ece.wisc.edu (William W. Carlson)
Newsgroups: gnu.bash.bug
Subject: Bug/Feature in globbing
Message-ID: <WWC.89Jul12082231@boole.ece.wisc.edu>
Date: 12 Jul 89 13:22:31 GMT
Sender: news@engr.wisc.edu
Distribution: gnu
Organization: University of Wisconsin-Madison
Lines: 13