Follow-up Comment #3, bug #32976 (project findutils): I don't really see these as being inconsistent; /some/path/some-basename is a path name, and the named file either exists or it doesn't.
The tests implemented by find (such as -iname) are essentially a query language allowing the user to specify which files they would like to see in the results. These are, in my conception of things at least, different concepts. If /foo/ is a case-insensitive file system, then surely "find /foo/BAR" and "find /foo/bar" should produce similar results. Identical in fact, apart from the case of "BAR" in the output. I believe this should already be happening (or am I wrong?). On the other hand, if /foo/ is a case-sensitive file system, /foo/BAR and /foo/bar are distinct names; zero, one or both of these files may exist, and find will corrrectly treat these as distinct. TL;DR: Start points are treated case-insensitively if they exist on a case-insensitive file system, and case-sentively if they exist on a case-sensitive file system. Did I misunderstand something? Please correct me if I did. _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?32976> _______________________________________________ Message sent via/by Savannah http://savannah.gnu.org/