Matěj Cepl <mcepl@xxxxxxx> writes: > On Wed Jan 15, 2025 at 12:22 PM CET, Jonas Konrad wrote: >> What did you do before the bug happened? (Steps to reproduce your issue) >> I opened a terminal on Arch Linux with a bash shell and called `git >> branch -h` to get a usage overview of git's `branch` command. I then >> tried processing the output with `grep` by `git branch -h | grep list` >> which gave the whole (unfiltered) output, i.e., the displayed message >> was not processed by `grep`. > > And that is exactly the correct behaviour. In the world of UNIX, > where pipes are normal, utilities should send to the stdout > only substantial material, ... If I understand the case Jonas reports correctly, he is talking about "git branch -h<RETURN>", and the "substantial material" (I'd rather phrase it as the primary output in response to the end user request) in that case is the help text. Somebody may want to go over "git help --all" and for each of them try "git $cmd -h >/dev/null" to find those that give the help output to their standard error stream. Thanks, both.
