Timeline for Do progress reports/logging information belong on stderr or stdout?
Current License: CC BY-SA 3.0
18 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 13, 2017 at 12:36 | history | edited | CommunityBot | replaced http://unix.stackexchange.com/ with https://unix.stackexchange.com/ | |
| Jan 13, 2017 at 9:10 | vote | accept | terdon♦ | ||
| Dec 26, 2016 at 23:04 | comment | added | Gaurav | One possible one-size-fits-all solution would be to only use stderr to report error messages, except when a --verbose flag is used, at which point progress reports are included as well. | |
| S Dec 21, 2016 at 18:39 | history | suggested | jwodder | CC BY-SA 3.0 | Proofreading |
| Dec 21, 2016 at 18:26 | review | Suggested edits | |||
| S Dec 21, 2016 at 18:39 | |||||
| Dec 21, 2016 at 12:20 | history | edited | terdon♦ | CC BY-SA 3.0 | added 60 characters in body; edited title |
| Dec 21, 2016 at 11:03 | comment | added | dotancohen | How I wish that we had a 'meta' file descriptor | |
| Dec 21, 2016 at 6:51 | answer | added | muru | timeline score: 16 | |
| Dec 21, 2016 at 2:28 | answer | added | B. Szonye | timeline score: 49 | |
| Dec 20, 2016 at 23:47 | answer | added | AnoE | timeline score: 15 | |
| Dec 20, 2016 at 15:17 | history | tweeted | twitter.com/StackUnix/status/811229025460961280 | ||
| Dec 20, 2016 at 15:03 | answer | added | Random832 | timeline score: -2 | |
| Dec 20, 2016 at 14:12 | comment | added | Stephen Kitt | @Seven I think you misunderstood; Sato is saying that using stdout is unsafe ("safe way to make the results useless"). | |
| Dec 20, 2016 at 12:29 | comment | added | Se ven | same as Sato Katsura said, stdout is actually a safe and right way to pringting spinners and other informative messages, but as many programmer say 'Silence is golden. Output nothing if everything is fine.' so in fact, stderr is always used to do that because of the vague definition and also stdout may break the pipe sequence.for official guide | |
| Dec 20, 2016 at 11:33 | comment | added | terdon♦ | @SatoKatsura yeah, that's my opinion as well and that's why I print such to stderr. The CTO of the company I work for, however, feels that printing to stderr is an indication that something went wrong. I made the, rather bold, claim that the POSIX Way® is printing to stderr and he called me out on it. Given that he has 20 odd years of experience on me, I would like to see if I can find some sort of "official" guideline. | |
| Dec 20, 2016 at 11:02 | comment | added | Satō Katsura | Printing spinners and the like to stdout together with the results is a safe way to make the results useless. If you ever need to pipe the results to some other program, said program would need to separate the results from the spinners. Also, if you redirect the output to a file you won't be able to see the spinners. IMHO. | |
| Dec 20, 2016 at 10:35 | answer | added | Stephen Kitt | timeline score: 96 | |
| Dec 20, 2016 at 10:13 | history | asked | terdon♦ | CC BY-SA 3.0 |