On 2019-11-10 00:37, 積丹尼 Dan Jacobson wrote:
> On man find, the only line that talks about "symlinks" is
> 
> 
>               %Y File's type (like %y), plus follow symlinks: `L'=loop,
>                `N'=nonexistent, `?' for any other error when determining
>                the type of the symlink target.
> 
> All the many rest on that page call them symbolic links. So this one
> should too, else searching for one misses the other, yes even if it is
> common knowledge that they are the same.

Good spot.

Fixed in 'find.1' - and additionally in 2 places in the Texinfo manual -
with the attached patch.
WDYT?

Have a nice day,
Berny
>From a0169f9aac1fd65e835b9c0df4001a792716c589 Mon Sep 17 00:00:00 2001
From: Bernhard Voelker <m...@bernhard-voelker.de>
Date: Wed, 13 Nov 2019 00:15:28 +0100
Subject: [PATCH] doc: use "symbolic link" instead of "symlink" consistently
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

* doc/find.texi (-printf): Change the shorter term "symlink" to
"symbolic link" for consistency with the rest of the Texinfo manual
and the man page.
(%Y): Likewise.
* find/find.1 (%Y): Likewise.

Suggested by 積丹尼 Dan Jacobson <jida...@jidanni.org> in:
  https://lists.gnu.org/r/bug-findutils/2019-11/msg00003.html
---
 doc/find.texi | 14 +++++++-------
 find/find.1   |  5 +++--
 2 files changed, 10 insertions(+), 9 deletions(-)

diff --git a/doc/find.texi b/doc/find.texi
index fbfa57ef..2cb80010 100644
--- a/doc/find.texi
+++ b/doc/find.texi
@@ -1740,11 +1740,11 @@ the output, instead of @samp{-ls}'s backslash-escaped names.  (Using
 specifier; @pxref{Unusual Characters in File Names}).  This format also
 outputs a uniform timestamp format.
 
-As for symlinks, the format above outputs the symlink target on a second
-line, following @samp{\n->}.  There is nothing following the arrow for
-non-symlinks.  Another approach, for complete consistency, would be to
-@code{-fprintf} the symlinks into a separate file, so they too can be
-null-terminated.
+As for symbolic links, the format above outputs the target of the symbolic link
+on a second line, following @samp{\n->}.  There is nothing following the arrow
+for file types other than symbolic links.
+Another approach, for complete consistency, would be to @code{-fprintf} the
+symbolic links into a separate file, so they too can be null-terminated.
 @end deffn
 
 @deffn Action -fprintf file format
@@ -1963,8 +1963,8 @@ link, @samp{l} will be printed.
 Type of the file as used with @samp{-type}.  If the file is a symbolic
 link, it is dereferenced.  If the file is a broken symbolic link,
 @samp{N} is printed.
-When determining the type of the symlink target, and a loop is encountered,
-then @samp{L} is printed (e.g. for a symlink to itself);
+When determining the type of the target of a symbolic link, and a loop is
+encountered, then @samp{L} is printed (e.g. for a symbolic link to itself);
 @samp{?} is printed for any other error (like e.g. @samp{permission denied}).
 
 @end table
diff --git a/find/find.1 b/find/find.1
index 20a1c109..da51a520 100644
--- a/find/find.1
+++ b/find/find.1
@@ -1576,8 +1576,9 @@ File's type (like in
 .BR "ls \-l" ),
 U=unknown type (shouldn't happen)
 .IP %Y
-File's type (like %y), plus follow symlinks: `L'=loop, `N'=nonexistent, `?' for
-any other error when determining the type of the symlink target.
+File's type (like %y), plus follow symbolic links: `L'=loop, `N'=nonexistent,
+`?' for any other error when determining the type of the target of a symbolic
+link.
 .IP %Z
 (SELinux only) file's security context.
 .IP "%{ %[ %("
-- 
2.23.0

Reply via email to