From: Eli Z. <el...@gn...> - 2012-07-07 08:52:23
|
> Date: Sat, 07 Jul 2012 09:08:00 +0200 > From: Erwin Waterlander <wat...@xs...> > > > find . -name \* > > > > You must escape the wildcard character just as you would in bash. > > Erwin, if this isn't working for you then please give us an example of > > what isn't working. > > > > Hi Earnie, > > Okay, with escaping it works. But I think that escaping and quoting is a > hassle for an average windows user. ?? But you are _supposed_ to quote wildcards where you need 'find' to get them unexpanded. > And for the 'find' command I see no use for the globbing. There are valid use cases when you'd want globbing. Here's a trivial example: find *.c -exec fgrep FOOBAR "{}" ";" > Globbing makes 'find' fail when the argument matches files in the > current directory. With unquoted wildcards, and in arguments to -name etc., yes. That's why you need to quote them. > I continue with Eli's port of findutils. Which already disables globbing where it is not needed, but still does glob in arguments where you'd want that. E.g., the above trivial example should work with my port. |