find -delete .. Do What I Mean?

[Matthijs De Smedt]

I have an issue with the way find handles its arguments. Perhaps this has
been discussed before, but I couldn't find it.

Today I wanted to remove some files from a directory tree using find. I
viewed the list of files to remove using "find -iname *-1*.jpg". Then I
wanted to delete them using "find -delete -iname *-1*.jpg".

With all other tools I use, I'm used to indifference of the order of the
arguments. In find's case, placing -delete before -iname happily deletes
every file and folder below the current directory. Without warning or
confirmation. Even if this is not a bug, this clearly does not follow the
"Do What I Mean" principle.

I would like to know if this can be submitted as a bug. And if not, why this
behavior was chosen.

Matthijs De Smedt