Update of bug #56823 (project findutils):
Severity: 3 - Normal => 2 - Minor
Status: None => Invalid
Assigned to: None => jay
_______________________________________________________
Follow-up Comment #1:
Well if we look at the "Finding Files" manual we see that -regex is described
like this:
@deffn Test -regex expr
@deffnx Test -iregex expr
True if the entire file name matches regular expression @var{expr}.
This is a match on the whole path, not a search. For example, to
[...]
Similarly, in the manual page:
-regex pattern
File name matches regular expression pattern. This is a match on the whole
path, not a search. For example, to
[...]
The description of the -regextype option specifically states that it affects
only the regular expression syntax understood:
@deffn Option -regextype name
This option controls the variety of regular expression syntax
understood by the @samp{-regex} and @samp{-iregex} tests.
The manpage is worded somewhat similarly:
-regextype type
Changes the regular expression syntax understood by -regex and -iregex
tests which occur later on the command line. To see which regular expression
types are known, use -regextype help. The Texinfo documentation (see SEE
ALSO) explains the meaning of and differences between the various types of
regular expression.
It's difficult then to see how such a confusion can arise.
If there is a specific change to the documentation that you think would avoid
confusion, I'd be happy to consider a patch you'd like to send.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?56823>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
