Subject: B20.1 bug: find is acting funny
From: [email-masked] (Hugh Winkler)

4 Jan 1999 01:38:21 -0800
Message-ID: <[email-masked]>
Reply-To: <[email-masked]>
Mime-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
To: <[email-masked]>

In b20.1 (bash 2.02.1(2), find 4.1) if I do
    find ./ -name *.java

and there are some .java files in the current directory, find emits

	find: paths must precede expression
	Usage: find [path...] [expression]

but if there are no .java files in the current directory, find behaves as
expected.

Same behavior for any search pattern, not just .java, of course.

find was working properly in 20.0 I'm pretty sure.

Hugh Winkler
Scout Systems, Inc.

-
For help on using this list (especially unsubscribing), send a message to
"[email-masked]" with one line of text: "help".