From:	hughw AT scoutsys DOT com (Hugh Winkler)
Subject:	RE: B20.1 bug: find is acting funny
5 Jan 1999 00:51:37 -0800 :
Message-ID:	<000601be3812$a35e0fd0$0c0aa8c0.cygnus.gnu-win32@harry.scoutsys.com>
References:	<179AA48D1741D211821700805FFE241873CA8D AT HQMAIL02>
Reply-To:	<hughw AT scoutsys DOT com>
Mime-Version:	1.0
To:	<gnu-win32 AT cygnus DOT com>

Thanks fellows,

You're both correct, it's my usage that's incorrect. I found the same
behavior on a bash running on a BSD system.

I'm still a little mystified that I don't need the escape or the quotes if
there are no matching files in the directory; I wonder what argv[3] is in
that case. I guess it must be "*.java". Interesting.


Hugh Winkler
Scout Systems, Inc.

> -----Original Message-----
> From: Kevin Schnitzius [mailto:kevins AT citrix DOT com]
> How does bash do file name matching on '*'?
> What does 'echo *.java' produce in that directory?
> Shouldn't your find command be 'find ./ -name \*.java'?
>

> -----Original Message-----
> From: oe AT port DOT de [mailto:oe AT port DOT de]
> If yo use find with file name globbing you shoud be shure
> that the shell doesn't it before
> So you have to say
>
> $ find ./ -name "*.java"
>
>

-
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".

- Raw text -