From mboxrd@z Thu Jan  1 00:00:00 1970
Subject: Re: [9fans] bug or a feature?
From: Pavel Mihaylov <bin@bash.info>
To: 9fans@cse.psu.edu
In-Reply-To: <4109a95286b1ab5e60c5fff7b21cfa01@collyer.net>
References: <4109a95286b1ab5e60c5fff7b21cfa01@collyer.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Message-Id: <1023928314.963.12.camel@dator>
Mime-Version: 1.0
Date: Thu, 13 Jun 2002 03:31:53 +0300
Topicbox-Message-UUID: ab375432-eaca-11e9-9e20-41e7f4b1d025

=D0=9D=D0=B0 13 =D1=8E=D0=BD=D0=B8 2002 =D0=B3. (=D1=87=D0=B5=D1=82=D0=B2=
=D1=8A=D1=80=D1=82=D1=8A=D0=BA), =D0=B2 2.49 =D1=87=D0=B0=D1=81=D0=B0, Geof=
f Collyer =D0=BF=D0=B8=D1=81=D0=B0:
>=20
> I do think that the current behaviour is more helpful than expanding
> to a null list would be.  If the pattern doesn't match, you've very likel=
y
> made a mistake.  I'd rather have ``cat ?akefile'' print
>=20
> 	cat: can't open ?akefile: '?akefile' directory entry not found
>=20
> and exit than have it just sit there reading standard input.
>=20

I just played with some common shells, the behavior of zsh (my choice in
Unix world) and csh seems to solve your case.

% echo nonex?
zsh: no matches found: nonex?
% bash
$ echo nonex?
nonex?
$ csh
> echo nonex?
echo: No match.
> ksh
$ echo nonex?
nonex?