tag 21749 notabug
thanks

On 10/24/2015 04:36 AM, Andreas Kern wrote:
> steps to reproduce
> 
>     run `printf --help`

That's probably running your shell's builtin printf, rather than the one
from coreutils.

Try:

env printf --help

or

/bin/printf --help

and to see the difference, try:

type printf

> comment:
> I checked it on ubuntu and on arch, both don't print the help. I checked
> the source package on ubuntu and there is code for that in printf.c

If you read the source code, you may also notice that coreutils' 'printf
--help' includes this text:


$ env printf --help | tail

and all C format specifications ending with one of diouxXfeEgGcs, with
ARGUMENTs converted to proper type first.  Variable widths are handled.

NOTE: your shell may have its own version of printf, which usually
supersedes
the version described here.  Please refer to your shell's documentation
for details about the options it supports.

GNU coreutils online help: <http://www.gnu.org/software/coreutils/>
For complete documentation, run: info coreutils 'printf invocation'

As such, I'm closing this as not a bug, although you should feel free to
make further comments.  Also, future bash releases may be adding support
for 'printf --help' with the bash builtin printf, to match the fact that
ksh builtin printf already accepts that option; but that won't help for
dash, which is Ubuntu's /bin/sh.

-- 
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to