On 03/19/2010 07:51 AM, Andreas Schwab wrote:
> Eric Blake <[email protected]> writes:
> 
>> On 03/17/2010 04:14 PM, Andreas Schwab wrote:
>>> Paul Gerber <[email protected]> writes:
>>>
>>>>> /bin/ls: No match
>>>
>>> That message comes from the shell (csh or tcsh).
>>
>> Or bash, if you turn on the non-default failglob option (which exists to
>> match the non-POSIXy behavior of csh).
> 
> No, bash would print this:
> 
> bash: no match: *.pdb.Z

That's one place where bash is nicer than tcsh - the error message is
accurate in telling which program had no match (it was the shell;
execution of ls was refused), whereas tcsh's implies that ls got a
chance to run, even though it did not.

But I'm biased - I hate the csh family of shells, because they are just
too hard to script with.

-- 
Eric Blake   [email protected]    +1-801-349-2682
Libvirt virtualization library http://libvirt.org

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to