Find's -regex matches the entire path, not just the file name. That means that to find /path/to/foo, you need -regex '.*foo', and not just foo`. You want something like:

find  . -E -regex ".*[a-z][A-Z].*"

It would be much simpler to use globs and the simpler -name as suggested by SYN, however, instead of regexes.

Find's -regex matches the entire path, not just the file name. That means that to find /path/to/foo, you need -regex '.*foo', and not just foo`. You want something like:

find  . -E -regex ".*[a-z][A-Z].*"

It would be much simpler to use globs and the simpler -name as suggested by SYN, however, instead of regexes.

There are two issues here. First, find's -regex matches the entire path, not just the file name. That means that to find /path/to/foo, you need -regex '.*foo', and not just foo`. Second, you can't use capture groups (what would be the point, you can't refer to them anywhere) so the parenthese are taken literally. You want something like:

find  . -E -regex ".*[a-z][A-Z].*"

It would be much simpler to use globs and the simpler -name as suggested by SYN, however, instead of regexes.

Find's -regex matches the entire path, not just the file name. That means that to find /path/to/foo, you need -regex '.*foo', and not just foo`. You want something like:

find  . -E -regex ".*[a-z][A-Z].*"

It would be much simpler to use globs and the simpler -name as suggested by SYN, however, instead of regexes.