From 26a329f49fb4537d598e93f16054fd9e16f7e677 Mon Sep 17 00:00:00 2001 From: Eugene Grosbein Date: Fri, 22 Jul 2022 18:39:47 +0700 Subject: [PATCH] find.1: explain why "find -s" may differ from "find | sort" In short, that's because a directory name may end with a character that goes before slash (/). MFC after: 1 week --- usr.bin/find/find.1 | 22 +++++++++++++++++++++- 1 file changed, 21 insertions(+), 1 deletion(-) diff --git a/usr.bin/find/find.1 b/usr.bin/find/find.1 index 72fe3c0bea06..9efb8908ee63 100644 --- a/usr.bin/find/find.1 +++ b/usr.bin/find/find.1 @@ -31,7 +31,7 @@ .\" @(#)find.1 8.7 (Berkeley) 5/9/95 .\" $FreeBSD$ .\" -.Dd November 8, 2021 +.Dd July 22, 2022 .Dt FIND 1 .Os .Sh NAME @@ -158,6 +158,26 @@ Note: and .Ql "find | sort" may give different results. +.Pp +For example, +.Ql find -s +puts a directory +.Ql Ar foo +with all its contents before a directory +.Ql Ar foo. +but +.Ql "find | sort" +puts the directory name +.Ql Ar foo. +before any string like +.Ql Ar foo/bar +because +.Ql .\& +goes before +.Ql / +in ASCII. In locales other than +.Ar C +results may vary more due to collate differences. .It Fl x Prevent .Nm