> stdout is only reserved for actual processed command output
replyIf user asks a program to print help message, the help text is the processed command output!
GNU offers guidance[1] to output --help to stdout, but it's not against the law to do it your way.
reply1: https://www.gnu.org/prep/standards/html_node/_002d_002dhelp....
I guess this is a point where I disagree with GNU. Then again, the reasons why I disagree are subtle enough that I don't care too much... I think this particular thing doesn't matter very much in practice, so go do your thing GNU...
replyI can see both sides. As someone automating, I could see getting the malformed command -h result to stderr. I can also see that sending -h to stdout would be expected as that is the legit out as requested by the user. At the least, if -h is sent to stdout for a malformed command then by gawd it better be a nonzero exit. With that, I think (and boy did it hurt) that it's an okay rule to break
replyOut of the problems we all agonize over, this is probably a 1 out of 10!
replyIn the case of `git log -100 | grep FOO`, the log output should go to stdout.
replyIn the case of `git diff | grep FOO`, the diff output should go to stdout.
In the case of `git --help | grep FOO` the help output should go to stdout.
In the case of `git --omg-wtf | grep FOO`, it's fine if there is only output on stderr.
I see you've never tried to run command --help | less
replyI just said that I always do `command --help 2>&1 | less`?
replyPretty annoying. Wouldn't it be good if command --help would just display the help?
reply