[bug #59745] Issues in findutils manpages

[Andreas Metzler]

Follow-up Comment #3, bug #59745 (project findutils):

Hello Helge,

On 2020-12-27 Helge Kreutzmann wrote:
> Follow-up Comment #2, bug #59745 (project findutils):
[...]
>>> Man page: find.1
>>> Issue: Superflous space in first line

>>> "The %m and %d directives support the B<#> , B<0> and B<+> flags, but the
[...]
>> The only duplicate spaces are right after the full stop. And afaict
>> this is done so throughout the manpage. No idea whether this is the
>> right thing to do.

> What this was referring to is the "B<#> , B<0>" part. The space before the
> comma, which is not present in other lists. The double space after the full
> stop is ignored by us, this is common.

Ah, thanks for the glasses. :-) Patch to be updated.

> ...
>>> "B<$ find . -name *.c -print>\n"
>>> "find: paths must precede expression\n"
>>> "find: possible unquoted pattern after predicate `-name'?\n"

> Looks correct in current GIT.

> Actually, it doesn't even error out in my Debian unstable system
> anymore, so I cannot check.

This quoting issue only shows up if *.c is expanded by the shell because
there
are matching files in pwd:
~~~
ametzler@argenau:~$ rm -rf /tmp/findtest/ ; mkdir /tmp/findtest/ ; cd
/tmp/findtest/
ametzler@argenau:/tmp/findtest$ find . -name *.c -print
ametzler@argenau:/tmp/findtest$ touch fil1.c fil2.c
ametzler@argenau:/tmp/findtest$ find . -name *.c -print
find: paths must precede expression: `fil2.c'
find: possible unquoted pattern after predicate `-name'?
ametzler@argenau:/tmp/findtest$ echo find . -name *.c -print
find . -name fil1.c fil2.c -print
~~~

cu Andreas

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?59745>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/