Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10 5/3/83 based; site houxj.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxl!houxm!houxj!wapd
From: wapd@houxj.UUCP (Bill Dietrich)
Newsgroups: net.unix
Subject: Re: An odd difference between 'cat file' - (nf)
Message-ID: <348@houxj.UUCP>
Date: Mon, 16-Apr-84 17:51:15 EST
Article-I.D.: houxj.348
Posted: Mon Apr 16 17:51:15 1984
Date-Received: Tue, 17-Apr-84 07:32:15 EST
References: <3068@fortune.UUCP>
Organization: AT&T Bell Labs, Holmdel NJ
Lines: 17


	I filed an MR to the BTL Unix maintainers a long
time ago about this (not expanding wildcards after '<' and '>').
I was told that the reason was that this could easily lead
to unintentional arguments :
	cat abc def >>x*
expanding to :
	cat abc def >>x1 x2 x3 x4
which would be bad.

	My response was that not only is wildcarding dangerous
in the current state (rm -fr x*), but there are cases where
the shell silently ignores weird expansions (cd x*).  They
were unmoved.

					Bill Dietrich
					houxj!wapd