From:	John DOT Cooper AT digitivity DOT com ("John Cooper")
Subject:	`find' command broken.
11 Jul 1997 03:38:51 -0700 :
Approved:	cygnus DOT gnu-win32 AT cygnus DOT com
Distribution:	cygnus
Message-ID:	<19970711092719531.AAA303.cygnus.gnu-win32@TENDLE>
Reply-To:	john DOT cooper AT digitivity DOT com
Mime-Version:	1.0
Original-To:	GNU-Win32 AT cygnus DOT com
Original-Cc:	Amol Deshpande <amold AT microsoft DOT com>, john DOT cooper AT digitivity DOT com
X-Mailer:	VM 6.32 under Emacs 19.34.1
X-Attribution:	JSC
X-Face:	-%]aecOJlhOSKn)}>~DbRQwM6G6gDkOD{2f!2Bt9|S-xC1~Gk^dCp_/HH#zo^u5z8iGty3N
	L_1.GYkj0by`^VQK14EzbsY~BC%%O#x+[Giaf?X`hi9H)oEy]M>cx/Y4.I^5@^#kQrJk*!DwlpX: 1}
	eZVU9: ~_QGIMF5[I
Original-Sender:	owner-gnu-win32 AT cygnus DOT com

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>

I'm actually using the early zsh release, and get the same result when I run
`find . -name *.c -print' .

Oddly, this does work under bash.  Can anyone explain this?

Thanks,

    --- John

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