Timeline for Do progress reports/logging information belong on stderr or stdout?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 11, 2020 at 14:16 | history | edited | CommunityBot | Commonmark migration | |
| Jan 13, 2017 at 9:10 | vote | accept | terdon♦ | ||
| Dec 21, 2016 at 19:05 | history | edited | B. Szonye | CC BY-SA 3.0 | Update to reflect usage clarifications |
| Dec 21, 2016 at 18:56 | comment | added | B. Szonye | Ah thanks for the clarification, that’s a little bit different from just stuff like “% complete” and hash-mark progress bars that you see in software like curl and yum. In that case, I would think about whether and how the user would want to interact with the output via grep or less or similar tools. | |
| Dec 21, 2016 at 12:23 | comment | added | terdon♦ | Thanks, the GNU guideline is the sort of thing I'm after. However, I realize my question was a little misleading. When I mentioned "progress reports" I was thinking of both things like N% done and things like doing foo and foo done. The latter should always be kept since they are used for debugging when redirected to a file. So your suggestion of checking whether the stream is interactive isn't applicable (though generally a very good idea). | |
| Dec 21, 2016 at 2:33 | review | First posts | |||
| Dec 21, 2016 at 2:43 | |||||
| Dec 21, 2016 at 2:28 | history | answered | B. Szonye | CC BY-SA 3.0 |