From mboxrd@z Thu Jan  1 00:00:00 1970
Message-Id: <200206130229.g5D2TJJZ005791@orthanc.ab.ca>
From: Lyndon Nerenberg <lyndon@orthanc.ab.ca>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] bug or a feature?
In-reply-to: Your message of "Wed, 12 Jun 2002 16:49:21 PDT."
             <4109a95286b1ab5e60c5fff7b21cfa01@collyer.net>
Date: Wed, 12 Jun 2002 20:29:19 -0600
Topicbox-Message-UUID: ab4e7478-eaca-11e9-9e20-41e7f4b1d025

>>>>> "Geoff" == Geoff Collyer <geoff@collyer.net> writes:

    Geoff> I do think that the current behaviour is more helpful than
    Geoff> expanding to a null list would be.  If the pattern doesn't
    Geoff> match, you've very likely made a mistake.  I'd rather have
    Geoff> ``cat ?akefile'' print

    Geoff> 	cat: can't open ?akefile: '?akefile' directory entry not
    Geoff> found

    Geoff> and exit than have it just sit there reading standard input.

But shell globbing is a shell function, therefore the shell should
report non-matches. If you want the application to do the globbing (the
ls and tar examples) you should quote the arguments to protect them from
shell globbing. Or set noglob in the shells that support it.  The fact
that noglob exists says to me that the no-match pass-through globbing
behaviour has been found to be problematic in the past.

--lyndon