From: fjh AT cs DOT mu DOT OZ DOT AU (Fergus Henderson)
Subject: Re: B20.1 bug: find is acting funny
4 Jan 1999 11:26:41 -0800
Message-ID: <19990104224927.49154.cygnus.gnu-win32@murlibobo.cs.mu.OZ.AU>
References: <000001be3792$9adb78a0$0c0aa8c0 AT harry DOT scoutsys DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
To: hughw AT scoutsys DOT com
Cc: gnu-win32 AT cygnus DOT com

On 03-Jan-1999, Hugh Winkler <hughw AT scoutsys DOT com> wrote:
> 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.

The behaviour you describe above is the proper behaviour;
you can observe the same on Linux, for example.
If beta 20.0 behaved differently, that was a bug in beta 20.0.

To get the behaviour that you want, you need to quote the "*.java" argument:

	find . -name "*.java"
	             ^      ^

-- 
Fergus Henderson <fjh AT cs DOT mu DOT oz DOT au>  |  "Binaries may die
WWW: <http://www.cs.mu.oz.au/~fjh>  |   but source code lives forever"
PGP: finger fjh AT 128 DOT 250 DOT 37 DOT 3        |     -- leaked Microsoft memo.
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".