[ale] weird "find" behavior

[lst at wiencko.net (List)]

Your shell is likely expanding * when not enclosed in quotes.  Depending 
on what shell, and numerous set and environment variables all kinds of 
strange things could be happening.

Best practice is to *always* quote wildcard characters (or any character 
the shell might expand/modify).

Tom

Jim Popovitch wrote:
> I'm seeing some find weirdness.  On both Ubuntu Etch and RH4ES, if I do
> the following I can locate files:
>
> 	find /usr/include/ -type f -name *.c
>
> But if I do this, I find nothing:
>
> 	find /usr/include/ -type f -name *.h
>
> However if I do this, I find files:
>
> 	find /usr/include/ -type f -name "*.h"
>
> WTF?
>
> -Jim P.
>
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> http://www.ale.org/mailman/listinfo/ale
>