Fixed with this patch.
On Fri, May 17, 2024 at 9:49 AM James Youngman <invalid.nore...@gnu.org>
wrote:
> Update of bug #65283 (group findutils):
>
> Severity: 3 - Normal => 2 - Minor
>
> Status: None => Fixed
>
> Assigned to: None => jay
>
>
> _______________________________________________________
>
> Follow-up Comment #1:
>
> Fixed in git.
>
> Example: The output of "locate foo" would include /home/james/foo/bar
> while the output of "find /home -name foo" would not.
>
>
>
> _______________________________________________________
>
> Reply to this item at:
>
> <https://savannah.gnu.org/bugs/?65283>
>
> _______________________________________________
> Message sent via Savannah
> https://savannah.gnu.org/
>
>
From 9cbbb20bd5f4490ac46431b4e7086ef761aab8af Mon Sep 17 00:00:00 2001
From: James Youngman <ja...@youngman.org>
Date: Fri, 17 May 2024 09:45:46 +0100
Subject: [PATCH] [doc] Explain how locate's and find's default matching
differ.
To: findutils-patc...@gnu.org
Example: The output of "locate foo" would include /home/james/foo/bar
while the output of "find /home -name foo" would not.
---
doc/find.texi | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/doc/find.texi b/doc/find.texi
index b0218fb8..634ae9fc 100644
--- a/doc/find.texi
+++ b/doc/find.texi
@@ -645,9 +645,9 @@ find @var{directories} -name @var{pattern}
where @var{directories} are the directories for which the file name
databases contain information. The differences are that the
-@code{locate} information might be out of date, and that @code{locate}
-handles wildcards in the pattern slightly differently than @code{find}
-(@pxref{Shell Pattern Matching}).
+@code{locate} information might be out of date, and that by default
+@code{locate} matches wildcards against the whole file name (not just
+its base name) (@pxref{Shell Pattern Matching}).
The file name databases contain lists of files that were on the system
when the databases were last updated. The system administrator can
--
2.39.2
