From 9b7edc688430b6c827eb3b85b49dabb575f8f07c Mon Sep 17 00:00:00 2001 From: Bernhard Voelker Date: Wed, 30 Dec 2020 09:53:32 +0100 Subject: [PATCH] doc: minor grammar change about a change in the past In the description of -name patterns matching "hidden" files, i.e., those beginning with a dot, avoid talking in the future. The change was back in version 4.2.2. Maybe we should drop this hint about historic behavior at all. * doc/find.texi (Base Name Patterns): Remove the word "will". * find/find.1 (.SH STANDARDS CONFORMANCE): Likewise. (.SH HISTORY): Likewise. --- doc/find.texi | 4 ++-- find/find.1 | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/doc/find.texi b/doc/find.texi index 2e8549a0..05ed5210 100644 --- a/doc/find.texi +++ b/doc/find.texi @@ -400,8 +400,8 @@ Notice that the wildcard must be enclosed in quotes in order to protect it from expansion by the shell. As of findutils version 4.2.2, patterns for @samp{-name} and -@samp{-iname} will match a file name with a leading @samp{.}. For -example the command @samp{find /tmp -name \*bar} will match the file +@samp{-iname} match a file name with a leading @samp{.}. For +example the command @samp{find /tmp -name \*bar} match the file @file{/tmp/.foobar}. Braces within the pattern (@samp{@{@}}) are not considered to be special (that is, @code{find . -name 'foo@{1,2@}'} matches a file named @file{foo@{1,2@}}, not the files @file{foo1} and diff --git a/find/find.1 b/find/find.1 index 3bfb45e0..b90e8fa8 100644 --- a/find/find.1 +++ b/find/find.1 @@ -1849,7 +1849,7 @@ This option is supported, but POSIX conformance depends on the POSIX conformance of the system's .BR fnmatch (3) library function. As of findutils-4.2.2, shell metacharacters -(`*', `?' or `[]' for example) will match a leading `.', because +(`*', `?' or `[]' for example) match a leading `.', because IEEE PASC interpretation 126 requires this. This is a change from previous versions of findutils. @@ -2461,7 +2461,7 @@ may not have been performed. . .SH "HISTORY" As of findutils-4.2.2, shell metacharacters (`*', `?' or `[]' for -example) used in filename patterns will match a leading `.', because +example) used in filename patterns match a leading `.', because IEEE POSIX interpretation 126 requires this. .P As of findutils-4.3.3,