Hello findutils, I noticed a small typo in the docs for symbolic link handling 
(which also showed up in a comment) and modified it using a regex. The built 
output in {prefix}/share/info/find.info appears to pick up the change correctly.

As a side note, I have been working on a library to perform directory traversal 
and really wished I'd looked at `find` more closely earlier. In particular the 
discussion of symbolic link handling, stat optimization with -noleaf, and the 
clever error behavior from -ignore_readdir_race all help to resolve some 
questions I'd been having difficulty with. The docs section on security 
implications is also just incredibly well-done and I have mentioned the HTML 
rendered documentation to others as an example of really effective discussion 
of safety/security.

Great software!
--Danny McClanahan

diff --git a/doc/find.texi b/doc/find.texi
index c84d8a4a..3d7c63a1 100644
--- a/doc/find.texi
+++ b/doc/find.texi
@@ -819,7 +819,7 @@ Actions that can cause symbolic links to become broken while
 confusing behaviour.  Take for example the command line
 @samp{find -L . -type d -delete}.   This will delete empty
 directories.  If a subtree includes only directories and symbolic
-links to directoires, this command may still not successfully delete
+links to directories, this command may still not successfully delete
 it, since deletion of the target of the symbolic link will cause the
 symbolic link to become broken and @samp{-type d} is false for broken
 symbolic links.
diff --git a/find/testsuite/find.gnu/execdir-hier.exp 
b/find/testsuite/find.gnu/execdir-hier.exp
index 59d877bb..4529919e 100644
--- a/find/testsuite/find.gnu/execdir-hier.exp
+++ b/find/testsuite/find.gnu/execdir-hier.exp
@@ -1,5 +1,5 @@
 # tests for -execdir ... \+
-# Specifically, ensure that output for separate directoires is not mixed.
+# Specifically, ensure that output for separate directories is not mixed.
 if { [ safe_path ] } {
     exec rm -rf tmp
     exec mkdir tmp tmp/two

Reply via email to