Mail Archives: cygwin/1997/10/21/18:57:05
I suspect you are using the wrong 'find'. For example, i found myself
inadvertently using the NT flavor of find instead of the bash flavor...turns
out my PATH had /WINNT/systemm32 prior to /gnuwin32/../bin.
I created the following alias to combat this:
alias f='//D/gnuwin32/b18/H-i386-cygwin32/bin/find.exe'
John Gibb
(415)-584-3754
jgibb1 AT ix DOT netcom DOT com
-----Original Message-----
From: GBradfor <GBradfor AT fhssmtp DOT redstone DOT army DOT mil>
To: gnu-win32 AT cygnus DOT com <gnu-win32 AT cygnus DOT com>
Date: Tuesday, October 21, 1997 5:35 PM
Subject: Elementary Problem with find
> This is, more than likely, a true newbie problem. I've searched the
> back issues of the mailing list, and there are no other reports of
> this problem. So, it's probably just me; but just in case...
>
> find is failing to take valid command strings. I am running b18 under
> Windows95.
>
> Example case:
> find . -name *.c -print
>
> The cygwin32 version gives the following error:
> FIND: Parameter format not correct
>
> Running this same command on my Linux box gives the appropriate file
> listing.
>
> I have also tried variations on this same theme:
> find <absolute path name (with both '\' and '/')> -name *.c -print
> find -name *.c -print /* no starting pathname; use present */
> /* directory as default. */
> find . -name "*.c" -print
> find . -name '*.c' -print
>
> The most interesting was:
> find "<absolute pathname>" -name *.c -print
> find ignored what was in quotes and interpretted everything else as
> search paths.
>
> Any suggestions on this?
>
> /s/
> Pat Bradford
>
> Reply to:
> gbradfor AT redstone DOT army DOT mil
> AND/OR
> p_n_brad AT traveller DOT com
>-
>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".
>
-
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 -