Re: [bug #65297] -regexp incompatible statements concerning default
James Youngman <[email protected]>
| Newsgroups | gmane.comp.gnu.findutils.bugs |
|---|---|
| Message-ID | <CAGwX767PAWCPNVZZK9UxX0DkBUPHwSnGfsmzSzaz5-vzagSnqw@mail.gmail.com> |
Fixed with this patch. On Fri, May 17, 2024 at 9:31 AM James Youngman <[email protected]> wrote: > Update of bug #65297 (group findutils): > > Status: None => Fixed > > > _______________________________________________________ > > Follow-up Comment #2: > > Fixed in git. > > > _______________________________________________________ > > Reply to this item at: > > <https://savannah.gnu.org/bugs/?65297> > > _______________________________________________ > Message sent via Savannah > https://savannah.gnu.org/ > >
0001-doc-Explain-that-find-defaults-to-GNU-Emacs-regexes.patch
(text/x-patch, 2.5 KB)
From 0582f8057e70a99b4caff4cb2aa5e5fffde3f970 Mon Sep 17 00:00:00 2001 From: James Youngman <[email protected]> Date: Fri, 17 May 2024 09:29:17 +0100 Subject: [PATCH] [doc] Explain that find defaults to GNU Emacs regexes. To: [email protected] This fixes Savannah bug #65297. --- doc/find.texi | 10 ++++------ find/find.1 | 11 +++++++---- 2 files changed, 11 insertions(+), 10 deletions(-) diff --git a/doc/find.texi b/doc/find.texi index 2e543085..b0218fb8 100644 --- a/doc/find.texi +++ b/doc/find.texi @@ -568,18 +568,16 @@ $ find . -path '*/*config' 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 match a file named @file{./fubar3}, you can use the regular expression -@samp{.*bar.} or @samp{.*b.*3}, but not @samp{f.*r3}. @xref{Regexps, -, Syntax of Regular Expressions, emacs, The GNU Emacs Manual}, for a -description of the syntax of regular expressions. For @samp{-iregex}, -the match is case-insensitive. +@samp{.*bar.} or @samp{.*b.*3}, but not @samp{f.*r3}. +For @samp{-iregex}, the match is case-insensitive. As for @samp{-path}, the candidate file name never ends with a slash, so regular expressions which only match something that ends in slash will always fail. There are several varieties of regular expressions; by default this -test uses POSIX basic regular expressions, but this can be changed -with the option @samp{-regextype}. +test uses GNU Emacs regular expressions, but this can be changed with +the option @samp{-regextype}. @end deffn @deffn Option -regextype name diff --git a/find/find.1 b/find/find.1 index cd1abfaa..8f93b6c2 100644 --- a/find/find.1 +++ b/find/find.1 @@ -466,8 +466,11 @@ expression types are known, use The Texinfo documentation (see .B SEE .BR ALSO ) -explains the meaning of and -differences between the various types of regular expression. +explains the meaning of and differences between the various types of +regular expression. If you do not use this option, find behaves +as if the regular expression type +.B emacs +had been specified. .IP "\-warn, \-nowarn" Turn warning messages on or off. These warnings apply only to the @@ -1034,8 +1037,8 @@ you can use the regular expression `.*bar.\&' or `.*b.*3', but not `f.*r3'. The regular expressions understood by .B find -are by default Emacs Regular Expressions (except that `.' matches -newline), but this can be changed with the +are by default Emacs Regular Expressions, but this can be changed with +the .B \-regextype option. -- 2.39.2