Follow-up Comment #7, bug #42501 (group findutils):
Chronologically:
-regex added first to NetBSD (inspired from GNU's) in:
commit 5ddc160e898d16e1f981c5f3f7c8aa41db732ac4
Author: cgd <c...@netbsd.org>
Date: Tue Jul 20 01:28:41 1999 +0000
add -regex and -iregex primaries which, like GNU find's primaries of the
same name, match files' entire paths against regular expressions.
-regex is case sensitive, -iregex is case-insensitive. Note that these
primaries are _not_ entirely compatible with the GNU find primaries,
because their BREs appear to support alternation with \| whereas our BREs
do not. Also note there are no primaries which provide extended regular
expressions matching, though if they are desired they would be trivial
to implement.
FreeBSD added all of -E -regex -i{name,path,regex} at the same time in:
commit 7c1d4b3ae901ee2c7a3537b10db787464fb26df0
Author: Akinori MUSHA <k...@freebsd.org>
Date: Fri Feb 23 16:20:55 2001 +0000
Implement the following options and primaries:
-E Interpret regular expressions followed by -regex and -iregex
op-
tions as extended (modern) regular expressions rather than
basic
regular expressions (BRE's). The re_format(7) manual page
fully
describes both formats.
-iname pattern
Like -name, but the match is case insensitive.
-ipath pattern
Like -path, but the match is case insensitive.
-regex pattern
True if the whole path of the file matches pattern using
regular
expression. To match a file named ``./foo/xyzzy'', you can
use
the regular expression ``.*/[xyz]*'' or ``.*/foo/.*'', but
not
``xyzzy'' or ``/foo/''.
-iregex pattern
Like -regex, but the match is case insensitive.
These are meant to be compatible with other find(1) implementations
such as GNU's or NetBSD's except regexp library differences.
Reviewed by: sobomax, dcs, and some other people on -current
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?42501>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
