Subject: Re: B20.1 bug: find is acting funny
From: [email-masked] (Earnie Boyd)

5 Jan 1999 20:46:03 -0800
Message-ID: <[email-masked]>
Reply-To: [email-masked]
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
To: [email-masked], [email-masked]

---Hugh Winkler <[email-masked]> 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.
> 
> 

`find' has always given this for this pattern.  The problem is where
the file globbing happens.  To execute this correctly you must quote
the * in the pattern so that the * is actual input to find.  E.G.:

find . -name \*.java

or 

find . -iname \*.java  ;# to ignore case of filename.
==
-                        \\||//
-------------------o0O0--Earnie--0O0o-------------------
--                [email-masked]               --
-- http://www.freeyellow.com/members5/gw32/index.html --
----------------------ooo0O--O0ooo----------------------

PS: Newbie's, you should visit my page.
_________________________________________________________
DO YOU YAHOO!?
Get your free @yahoo.com address at http://mail.yahoo.com

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