From: corinna.vinschen@cityweb.de (Corinna Vinschen)
Subject: Re: B20.1 bug: find is acting funny
5 Jan 1999 05:27:30 -0800
Message-ID: <3690EC6E.32A8EAE.cygnus.gnu-win32@cityweb.de>
References: <000001be3792$9adb78a0$0c0aa8c0@harry.scoutsys.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: hughw@scoutsys.com, gnu-win32@cygnus.com

Hugh Winkler 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.

If you use wildcards, which should be expanded by find, _not_ by the shell,
but by find, you should quote them:

	find . -name '*.java' -print

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

I bet, only with quoted wildcards, too.

Regards,
Corinna

-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".