[bug #59745] Issues in findutils manpages

[Helge Kreutzmann]

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

Hello Andreas,
thanks for handling these issues. A few remarks from my side:
> 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
"
> "other directives do not, even if they print numbers.  Numeric directives "
> "that do not support these flags include B<G>, B<U>, B<b>, B<D>, B<k> and "
> "B<n>.  The `-' format flag is supported and changes the alignment of a
field
> "
> "from right-justified (which is the default) to left-justified."

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


Look correct in current GIT.

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

...


    _______________________________________________________

Reply to this item at:

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

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