Re: Minor typos on find(1) manpage

[James Youngman]

On 7/15/07, S.-H.Zimmermann <address@hidden> wrote:
> Hi, all,
> the find(1) manpage looks really good.
> This is rather important, since that utility is not the easiest one
> to understand and to use.
>
>
> Some minor details which might be fixed:
>
> EXPRESSIONS
>    -nouser
>    -nogroup
>    ( -context ...  non-standard extension, okay with me )
> not in alphabetical order.

Thanks for spotting that.   There is no -context test in the upstream code.

> Same goes for
>    -ok
>    -print
>    -okdir
>    ...
>    -ls
>
> -execdir
>    "This *IS* a much more secure method"


I think I have now fixed all the ordering issues there.

> STANDARDS CONFORMANCE
>     -name:
>         period instead of comma in list in ().

Thanks.

>         Identical under HISTORY.

Can't find that one in my version, are you sure?

>     Other predicates:
>         "The POSIX standard requires that<very hard break>
>          The find utility shall detect ..."
>         Something is wrong wiith this sentence.

That is deliberate, the indented paragraph is a quotation.  I have
changed the phrasing of the surrounding text to make this clearer.

>     -perm /mode
>        even lower importance ...
>        a hyphen might be inserted before the name 'perm'
>        "... with the behaviour of perm -000"

Thanks.

> ENVIRONMENT VARIABLES
>     NLSPATH
>        "internationalisation"
>        actually spelled with 'z', "internationalization"

Not here it isn't.  Not everybody lives in the USA :-)

>        (see LANG,LC_ALL above; that's why I18N has been invented).
>        LC_MESSAGES internationali*s*ed?
>
> Splitting my last hairs now,
>     "use of the -exec option"
>     is actually an "action"
>     (several times; mostly called 'action', should be consistent).

Good catch.  Fixed three of these.   Thanks.

> I've seen those on manpages and
> found them also e.g. at http://linux.die.net/man/1/find
> but I'm not sure who is maintaining the genuine text

I am the upstream author.   You've sent your nits to the right place.
Thanks for the help.    I have entered your bug report into the
findutils bug tracking system
(https://savannah.gnu.org/bugs/index.php?20552).  This allows me to
remember to mention the fix in the release notes and so on.   It also
means that you will get an email when I commit the change fixing the
problem (this will happen after the patch has been reviewed).

James.