Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site fortune.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxl!ihnp4!fortune!rpw3
From: rpw3@fortune.UUCP
Newsgroups: net.unix
Subject: Re: An odd difference between 'cat file' - (nf)
Message-ID: <3068@fortune.UUCP>
Date: Sun, 15-Apr-84 07:05:49 EST
Article-I.D.: fortune.3068
Posted: Sun Apr 15 07:05:49 1984
Date-Received: Tue, 17-Apr-84 06:43:19 EST
Sender: notes@fortune.UUCP
Organization: Fortune Systems, Redwood City, CA
Lines: 22

#R:opus:-36700:fortune:26900045:000:799
fortune!rpw3    Apr 15 03:30:00 1984

This IS odd. I just tried it on 4.1bsd, and the same thing: "cannot open".
I also am a lazy typist, and when I know that a file exists, and there is
a unique path to it, I do as you do, for example:

	fi*/ne*/art*/*info == file/net/articles/terminfo

'csh' (4.1bsd) ALLOWS "foo <fi*/ne*/art*/*info", 'sh' (4.1) doesn't. (If the
expansion is not unique, 'csh' says: "Ambiguous". I can dig it. It would be
asking a bit much for it to turn "foo <bar*" into "cat bar* | foo".  ;-} )

This is weird since (as you note) 'sh' DOES allow "cd fi*/ne*/art*".
Therefore it MUST have a "ExpandUnique" (or some such) in it somewhere...

Rob Warnock

UUCP:	{ihnp4,ucbvax!amd70,hpda,harpo,sri-unix,allegra}!fortune!rpw3
DDD:	(415)595-8444
USPS:	Fortune Systems Corp, 101 Twin Dolphin Drive, Redwood City, CA 94065