Not necessarily a bug, more of a 'feature'

the combination of 'bash' and 'find' works a little differently with this new release.

In 4.4 i could enter this find command and get the expected result:

tying the same on a 4.6 machine yields:

Instead i must escape the "*" like this


why is it like this?

This breaks some of my scripts 

Your scripts were already broken .  The shell expands *.new to a list of matching filenames, then find cries because it expected only one pattern after -name (unless there was only one match anyway). You can get the output of your first example if you turn off the shell globbing: set -o noglob

Maybe you did this before?

Quoting as "*.new" is better, because explicit beats implicit (or indeed, escape the special characters).

My 4.4 is no different to snapshot in this:


cheers  ...  markc

pedantic  point, but -print is the default option and you don't need to type it.  I'm incredibly lazy so I don't type anything I don't have to

I decide that   

They work in sco unix though 

I suppose i could concur... escaping IS backwards-compatible ...



i've been doing it like that for 11 years now, and i'm too lazy to re-learn 
I work with several flavors of unix + linux daily, so i tend to learn commands in a way that work for all. I don't remember where 'find' does not have -print as default, but there must be somewhere 


Edit :
The reason i discovered this is that i happened to be executing find in a directory where there were matching files, i (and many, many more, i trust) normally use ls to find files in a directory 

it took me a while to get out of the habit of typing:

gunzip -c | tar xvf -

:-)

don't laugh, i still do that... It is even worse the other way around, when you are on some AIX system and can't figure out why 'tar -xvfz arcanoid.tar.gz ' won't work