Read and respond to this message at:
https://sourceforge.net/projects/gnuwin32/forums/forum/74807/topic/1832242
By: feiyunw
I confirmed this bug on my Win 7 x64 machine.
Here is another example:
http://stackoverflow.com/questions/3995493/gnuwin32-find-exe-expands-wildcard-be
fore-performing-sear
Read and respond to this message at:
https://sourceforge.net/projects/gnuwin32/forums/forum/74807/topic/1832242
By: inkarkat
Same problem here, gnuwin32 find version 4.2.20. The problem (expanding the
wildcard using matches in the current dir, resulting in "Paths must precede
expression" error)
Read and respond to this message at:
https://sourceforge.net/forum/message.php?msg_id=4837862
By: jon_moore
I think I've seen the same thing. It looks like the gnuwin32 find 4.2.20 (my
version) is expanding the wildcard using matches in the current directory.
That gives the kind of errors gru
Read and respond to this message at:
https://sourceforge.net/forum/message.php?msg_id=4677182
By: gnuwin32
The examples you gave, all work fine on my system (MS-Windows XP SP2). For
example,
find . -iname "*n*"
lists all the files in the current directory and below with an n in their nam
Read and respond to this message at:
https://sourceforge.net/forum/message.php?msg_id=4675206
By: grumbled00k
Still no idea? ... gnuwin's find is completely useless when it's impossible
to search for files with a certain extension ...
Read and respond to this message at:
https://sourceforge.net/forum/message.php?msg_id=4542194
By: grumbled00k
Any path, like "." or "C:\users\user\documents".
Try searching for "*nnn*", "*nn*" or "*n*" in the default path (".").
Only "*n*" gives the error.
_
Read and respond to this message at:
https://sourceforge.net/forum/message.php?msg_id=4538659
By: wwp
What's the exact value of "path" in your examples?
__
You are receiving this email because you elected to monitor this forum