On Mon, 9 Jan 2012, Warren Block wrote:
The user can request usage() output with -h or --help or something
equivalent, and that output should go to stdout because it's not an error and
that data is what was requested. IMO, of course.
This should probably be implemented by passing a FILE poin
On Mon, 9 Jan 2012, Bruce Evans wrote:
On Sun, 8 Jan 2012, Warren Block wrote:
Description:
usbconfig(8)'s -h option prints output to stderr. This output is not due
to an error, and is already 28 lines line. A typical terminal will not
display it all, so the user has to redirect stderr to
On Sun, 8 Jan 2012, Warren Block wrote:
Description:
usbconfig(8)'s -h option prints output to stderr. This output is not due to an
error, and is already 28 lines line. A typical terminal will not display it
all, so the user has to redirect stderr to view it with less or other utilities.
H
Synopsis: [patch] usbconfig(8) sends help output to stderr instead of stdout
Responsible-Changed-From-To: freebsd-bugs->eadler
Responsible-Changed-By: eadler
Responsible-Changed-When: Sun Jan 8 21:12:26 UTC 2012
Responsible-Changed-Why:
I'll take it.
http://www.freebsd.org/cgi/query-pr.cgi?pr=16
>Number: 163934
>Category: bin
>Synopsis: [patch] usbconfig(8) sends help output to stderr instead of
>stdout
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible:freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Re
