From: dumser@ti.com (James Dumser) Subject: re: `find' command broken. 11 Jul 1997 13:46:07 -0700 Approved: cygnus.gnu-win32@cygnus.com Distribution: cygnus Message-ID: Reply-To: James Dumser 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: john.cooper@digitivity.com X-BeyondMail-Priority: 1 Conversation-ID: <19970711092719531.AAA303@TENDLE> In-Reply-To: <19970711092719531.AAA303@TENDLE> Original-Cc: GNU-Win32@cygnus.com X-Receipt-From-Agent: true Original-Sender: owner-gnu-win32@cygnus.com On Fri, 11 Jul 1997 10:27, John Cooper 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 dumser@ti.com - For help on using this list (especially unsubscribing), send a message to "gnu-win32-request@cygnus.com" with one line of text: "help".