Subject: re: `find' command broken.
From: [email-masked] (James Dumser)

11 Jul 1997 13:46:07 -0700
Approved: [email-masked]
Distribution: cygnus
Message-ID: <[email-masked]>
Reply-To: James Dumser <[email-masked]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7Bit
X-Mailer: BeyondMail for Windows/Professional 2.3
Original-To: [email-masked]
X-BeyondMail-Priority: 1
Conversation-ID: <19970711092719531.AAA303@TENDLE>
In-Reply-To: <19970711092719531.AAA303@TENDLE>
Original-Cc: [email-masked]
X-Receipt-From-Agent: true
Original-Sender: [email-masked]

On Fri, 11 Jul 1997 10:27, John Cooper <[email-masked]> 
  wrote:
>Since cmd.exe doesn't do any globbing, the following should presumably 
>work:
>
>    H:\ef>find . -name *.c -print
>    find: paths must precede expression
>    Usage: find [path...] [expression]
>    H:\ef>

And the fact that cmd does not glob is the "problem": bash globs; but 
since cmd doesn't, cygwin32 globs for it (because Unix programs expect 
globbing to be done). 
  
>Oddly, this does work under bash.  Can anyone explain this?

This will work under bash IFF there are no .c files in the current 
directory (bash tries to glob; but since there are no matches, it leaves
it alone) -- in which case, running under cmd should have the same 
results). Did you run your tests (cmd vs bash) from the same directory?

The correct syntax should be
	find . -name '*.c' -print

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